Message-ID: <36E8B766.EE1BF43@aaanet.ru>
Date: Fri, 12 Mar 1999 09:42:46 +0300
From: Vitali Shulgin <shulgin AT aaanet DOT ru>
Organization: JSC DONTELECOM
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: pgcc AT delorie DOT com
Subject: Re: pgcc-1.1.1 against glibc-2.1 INCLUDE_PATH
References: <36E77314 DOT C76F41F3 AT aaanet DOT ru> <19990312032621 DOT H16842 AT cerebro DOT laendle>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
Reply-To: pgcc AT delorie DOT com

Currently I'm using egcs-1.1.1
I've successfully compiled the glibc2.1 with it.
All the checkings were passed without any errors and warnings.
After that, I've made installation accordingly to all recommendations
from glibc FAQ, readme and etc.

After that, I decided to patch egcs with pgcss and recompile 
against new library.

My configure commandline include:

--enable-shared --with-gnu-as --with-gnu-ld --enable-threads
--prefix=/usr

Here are the lines preceding to error message:

--begin--
In file included from
/usr/lib/gcc-lib/i686-pc-linux-gnu/egcs-1.1.1/include/limits.h:117
		from include/limits.h:117
		from include/syslimits.h:7
		from include/limits.h:11
		from ../../egcs-1.1.1/gcc/libgcc2.c:1101
/usr/include/limits.h:132 No include path in where to find limits.h
--end--

Thank you for care...


Marc Lehmann wrote:
> 
> On Thu, Mar 11, 1999 at 10:39:00AM +0300, Vitali Shulgin wrote:
> > Hello all,
> >
> > I've just upgraded my system with glibc2.1
> 
> Quick question: is your (currently installed) compiler ready for glibc,
> too, or are you just using your old libc5 compiler? If yes, that is your
> problem.
> 
> > Now I'm trying to compile egcs patched with pgcc.
> > Problem is that I'm receiving error : "No include path in which to find
> > limits.h"
> > I have several "limits.h" in my system. :
> > To which one should I point the process?
> 
> To none of them. If you compiler is unable to find his limits.h itself it is
> broken.
> 
> Can you quote the full compiler call that caused this problem, i.e. a few
> lines before that error message, and the commandline you used to configure
> pgcc with?
> 
> --
>       -----==-                                             |
>       ----==-- _                                           |
>       ---==---(_)__  __ ____  __       Marc Lehmann      +--
>       --==---/ / _ \/ // /\ \/ /       pcg AT goof DOT com      |e|
>       -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
>     The choice of a GNU generation                       |
>                                                          |