This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] Fix unified tree breakage
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Oct 07, 2005 at 11:08:38AM -0300, Alexandre Oliva wrote:
> I think you need some means to avoid running the wrong binary in
> Canadian crosses and cross-back tools. E.g., consider --build=x
> --host=y --target=z. How can run-tool --target=whatever distinguish
> between gas/as-new, that's built for the host y and thus won't run on
> the build machine x, from gcc/as, presumably copied from a pre-build
> --host=x --target=z toolchain, specified in
> $(CONFIGURED_AS_FOR_TARGET), or, as a potential nice improvement,
> built in the build-x directory.
I ran into something like this the other day, while building GCC as
- --build=i686-pc-linux-gnu --host=i386-mingw32 --target=arm-unknown-elf.
The resulting GCC wants to run just "as"; if I specify
- --with-as=c:/gnutools/cross/bin/arm-unknown-elf.exe (which is what I
really wanted), the configure script got confused about what exactly
that --with-as (and same for ld) is: a tool running on the build
machine, or the host machine. At runtime GCC wants to use it as
DEFAULT_ASSEMBLER to rewrite in the place of "as" in invoke_as, so from
that perspective it is a host tool. OTOH the configure script expects
that specified assembler to exist and be test -x, which is just
confused.
Eventually I just got my colleague to do gcc -dumpspecs >specs, edit
invoke_as, and then add -specs=specs to $(CC) in the makefile. Does GCC
really need --with-host-as=/nonexistent/on/build/as, or do I need to
RTFM on --with-sysroot?
For the archives...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Please fetch my new key 804177F8 from hkp://wwwkeys.eu.pgp.net/
Comment: Key D7CBA633 will soon expire, check its signature of 804177F8 now!
iD8DBQFDRtGawyMv24BBd/gRAoP5AJ0QN3cWbH7mqNRQA4nIRTJteqfBogCeO/9s
ka58VHMt8ZkshNcH+l2aaPY=
=fCj7
-----END PGP SIGNATURE-----