This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Build error on trunk due to new ./configure

From: Paul Thomas <paulthomas2 at wanadoo dot fr>
To: Andrew Pinski <pinskia at physics dot uc dot edu>
Cc: Jan-Benedict Glaw <jbglaw at lug-owl dot de>, pault at gcc dot gnu dot org, gcc at gcc dot gnu dot org, rguenther at suse dot de
Date: Tue, 14 Mar 2006 20:19:12 +0100
Subject: Re: Build error on trunk due to new ./configure
References: <20060313224957.14853.qmail@sourceware.org> <20060314085640.GA32065@lug-owl.de> <20060314135424.GJ32065@lug-owl.de> <ba83bf173d6703a07eb6b0a367ffd6d8@physics.uc.edu>

Andrew (and everybody else),

I upgraded autoconf because the build crashed when I tried to regenerate the fortran library. There were already symbols present that were not recognised by my autoconf (I kept no record of which - it was the default with FC3). I upgraded to the version recommended in the error message......

i686-linux-gnu). No wonder that `genmode' cannot be linked with
../build-i686-pc-linux-gnu/libiberty/libiberty.a (which is now a
VAX-ELF file) :-)
This was just fixed by:
2006-03-14  Richard Guenther  <rguenther@suse.de>
* configure: Regenerate with autoconf 2.13.

..thanks, Richard. I did not realise that there would be this fall-out from the upgrade - equally, though, the pollution was already there.

Cheers

Paul

References:
- Re: r112028 - in /trunk: configure gcc/fortran/Chan...
  - From: Jan-Benedict Glaw
- Build error on trunk due to new ./configure (was: r112028 - in /trunk: configure gcc/fortran/Chan...)
  - From: Jan-Benedict Glaw
- Re: Build error on trunk due to new ./configure (was: r112028 - in /trunk: configure gcc/fortran/Chan...)
  - From: Andrew Pinski

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]