On 9 Nov 2001, at 23:52, Prof Abimbola Olowofoyeku wrote:
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.
I'm afraid that you miss my point. There is no *requirement* to place the files where the driver program expects them. Adding the actual location to the path, for example, will work around this. So will employing GCC_EXEC_PATH or COMPILER_PATH.
What I thought you were asserting was that there was some fundamental requirement that (for example) GPC based on gcc-2.95.3 would only work properly if gcc-2.95.3 was also installed due to some inherent dependencies in the tools themselves and not merely due to where they are located. As far as I understand, there are no such dependencies. Yes, by default, the gpc and gcc driver programs will look in certain standard places for their tools, but existing methods are available that will allow the drivers to look elsewhere. Installing a full copy of a specific version of gcc *simply* to satisfy the defaults of the driver program is what I was stating was unnecessary.
As an example, my Windows system is set up with this directory structure:
E:\Programming\GNU --> gcc.exe, ld.exe, etc.
E:\Programming\GNU\mingw32\2.95.3-6 --> cc1.exe, cpp0.exe, etc.
E:\Programming\Pascal --> gpc.exe
E:\Programming\Pascal\i486-pc-mingw32msvc\2.95.3 --> gpc1.exe, etc.
With:
COMPILER_PATH=E:\Programming\GNU\mingw32\2.95.3-6 GPC_EXEC_PREFIX=E:\Programming\Pascal\
...I can compile and link C and Pascal programs with GPC with no trouble.
Chief, I believe that we're arguing two different points here. :-)
-- Dave