Re: configure problem for cross compilers

[Jim Wilson <wilson at specifixinc dot com>]

Jan Beulich wrote:
> Trying to build an x86_64 compiler (3.4.0) on an x86 machine, I ran into what seem to be a general problem with the top level configure script forcing LD to be set (for libtool) but that way confusing the gcc/configure script's determination of what ld to use (namely does this prevent a newly built ld in the same tree to be used). This used to not be a problem until 3.3.3.
> Is this intentional (and thus there is a known solution * other than having to pass in LD=ld each time one wants to run a cross configure * that I simply wasn't able to locate), or should I file this as a bug? In the latter case, I'm also unclear where such a bug for the top-level stuff should go (as this is not gcc-specific).

It isn't clear to me what problem you are trying to reprort.  Please 
give more details.  We can't help unless we can reproduce the problem.

It looks like you are complaining abou the gcc_prog_ld code in the 
toplevel configure.in, but I don't understand why it is a problem.

You say this was never a problem until gcc-3.3, but it looks like this 
code is new in gcc-3.4, so if there was a problem with gcc-3.3, it must 
have been a different one.

This sets LD which is supposed to be the native LD which goes with CC. 
This shouldn't be a newly built linker, particularly if you are trying 
to do a cross build.

It is OK to report bugs in the toplevel files against gcc.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com