On 10 Nov 01, at 19:03, Frank Heckenbach wrote:
[...]
Prof Abimbola Olowofoyeku wrote:
Perhaps because, on many systems, users do not have write access to the "/usr" directory - and, in such cases, unless they can convince the sys admins to install stuff for them, they will be stuck.
Not at all. I've installed many GPCs in my home directories on Solaris, AIX and IRIX systems lately (and probably OSF next week :-). All configured with --prefix=$HOME/usr and no further problems with the dirs.
That is exactly what I was referring to. The question was, why did the gcc people allow environment variables to change the default search paths.
[...]
The root of the problem seems to be the use of a patched GCC and a non-GCC-patched GPC (without installing the non-patched GCC in parallel). This is a "broken" GPC installation.
Yes.
You can avoid this (don't use the patched GCC, install two GCCs, try to install a GCC-patched GPC, ...), or you can use the environment variables provided for such "broken" installations ...
Yes.
So ... what's the problem, anyway?
IIRC, David's problem/query was: why should a gpc distro based on a certain gcc version require the same version of gcc? and, if it does require it, then that does not "seem reasonable".
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