Mail Archives: cygwin/2000/04/26/22:26:49
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
- Raw text -