Date: Wed, 23 Nov 1994 11:54:23 +0900
From: Stephen Turnbull <turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp>
To: pgeiss AT dali DOT uphys DOT uni-heidelberg DOT de
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: cannot link with djgpp1.12

Tom Brosnan and I had exactly this problem with Ghostscript 3.x.

You can work around it by stubediting ld 2.4 to use GO32 v1.11.maint3.
I assume other patchlevels of GO32 v1.11 will work, that's just the
copy I had on hand and was successful with.

Procedure:
1.  Get a copy of a v1.11 GO32.EXE, put it on your path wherever your
GO32 usually lives, and name it GO1_11M3.EXE or (something similarly
not GO32).
2.  execute "stubedit ld.exe" in the djgpp/bin directory (or wherever
you keep the compiler executables).  Answer "name of extender" with
the name you used in step 1 (you don't need the ".EXE") and "version
required" with "1.11".  (You could specify the patchlevel as well, but
you may want to try a couple of different patchlevels and this would
cost a few extra keystrokes everytime forthe ".maint3" part of the
version string.)  The rest of the questions should be defaulted by
hitting return.

The Ghostscript build produces more than 200 object files, so your
puny (that's a joke :) program should link OK with a stubedited ld and
v1.11 GO32.  If you really want to be careful and use this version
only explicitly, you could produce a stub which uses the v1.11
extender and executes ld.exe and call it bigld.exe, but that would
break most makefiles (you couldn't use "gcc -o $(COFFFILE) $(OBJECTS)").
    --Steve