Andris Pavenis wrote:
On Friday 02 November 2001 03:10, Frank Heckenbach wrote:
It would appear that in the Host <> Build case, the definition override:
GPC_FOR_TARGET = ix86-pc-mingw32msvc-gpc
...should appear in the top-level makefile.
AFAICS there are at least 3 ways to solve it:
- Set GPC_FOR_TARGET on the command line. That's what I'm doing, and it works. But it's not optimal since it could be done automatically.
It did not work for me unless I added GPC_FOR_TARGET to the flags to pass to submakes (my experience with building gcc-2.95.X together with GPC for DJGPP) as far as I remember
Convince the GCC people to set GPC_FOR_TARGET in the top level makefile. Someone who is in contact with them (e.g., Peter, not me) could try this.
Forget about GPC_FOR_TARGET, and use GCC_FOR_TARGET with s/gcc/gpc/ (e.g., ./xgcc -> ./xgpc, /usr/bin/foo-bar-baz-gcc -bqux -> /usr/bin/foo-bar-baz-gpc -bqux). Does anyone see a situation where this would fail? (Though the second one is probably the cleaner solution.)
If it's possible, then I would prefer this way (at least for now while GPC is still a separate package) as it would not require to do anything with top level Makefile. Perhaps it is necessary to test this way to see whether it's not breaking anything.
I've tried this on a couple of systems now, and didn't find a reliable way to do it.
The problem is that the prefix directory may contain `gpc' and or `gcc' (e.g., some people might build the whole stuff in a `gpc' directory, and with gcc-2.95.x it's always in a `gcc' subdirectory). These must not be changed, of course -- neither in the (possible) path to xgcc, not in the (possible) `-B' option.
Replacing only the executable name seems quite hard to do, assuming only a "stupid" (i.e., non-GNU ;-) sed. (I've had bad experiences with other seds, e.g. the Solaris one doesn't even support full regular expressions.)
So, if you have any good suggestion how to do it, let me know. Until then, I'll undo the change, and GPC_FOR_TARGET will have to be set otherwise.
Frank