According to Laussy Fabrice:
Hmm... I can't seem to find a patch in there anywhere.
Maybe it's `/usr/local/gcc-2.7.2.1/p/diffs/gcc-2.7.2.x.diff' in your distribution?
There is only gcc-2.7.2.x.patch. There is no 2.7.2.1 once unpacked the archive,
Ah - that's correct! The documentation is outdated here, sorry.
there is no anymore after running ./configure.
That should not happen! Please re-extract it from your GPC distribution archive.
Here is how it should work (for gpc-98something):
esmeralda/usr/local/src/gcc-2.7.2.1# ./configure This appears to be a i586-unknown-linux system. Using `./config/i386/i386.c' to output insns. Using `./config/i386/i386.md' as machine description file. Using `./config/i386/linux.h' as target machine macro file. Using `./config/i386/xm-linux.h' as host machine macro file. Merged x-linux. *** *** configure detected GCC version 2.7.2.1 *** GPC 2.1 requires a patch to build with GCC 2.7.2.1 *** This patch will now be applied. *** Press ENTER to continue, Ctrl-C to abort. ***
Merged c++ pascal fragment(s). Created `./Makefile'. Merged x-linux. Created `cp/Makefile'. Merged x-linux. Created `p/Makefile'. creating cache ./config.cache [...] creating gpc-config.h Links are now set up to build a native compiler for i586-unknown-linux. esmeralda/usr/local/src/gcc-2.7.2.1#
However, as you know, I cannot create the 2.7.2.1 patch. Incorrect path.
Of course you cannot create it. You need the patched and the unpatched files in order to create the patch.
Frank Heckenbach wrote:
It should be included in libgpc.a -- did you check that the version you use is the correct one (and not perhaps an older version is laying around somewhere else; perhaps try "locate libgpc.a" if that's set up to work on your system, and remove any old version it finds).
I have make clean and make clean-dist, + remove my symbolic link of old GPC in my own /bin.
In fact, I assume my failure on patching GCC explain the problem (there is some other problems not when compilating but when running).
Normally, the patched GCC source files do not affect `libgpc.a', but obviously something went completely wrong with the configuration of your GPC source tree, so maybe `libgpc.a' was not produced due to some missing makefile or whatever.
Good luck,
Peter