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. Why this should be so is not the issue. It seems that it is so, and has been so for a long time.
Not really hard-coded. They can be overwritten with `-b' and `-V', respectively. But I don't think that's the way to go 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.
In fact, that's an issue. The more we change in the driver, the harder integration will become. So, provided `COMPILER_PATH' and `LINKER_PATH' will work, I don't feel like adding any other ways. It's not that much of a difference having to set one or two environment variables.
Frank