Bug#630101: gdc-4.4: FTBFS: tries to build 32bit executable on 64bit system
Package: src:gdc-4.4
Version: 1.063-4.4.6-3
Severity: serious
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)
Hi!
Your package fails to build on the kfreebsd-amd64 buildd:
/build/buildd-gdc-4.4_1.063-4.4.6-3-kfreebsd-amd64-0PaC1x/gdc-4.4-1.063-4.4.6/build/./gcc/xgcc -B/build/buildd-gdc-4.4_1.063-4.4.6-3-kfreebsd-amd64-0PaC1x/gdc-4.4-1.063-4.4.6/build/./gcc/ -B/usr/x86_64-kfreebsd-gnu/bin/ -B/usr/x86_64-kfreebsd-gnu/lib/ -isystem /usr/x86_64-kfreebsd-gnu/include -isystem /usr/x86_64-kfreebsd-gnu/sys-include -g -O2 -O2 -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../.././gcc -I../../../src/libgcc -I../../../src/libgcc/. -I../../../src/libgcc/../gcc -I../../../src/libgcc/../include -DHAVE_CC_TLS -o _muldi3_s.o -MT _muldi3_s.o -MD -MP -MF _muldi3_s.dep -DSHARED -DL_muldi3 -c ../../../src/libgcc/../gcc/libgcc2.c
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-kfreebsd-gnu/libc.so when searching for -lc
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-kfreebsd-gnu/libc.a when searching for -lc
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/x86_64-kfreebsd-gnu/crti.o' is incompatible with i386 output
/usr/bin/ld: i386:x86-64 architecture of input file `/usr/lib/x86_64-kfreebsd-gnu/crtn.o' is incompatible with i386 output
collect2: ld returned 1 exit status
make[7]: *** [libgcc_s.so] Error 1
make[7]: Leaving directory
`/build/buildd-gdc-4.4_1.063-4.4.6-3-kfreebsd-amd64-0PaC1x/gdc-4.4-1.063-4.4.6/build/x86_64-kfreebsd-gnu/32/libgcc'
Full log at
https://buildd.debian.org/status/fetch.php?pkg=gdc-4.4&arch=kfreebsd-amd64&ver=1.063-4.4.6-3&stamp=1307661109
Regards
Christoph
If you have further questions please mail debian-bsd@lists.debian.org
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
Reply to: