This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: f2c configure fix
- To: Richard Henderson <rth at twiddle dot net>
- Subject: Re: f2c configure fix
- From: Jeffrey A Law <law at hurl dot cygnus dot com>
- Date: Tue, 09 Feb 1999 02:02:50 -0700
- cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, egcs-patches at egcs dot cygnus dot com
- Reply-To: law at cygnus dot com
In message <19990209003046.A7662@twiddle.net>you write:
> On Mon, Feb 08, 1999 at 02:32:44PM -0500, Kaveh R. Ghazi wrote:
> > So it appeared that the problem was that the appropriate -I
> > flag wasn't passed to configure to find libiberty.h.. (I'll assume
> > your explanation above occured because you fixed this and found the
> > next problem was that PROTO wasn't defined properly.)
>
> Um, actually, no. I did not see the same problem you are. One
> possible explanation is relative build tree differences. I have
If you're testing on linux, then you may be bitten by linux having libiberty
in /usr/include or somewhere else early in the path.
Other systems don't have an installed libiberty.h, which is what both Kaveh
and I have seen problems with.
Consider this from my hpux10.20 build:
configure:1065: using $CPP $CPPFLAGS -I../../gcc/f -I../../gcc -I../../gcc/confi
g -I/puke/law/egcs/egcs/libf2c/../gcc/f -I/puke/law/egcs/egcs/libf2c/../gcc -I/p
uke/law/egcs/egcs/libf2c/../gcc/config
In file included from /puke/law/egcs/egcs/libf2c/../gcc/f/system.j:25,
from /puke/law/egcs/egcs/libf2c/../gcc/f/proj.h:32,
from configure:1068:
/puke/law/egcs/egcs/libf2c/../gcc/system.h:426: libiberty.h: No such file or dir
ectory
Note carefully the -I arguments. Nothing gets us to the toplevel
$srcdir/include directory.
jeff