On 7 Nov 2001, at 11:38, Prof. A Olowofoyeku wrote:
You basically have a broken gpc installation. Your gcc version ("2.95.3-5") does not match your gpc version ("2.95.3").
I'm not sure I see why this should be considered a requirement. This would imply that if I wanted to test out GPC compilers based on 2.95.3, 2.95.2, and 2.8.1, I would need to install corresponding implementations of GCC, just to have, e.g., "collect2" in the right places. That does not seem reasonable.
I understand that GPC defaults to looking the in the same place for all tools, but that should be alterable by environment settings, and doing so should not be considered "fixing a broken installation." It's merely creating an *alternate* installation.
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?
That functionality is already present with GCC_EXEC_PREFIX.
If the directory paths were correct, then gpc would probably have used your gcc "specs" file instead of its own.
But then that would have caused another problem. There are (or at least were, the last time I checked) Cygwin-specific parameters in the specs file supplied with the Cygwin version of GCC, e.g., "%q". GPC will choke on these.
-- Dave