This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libf2c + elf + multilib = build problems
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: Re: libf2c + elf + multilib = build problems
- From: Richard Earnshaw <rearnsha at arm dot com>
- Date: Thu, 17 Aug 2000 16:03:30 +0100
- Cc: law at cygnus dot com, gcc-bugs at gcc dot gnu dot org
- Cc: rearnsha at arm dot com
- Organization: ARM Ltd.
- Reply-To: rearnsha at arm dot com
> On Aug 17, 2000, Richard Earnshaw <rearnsha@arm.com> wrote:
>
> > Don't forget that config-ml.in is used in producing the target makefiles,
>
> No, it's used to run `configure' for each multilib variant, and it
> should adjust references to multilibbed directories in CC and CXX
> before running configure.
Ah, I've found the problem; it's at my end.
My copy of newlib was picking up a different version of config-ml.in (from
my sourceware tree) because of the way I have newlib symlinked into my gcc
tree. This was slightly out of date, so didn't have the latest changes in
it. This of course then wrote the bad line into config.cache which libf2c
was then picking up.
I've updated my newlib and it all builds fine now. However, I notice that
there are still a small number of (I think) white space differences
between gcc's version and that in the sourceware repository. Any chance
that these can be reconciled?
Oh for the day when gcc, binutils and newlib are part of a single
repository.
Anyway, thanks for your help,
Richard.