Tue Nov 30 23:39:00 GMT 1999
Mike MacDonald <email@example.com> writes:
> Ok, I got man working.. I'm not going to worry about 2.95 until I have
> time.. 2.91 is compiling fine for me..
There is no version 2.91 -- I assume you mean 2.91.xx, xx <= 66 (eg.,
2.91.66 corresponds to egcs-1.1.2 if I remember correctly; gcc -v
will provide the correct info).
The problem with -remap is always due to the following -- compiler driver
from a newer GCC distribution executing CPP from an older GCC distribution
by mistake. The cause can be one of the following:
- you have GCC_EXEC_PREFIX defined incorrectly (if so, undefine it
and see what happens).
- you have GNAT installed. See my web page for workaround.
- inconsistent mount. This is the tricky one, since you have
to know how GCC looks up subprograms given it's installation directory.
Let's say you've mounted the /Cygnus/cygwin-b20/H-i586-cygwin32/bin
as /bin; now you run the following:
$ gcc -v
gcc will now look in the PATH, and find itself in /bin/gcc.exe; it'll
now try to find it's subprograms in /bin/../lib/gcc-lib/, and will
fail if you haven't mounted /lib as well.
The workaround is to put /Cygnus/cygwin-b20/H-i586-cygwin32/bin in your
PATH *before* /bin.
I seem to remember that you had trouble when you hardcoded CC=/bin/gcc
in your Makefile; I'd bet the last one biting you. My opinion of this
behaviour is that it's not a bug, rather an annoying side-effect of the
rather bizarre directory hierarchy chosen by Cygnus. I haven't looked
at the CD yet to see what's used there.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org
More information about the Cygwin