-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > Ian Lance Taylor escribió: When you compiled GCC yourself, what > target did you use? I didn't specified any target, my configure line was: ./configure --prefix=/usr - --bindir=/usr/x86_64-gentoo-freebsd6.1/gcc-bin/3.4.6 - --includedir=/usr/lib/gcc/x86_64-gentoo-freebsd6.1/3.4.6/include - --datadir=/usr/share/gcc-data/x86_64-gentoo-freebsd6.1/3.4.6 - --mandir=/usr/share/gcc-data/x86_64-gentoo-freebsd6.1/3.4.6/man - --infodir=/usr/share/gcc-data/x86_64-gentoo-freebsd6.1/3.4.6/info - --with-gxx-include-dir=/usr/lib/gcc/x86_64-gentoo-freebsd6.1/3.4.6/include/g++-v3 - --host=x86_64-gentoo-freebsd6.1 --build=x86_64-gentoo-freebsd6.1 - --disable-altivec --disable-nls --with-system-zlib --disable-checking - --disable-werror --disable-libunwind-exceptions --enable-multilib - --disable-libgcj --enable-languages=c,c++ --enable-shared - --enable-threads=posix --enable-__cxa_atexit > To get FreeBSD labelled binaries, you should configure with > something like --target=i386-freebsd I used it with the error: "Please update *-*-freebsd* in gcc/config.gcc" so I don't touch it (the $target that I got with that was "i386-pc-freebsd"). Shall config.gcc sets the correct target? Reading it I saw the case "*-*-freebsd[6].*)" and my CHOST is "x86_64-gentoo-freebsd6.1" so it triggered the target with same results. > You will also need to build the binutils with that --target option. > My binutils has the following BFDs: elf64-x86-64 elf32-i386-freebsd coff-i386 efi-app-ia32, and emulations: elf_x86_64_fbsd elf_i386_fbsd elf_x86_64 elf_i386 Thanks in advance, - -- Victor Roman Archidona -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) iD8DBQFEtIoJQ/ddYKMfqaARAj3UAKCVYKDjOEaIWyPPKHuAsabpPpIbcACfYLMU ToRvWAldWTCvTkxgU/iSCs8= =dfcM -----END PGP SIGNATURE-----
