On 9 Nov 01, at 18:06, J. David Bryan wrote:
On 9 Nov 2001, at 20:36, Prof Abimbola Olowofoyeku wrote:
On 9 Nov 01, at 12:35, J. David Bryan wrote:
just to have, e.g., "collect2" in the right places.
Not just for collect2.
N.b.: "e.g." ;-)
e.g., everything else (cpp0, cc1, libgcc.a, etc.).
That does not seem reasonable.
Reasonable or not, that is the way it is.
Why should that be a requirement? Why would it matter, for example, that the 2.95.3 version of the C compiler is called when the 2.8.1-based version of GPC needs to compile a C program? Or that the 2.95.3 version of collect2 is called to link files generated by a 2.95.2 version of GPC?
It would matter because the target machine and target version are hard coded into the driver program, and the driver program uses the target version as the basis for locating the C program files. I think I explained this in my last two posts. Why this should be so is not the issue. It seems that it is so, and has been so for a long time. I am not sure that the gcc guys will change gcc in this respect just to accommodate our special needs here.
So, ISTM that, if gpc is to be merged with gcc eventually, that behaviour will have to remain (Frank or Peter can tell whether this is correct or not). If gpc will engage in "non standard" behaviour (by looking for files elsewhere) then it seems that the gpc driver program needs to be patched with something *additional* to the normal gcc behaviour (as opposed to replacing the normal gcc behaviour). That is why I asked whether we could add an environment variable to do this. It may well be that the "COMPILER_PATH" variable that Frank referred to already does this - but I haven't checked this yet.
What version dependencies exist?
Type "gpc -print-search-dirs" and you will see where it looks for its gcc executables. It is exactly the same place as gcc (try "gcc -print- search-dirs"). You will see that the hard coded paths contain the target compiler version also hard coded.
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm Email: African_Chief@bigfoot.com