This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Problem building libiberty
- To: ghazi at caip dot rutgers dot edu
- Subject: Re: Problem building libiberty
- From: Mark Kettenis <kettenis at wins dot uva dot nl>
- Date: Fri, 16 Jun 2000 20:05:53 +0200 (MET DST)
- CC: gcc-bugs at gcc dot gnu dot org
- References: <200006161538.LAA09959@caip.rutgers.edu>
Date: Fri, 16 Jun 2000 11:38:18 -0400 (EDT)
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
> I noticed the problem when building GDB (our libiberty was just resynced
> with GCC), but I'm pretty sure the same problem exists in GCC's master
> copy. Obviously a bug in gcc 2.7.2, but introducing a hard error to
> avoid a warning defeats its purpose a bit :-(.
> Mark
This problem should not occur if you also resync the top level
`include' directory which complements the `libiberty' directory. In
include/ansidecl.h, we define __extension__ to be empty if gcc < v2.8.
We did this precisely because we encountered the same issue
bootstrapping gcc with 2.7.x.
Thanks! I'll make sure the GDB/binutils repository updates its
`include' directory.
Mark