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 10:14:55 +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 16, 2000, Jeffrey A Law <law@cygnus.com> wrote:
>
> > In message <200008161553.QAA19038@cam-mail2.cambridge.arm.com>you write:
> >>
> >> Hmm, so I tried to turn on a reasonable combination of multilibs for the
> >> arm+elf back end. Ooops.
> >>
> >> All works fine until libf2c runs its check to see if the compiler can make
> >> valid executables. This fails for some of the multilib combinations
> >> because it is trying to use a version of newlib that was build for a
> >> different combination... Not good.
> >>
> >>
> >> Anyone know what's up here?
> > I believe Alexandre Oliva posted a patch for this (which I thought
> > eventually got approved)?!?
>
> Yep, it's in but, AFAICT, the -B and -L flags haven't been adjusted.
> Richard, is your copy of config-ml.in up-to-date
>
Yep, at least CVS says it is ...
One thing I notice is that configure is finding the value for gcc from
arm-elf/config.cache. Surely this is bad.
R.