On 9 Nov 2001, at 20:36, Prof Abimbola Olowofoyeku wrote:
That functionality is already present with GCC_EXEC_PREFIX.
As far as I understand, it isn't - or maybe my understanding is just wrong.
[...]
In this case, if my understanding is correct, then setting GCC_EXEC_PREFIX gets you nowhere - because the target version that ends the concatenated path still points to "2.95.2".
Actually, it tries the GCC_EXEC_PREFIX both with and without the machine and version number. Try setting GCC_EXEC_PREFIX to "/aaa/bbb/" for example, and then do:
gcc -print-search-dirs
You'll note that the "programs" and "libraries" searches are done first with "/aaa/bbb/i686-pc-cygwin/2.95.2/" and then with "/aaa/bbb/" (among other variations).
So setting GCC_EXEC_PREFIX to:
"..../gcc-lib/i686-pc-cygwin/2.95.3-2/"
will try "..../gcc-lib/i686-pc-cygwin/2.95.3-2/i686-pc-cygwin/2.95.2/", which will fail, and then will try "..../gcc-lib/i686-pc-cygwin/2.95.3-2/", which will succeed.
I don't know how the "specs" file is built. But isn't it the case that this is built from the same place as the gcc specs file is built?
Specs is built essentially by doing:
gpc -dumpspecs > specs
or
gcc -dumpspecs > specs
If GPC and GCC have different internal specs and specs processing, then they are not interchangeable.
-- Dave