#856 closed bug (duplicate)
Build failds on arch x86_64
Reported by: | johndrinkwater | Owned by: | admin |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Build System | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86-64 |
Description
How to reproduce:
Run on a x86_64 hosted machine, fyi, Fedora Core 4 on an AMD 64.
./configure --build-cross-tools-gcc4 x86 ../buildtools/ jam -q haiku-image
Building fails with:
Link generated/objects/linux/lib/libroot_build.so /usr/bin/ld: generated/objects/linux/release/build/libroot/errors.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC generated/objects/linux/release/build/libroot/errors.o: could not read symbols: Bad value collect2: ld returned 1 exit status cc -shared -Xlinker -soname="libroot_build.so" -o "generated/objects/linux/lib/libroot_build.so" "generated/objects/linux/release/build/libroot/byteorder.o" "generated/objects/linux/release/build/libroot/errors.o" "generated/objects/linux/release/build/libroot/fs.o" "generated/objects/linux/release/build/libroot/fs_attr.o" "generated/objects/linux/release/build/libroot/misc.o" "generated/objects/linux/release/build/libroot/sem.o" "generated/objects/linux/release/build/libroot/thread.o" "generated/objects/linux/release/build/libroot/strlcpy.o" "generated/objects/linux/release/build/libroot/strlcat.o" "generated/objects/linux/release/build/libroot/strnlen.o" -lstdc++ ;
Tried adding -fPIC into build/jam/BuildSetup, but doesn't work. Though probably have been editing the wrong var.
Change History (5)
comment:1 by , 18 years ago
Milestone: | → R1 |
---|---|
Version: | → R1 development |
comment:2 by , 18 years ago
comment:4 by , 17 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:5 by , 15 years ago
Platform: | x64 → x86-64 |
---|
Note:
See TracTickets
for help on using tickets.
hmm i see this error on my linux from scratch machine running clean 64-bit binaries. I may be able to fix this if my Mainboard RMA ever gets returned :((