On 7 Nov 2001, at 9:53, Pierre Muller wrote:
[...]
But I still get a problem, cpp0 executable is not found... is that an alias of cpp ??
$ gcc -v Reading specs from /bin/../lib/gcc-lib/i686-pc-cygwin/2.95.3-5/specs gcc version 2.95.3-5 (cygwin special)
$ gpc -v Reading specs from /usr/local/lib/gcc-lib/i686-pc-cygwin/2.95.3/specs gpc version 20010623, based on 2.95.3 20010315 (release)
You basically have a broken gpc installation. Your gcc version ("2.95.3- 5") does not match your gpc version ("2.95.3"). So gpc cannot find the files it needs. This is actually the *real* cause of all the problems that you have been experiencing (including with "as"). Also, your gcc and gpc seem to be installed in different places. Until you fix this, you will get other problems - especially when it comes to linking (e.g., it won't find "collect2.exe").
The easiest solution that I can see is to copy cpp0.exe, cc1.exe, and collect2.exe from the gcc "...i686-pc-cygwin/2.95.3-5/" directry to the gpc "...i686-pc-cygwin/2.95.3/" directory. There are other possible solutions - e.g., get (or build) the correct gcc version (i.e., just plain "2.95.3", without the "-1" or "-5" suffixes). Possibly another solution is to set the GCC_EXEC_PREFIX or GPC_EXEC_PREFIX environment variables - but I am not sure whether this will help.
It is a problem for GPC that Cygnus keeps adding these suffixes. I can understand why, and I am sure that they are justified to do so - but it does mean that it is more likely than not, that gcc and gpc versions will not match, unless each person builds gpc for himself to match the exact suffix of the gcc version (and then everytime you upgrade your gcc, you will need to rebuild the gpc driver program).
Frank, is there a cleaner solution to all this? For example, can we introduce an optional environment variable which the gpc driver program will look for (e.g., "INSTALLED_GCC_VERSION=2.95.3-5") and then be able to find the other executables that it needs?
I can of course patch gpc.c myself to do this under Cygwin and Mingw - but it might be useful for other platforms as well.
To the African Chief, maybe it would be nice to add some script that could find out in which mode the /usr/local/lib/.... dir is mounted and modify specs files accordingly !
This is a red herring. Like I said, the real cause of your problems has been identified above. If the directory paths were correct, then gpc would probably have used your gcc "specs" file instead of its own.
Best regards, The Chief --------- Prof. Abimbola Olowofoyeku (The African Chief) Author of Chief's Installer Pro for Win32 Email: African_Chief@bigfoot.com http://www.bigfoot.com/~african_chief/