Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com> List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com> List-Archive: <http://sourceware.cygnus.com/ml/cygwin/> List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com> List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199911101541.JAA24924@mercury.xraylith.wisc.edu> To: Mike MacDonald <mmacdona AT tsi DOT gte DOT com> cc: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com> Subject: Re: include path In-Reply-To: Your message of "Wed, 10 Nov 1999 10:24:03 EST." <D7FDE5F0B39AD21181AA00805FA7183E040ABA1B AT tpaexc02 DOT tsi DOT gte DOT com> Date: Wed, 10 Nov 1999 09:41:42 -0600 From: Mumit Khan <khan AT thor DOT xraylith DOT wisc DOT edu> Mike MacDonald <mmacdona AT tsi DOT gte DOT com> writes: > I guess my probem is that gcc is not properly finding: > > /usr/lib/gcc-lib/i586-cygwin32/2.95.2/include > > And I don't want to have to modify all my Makefiles to point there, so I'm > wondering if there is a way to get it to look there.. It can't find the > libs in the 2.95.2 directory either, I was able to copy them to /usr/lib - > and it works fine.. Because of limits.h I can't do that with this dir.. > I'm gonna try mapping it to /include - which I should have thought of doing > before.. Mike, If you have to tell GCC to look into it's own include directory, your setup is hosed. Period. You seem to be having an awfully hard time with GCC, which I don't understand. There are many other people using it any/much trouble; I'd still like to understand why you're the one running into odd problems. My bet is the way you've modified your Cygwin installation with mounts or using environment variables, but I could be wrong of course. I suggest you post (or send me) the following: 1. output of `cygcheck -s -r' 2. gcc -v 3. gcc -print-search-dirs 4. gcc -o foo -v foo.c where foo.c is some hello world file Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com