This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Possible problem in libstdc++v3 (A happy conclustion)
- To: gcc at gcc dot gnu dot org
- Subject: Re: Possible problem in libstdc++v3 (A happy conclustion)
- From: Loz <loz at flower dot powernet dot co dot uk>
- Date: Wed, 18 Jul 2001 21:51:05 +0100
- Followup-To: <3B54C648.1070803@flower.powernet.co.uk>;,from,loz@flower.powernet.co.uk,on,Wed,Jul,18,2001,at,12:12:08AM
Upgrading to the latest development release of binutils (2.11.90.0.24)
fixed the problem, I guess that means that gcc was generating OK
assembler. Reading through the change log I'd guess it was the fix in
2.11.90.0.8 that did it. Its a happy coincidence that the chap who
writes the binutils release notes (and the code too!) posts them to the
gcc list.
Thinking about the whole "Is a cross-compiler from i686 to i586
pointless" thing: I'm now thinking, given that I need to create some
statically linked binaries that it may be a useful way of organizing the
different architecture versions of the libraries I need, as most GNU
stuff supports --target in their configure scripts - and the cross
linker will then look in the right place by default. I'm sure I could do
all this with options to ld through make by hand, but this seem easier.
cheers
Loz