Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
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
X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs
Date: Wed, 26 Apr 2000 14:56:21 -0500 (CDT)
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
Reply-To: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To: Fontenot Larry A DLVA <FontenotLA AT NSWC DOT NAVY DOT MIL>
cc: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: Weird behavior when using "-I" with gcc-2.95.2 
In-Reply-To: <7B4C28C84831D211BFA200805F9F34567030F5@nswcdlvaex04.nswc.navy.mil>
Message-ID: <Pine.HPP.3.96.1000426145016.12100G-100000@hp2.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 25 Apr 2000, Fontenot Larry A DLVA wrote:

> Attached is the requested bug.txt.  It looks as though the default search
> paths are still valid.  And everything works just fine until I add a "-I
> anypath".  The only way to get the compiler to work properly at that point
> is to provide both "-I /usr/i686-pc-cygwin" and "-I /usr/include/g++-3".

Thanks for the information. However, I don't see anything wrong with
your setup, so we'll just have to do some experiments and track it 
down.

I noticed that you've set up the mount table to mount the various
drives as /<drive_letter>, which should be fine. Also, PWD is set 
to /i/CPP/hello, which means you're working on a remote drive at 
this point, and your "home" directory is also on a server ie remote 
drive /h.

Could you please do the following -- run the same testcase on a local
drive and see if the problem is repeatable. I'd like to remove as many
variables as possible, and that may help tracking this down. As you
can imagine, lots of use GCC and we don't see this problem.

I think the `invalid argument' is simply a misleading error message,
and the real error is still lurking in there. The final experiment
will be to run the compilation under `strace', but that's going to
generate a *huge* log file and I'm trying to avoid that.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com