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: Fontenot Larry A DLVA <FontenotLA at nswc dot navy dot mil>
- Subject: Re: Weird behavior when using "-I" with gcc-2.95.2
- From: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Date: Tue, 25 Apr 2000 14:37:58 -0500
- cc: "'cygwin at sourceware dot cygnus dot com'" <cygwin at sourceware dot cygnus dot com>
Fontenot Larry A DLVA <FontenotLA@NSWC.NAVY.MIL> writes:
> Well, the only solution I could come up with was to compile with the
> g++ -I /usr/i686-pc-cygwin/include -I./ -c hello.cpp
> I have since moved the contents of /usr/i686-pc-cygwin/bin,
> /usr/i686-pc-cygwin/include, and /usr/i686-pc-cygwin/lib to /usr/bin,
> /usr/include, and /usr/lib, respectively. I thought that might help, but I
> still need to compile with the following:
> g++ -I /usr/include -I./ -c hello.cpp
> I even tried reinstalling the entire cygwin set with the newsetup.exe. No
This is very odd indeed, and I wonder why gcc/cpp is producing the
`invalid argument' error!
Please provide a bit more info on your platform:
$ echo "g++ -I./ -c hello.cpp" > bug.txt
$ g++ -I./ -c -v -H hello.cpp >> bug.txt 2>&1
$ cygcheck -s -r >> bug.txt 2>&1
and post the resulting bug.txt file.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org