This is the mail archive of the
mailing list for the Cygwin project.
RE: Weird behavior when using "-I" with gcc-2.95.2
- To: "'Mumit Khan'" <khan at NanoTech dot Wisc dot EDU>, Fontenot Larry A DLVA <FontenotLA at NSWC dot NAVY dot MIL>
- Subject: RE: Weird behavior when using "-I" with gcc-2.95.2
- From: Fontenot Larry A DLVA <FontenotLA at NSWC dot NAVY dot MIL>
- Date: Thu, 27 Apr 2000 09:01:22 -0400
- Cc: "'cygwin at sourceware dot cygnus dot com'" <cygwin at sourceware dot cygnus dot com>
Well that was very interesting. Everything compiles just fine on the local
hard disk when using the "-I ./". So then I tried my H:\ drive. That is a
drive I have mapped from a WinNT server. Once again, everything works just
fine. So then I went to my I:\ drive, which is a Sun Solaris file server
using SunLink software to emulate a WinNT server. That is when I start
having problems. Apparently, gcc is seeing something differently when
compiling on my I:\ drive. Should I try to use strace at this point to find
out what the difference might be?
From: Mumit Khan [SMTP:khan@NanoTech.Wisc.EDU]
Sent: Wednesday, April 26, 2000 3:56 PM
To: Fontenot Larry A DLVA
Subject: RE: Weird behavior when using "-I" with gcc-2.95.2
On Tue, 25 Apr 2000, Fontenot Larry A DLVA wrote:
> Attached is the requested bug.txt. It looks as though the default
> paths are still valid. And everything works just fine until I add
> anypath". The only way to get the compiler to work properly at
> is to provide both "-I /usr/i686-pc-cygwin" and "-I
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
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
Could you please do the following -- run the same testcase on a
drive and see if the problem is repeatable. I'd like to remove as
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.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org