I got interrupted/distracted by the release testing for Berkeley UPC.
So, I missed the fact that the fix of #87 was OK for x86-64, but not quite right for x86 (i386).
The problem looks similar to #87:
/usr/bin/ld: cannot open linker script file upc.ld: No such file or directory
clang-3.8: error: linker command failed with exit code 1 (use -v to see invocation)
But the problem is not a missing -L, but rather that the one provided doesn't match where the libs and linker script were installed.
While all of the LLVM libs are in ${prefix}/lib/, the upc.ld and other UPD runtime files are all in ${prefix}/lib/32/. Meanwhile the linker command contains -L${prefix}/bin/../lib.
I would guess that the proper fix is to change where the UPC runtime files are installed, since ONLY the UPC files are in that "32" subdirectory (and that is the only ABI on the system).
PHHargrove
commented
8 years ago
I got interrupted/distracted by the release testing for Berkeley UPC. So, I missed the fact that the fix of #87 was OK for x86-64, but not quite right for x86 (i386).
The problem looks similar to #87:
But the problem is not a missing -L, but rather that the one provided doesn't match where the libs and linker script were installed.
While all of the LLVM libs are in
${prefix}/lib/, theupc.ldand other UPD runtime files are all in${prefix}/lib/32/. Meanwhile the linker command contains-L${prefix}/bin/../lib.I would guess that the proper fix is to change where the UPC runtime files are installed, since ONLY the UPC files are in that "32" subdirectory (and that is the only ABI on the system).