llvm-nm error The end of the file was unexpectedly encountered #10195
Comments
|
Additional interesting info: After a failed build with 1.39.5 I downgraded emscripten to 1.39.1, rerun compilation without removing |
|
@sbc100 I thought we had fixed the issue with |
|
I think it must of been #9758 where we added support for automatically adding archive indexes. |
|
Maybe the best solution is to write my own archive header parser to detect the missing index. |
|
I thought we had a test for this. WIll add one. |
|
I can't seem to reproduce this when adding random text files to the archive. Can you send me this |
|
The problem seems to be that rust metadata files start with two null bytes which means llvm thinks they are COFF files. Doh. I filed an llvm bug to try to get that fixed by I'm not sure it will land: https://bugs.llvm.org/show_bug.cgi?id=44683 In the mean time if looks like rust fixed this upstream too: rust-lang/rust#66235 I'm not sure how or when that change to rust-lang makes it into your toolchain but this problem should go away once it does. |
There is an llvm but that mean that certain binary files get mistaken for COFF object which means llvm-nm will error out: https://bugs.llvm.org/show_bug.cgi?id=44683 Instead write out own trivial ar parser to detect the presence of that index. Fixes: #10195
There is an llvm but that mean that certain binary files get mistaken for COFF object which means llvm-nm will error out: https://bugs.llvm.org/show_bug.cgi?id=44683 Instead write out own trivial ar parser to detect the presence of that index. Fixes: #10195
|
Should be fixed in #10300 |
There is an llvm but that mean that certain binary files get mistaken for COFF object which means llvm-nm will error out: https://bugs.llvm.org/show_bug.cgi?id=44683 Instead write out own trivial ar parser to detect the presence of that index. Fixes: #10195
There is an llvm but that mean that certain binary files get mistaken for COFF object which means llvm-nm will error out: https://bugs.llvm.org/show_bug.cgi?id=44683 Instead write out own trivial ar parser to detect the presence of that index. Fixes: #10195
Steps to reproduce:
rustup target add wasm32-unknown-emscriptencargo build --releaseConsole output
/tmp/emscripten_temp/is emptyEnvironment
Additional info
With emscripten 1.39.0 and 1.39.1 it compiles fine. Versions 1.39.2 and later are affected.
The text was updated successfully, but these errors were encountered: