Filename: unstable/binary-i386/devel/gpc_2.0-3.deb
^^^^^^^^ Thank you very much ;-)
Obviously, the `gpc' driver program cannot locate the library `libgpc.a'. From the installation log I have the impression that you did not install `libgpc.a' but a file named `libgpc2.a'. Perhaps both are the same, and it suffices to link `libgpc.a' to `libgpc2.a' in your `/usr/lib/' directory or whereever you keep your libraries?
The instalation does not provide any "libgpc.a", only "libgpc.so.2".
Did you symlink libgpc.so -> libgpc.so.2 (or whatever the exact libname is) ?
I played with a shared RTS library in some pre-2.0 beta's but decided not to put it in the 2.0 release because it would require libgpc.so to be distributed with all GPC compiled programs and I feared confusion. Assuming you don't have one of these beta's (they had 96XXXX version numbers), my guess is that the Debian maintainer clameter@debian.org decided to put this feature back in. Maybe you should ask him.
Can I use some switch (-static or ...) to use libgpc.so.2 instead of libgpc.a?
No, -static would search for a (nonexisting) libgpc.a
If all else fails, you may have to link /usr/lib/gcc-lib/i386-linux/2.7.2.1/libgpc.a -> /usr/lib/libgpc.so.2, but that's very cruel :-(
Thank you for your help.
Happy hacking,
JanJaap