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
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Wed, 26 Apr 2000 23:27:06 -0400
To: "'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
Message-ID: <20000426232706.A28782@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cgf AT cygnus DOT com,
	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
References: <7B4C28C84831D211BFA200805F9F34567030F5 AT nswcdlvaex04 DOT nswc DOT navy DOT mil> <Pine DOT HPP DOT 3 DOT 96 DOT 1000426145016 DOT 12100G-100000 AT hp2 DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.12i
In-Reply-To: <Pine.HPP.3.96.1000426145016.12100G-100000@hp2.xraylith.wisc.edu>; from khan@NanoTech.Wisc.EDU on Wed, Apr 26, 2000 at 02:56:21PM -0500

I've just seen a problem in cygwin that could account for this behavior.
It would be interesting to see if tonight's snapshot improves this
behavior.

http://sourceware.cygnus.com/cygwin/snapshots/

cgf

On Wed, Apr 26, 2000 at 02:56:21PM -0500, Mumit Khan wrote:
>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
>

-- 
cgf AT cygnus DOT com                        Cygnus Solutions, a Red Hat company
http://sourceware.cygnus.com/         http://www.redhat.com/

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