🚀 go-pugleaf

We don't run the DECwindows or DEC Motif stuff here, but recently I
helped out some folks in another department who had your exact same
problem.

Here's what I think happened, and what you can do to fix it. 
When you loaded Ultrix and Motif I think you did this: 

Loaded the default DECwindows subset 	  UDWXDEV420
Loaded the DEC Motif 1.1.3 subset    	  DXMXM113
( then, saw the MIT R4 stuff in the Unsupported and...)
Loaded the Unsupported X11 R4 Components  ULXUNMIT420

So, here's what happened with regards to your linking X libs of
	-lXm -lDXm -lXt -lX11 

-lXm links to the DEC Motif libXm.a
-lDXm links to the DEC Motif libDXm.a 
-lXt links to the UNSUPPORTED libXt.a which CLOBBERED the
     DEC Motif supplied libXt.a  <<< ERROR, DOES NOT WORK >>>  
-lX11 links to the DECwindows -lX11 because the MIT one is named
      -lX11-mit.

A listing from setld confirms the fact the the Unsupported MIT
setld clobbers the DEC motif libXt.a

DEC Motif X11 libs:	MIT Unsupported X11 libs:
/usr/lib/libX11.a	/usr/lib/libX11-mit.a
/usr/lib/libXm.a	
/usr/lib/libXmu.a	/usr/lib/libXmu.a
/usr/lib/libXt.a	/usr/lib/libXt.a

So actually you have two clobbered Motif libs: -lXt and -lXmu

To fix it we did this:

Move /usr/lib/libXt.a to /usr/lib/libXt-mit.a and
     /usr/lib/libXmu.a to /usr/lib/libXmu-mit.a
Re-install the Motif development subset again. Which is named
DXMXM113  OSF/Motif Development Env. (RISC)

I am pretty sure this will fix your problem. At this point
I suggested a move to public domain MIT X11R5 and a purchase
of OSF's Motif. This value added stuff X11 stuff should be
scrapped. It makes life more difficult than it has to be.
Let me know if this works for you. 

 Paul Tatarsky         email: paul@cse.ucsc.edu
 UC Santa Cruz
 CIS/CE Board          
 Technical Staff