Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 3 Sep 2005 00:07:59 +0200 (MET DST) From: Angelo Graziosi To: Cygwin List Subject: Re: xmkmf resuling in bad search path for std includes? In-Reply-To: <6.2.1.2.0.20050901205803.050ca2d8@pop.prospeed.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.0.3.2, Antispam-Data: 2005.9.2.28 X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __STOCK_CRUFT 0' On Thu, 1 Sep 2005, Larry Hall wrote: > At 05:53 PM 9/1/2005, you wrote: > > > >On Wed, 31 Aug 2005, Larry Hall wrote: > > > > > >I have uninstalled GPC package and removed the > >/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/ directory so that now there is not > >any reference to 3.3.3 version of GCC (not in the registry not on the > >disk). > > > >After this I have tried new builds of CERNLIB with 3.4.4-1 and also in > >this case there is the warning like this: > > > > > >---------------------------------------------------- > >makedepend: warning: ...... (reading /usr/include/sys/unistd.h, line > >13): cannot > >find include file "stddef.h" > >not in /usr/X11R6/include/stddef.h > >not in /usr/local/lib/gcc-include/stddef.h > >not in /usr/include/stddef.h > >not in /usr/include/w32api/stddef.h > > > >not in /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/include/stddef.h > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >---------------------------------------------------- > > > > > >>From where the reference to /usr/...../3.3.3/.... ? > > > Must your local config of CERNLIB itself that still remembers things as > they were when 3.3.3 was installed. Have you regenerated the makefile > since then? > > Every time I build starting from scartch, i.e. untaring the source and regenerating the makefile. It could be that there is some config file in the build process that references to GCC 3.3.3. I will investigate this deeply. Thanks, Angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/