🚀 go-pugleaf

This is almost surely something bogus that I did, but I'm hoping
someone can spare me a couple hours of gcc debugging:

I'm trying to build gcc 2.4.3.1 on a Data General AViiON 300 series
running DG/UX 5.4 R2.01 (yes, I remembered to use sde-target(1)).
Everything goes great until I try to make install-libobjc:

	/tmp_mnt/gnu/gcc-2.4.3.1/xgcc -B/tmp_mnt/gnu/gcc-2.4.3.1/ `cat fflags` -c  -DIN_GCC -D_M88KBCS_TARGET  -g -O -I. -I.. -I/tmp_mnt/gnu/gcc-2.4.3.1 -I/tmp_mnt/gnu/gcc-2.4.3.1/config /tmp_mnt/gnu/gcc-2.4.3.1/objc/sendmsg.c
/tmp_mnt/gnu/gcc-2.4.3.1/objc/sendmsg.c:99: warning: #warning performv:: will not work
/tmp_mnt/gnu/gcc-2.4.3.1/objc/sendmsg.c: In function `objc_msg_sendv':
/tmp_mnt/gnu/gcc-2.4.3.1/objc/sendmsg.c:100: incompatible type for argument 3 of indirect function call
*** Error code 1

Not caring much about Objective C, I ignore the errors.  Then I try to
compile a C program.  If TARGET_BINARY_INTERFACE is set to m88kbcs,
everything works fine.  In the default environment, though, I get

ld: /usr/local/lib/gcc-lib/m88k-dg-dgux/2.4.3/m88kdgux.ld: fatal error:
file type unknown to the library used by ld

Which appears to be coming from the m88kdgux ld.  So is there some
magic I can use on the m88kdgux.ld file or pass to ld to convince ld to
(not) use it?  I'm reasonably sure the 2.3.3 compiler worked under
R2.01, but I know I built it under a previous OS rev.

Can anybody help?  (Please respond via e-mail.  I don't get the
newsgroup and I'll summarize if there's interest.)

                                Doug Becker
                                dbecker@legato.com