My original question(s):
>I was just trying to install motdueco02123v32, a patch on Motif for osf v3.2
>(on my alpha 3000/300) and it bombed. It appears that the install script
>was looking for a file named 3133 - perhaps not incidentally one of the values
>returned by the checksum.
>Has anyone else bothered to try installing this patch? Has it worked for you?
>On a related note, has anyone else experienced problems with dxnotepad dying
>after a save? Or xtpu dying after an open/save? Nobody had when I asked
>before, but I figured tincture of time may have changed that.
I got three responses:
Bob Sloane <SLOANE_at_KUHUB.CC.UKANS.EDU>
wwcoot_at_lpdwhy.bhp.com.au (Tim Cook)
Marc_Hache_at_MBnet.MB.CA (Marc Hache)
Bob pointed out that:
>The INVENTORY file in the distribution is incorrect. It should be:
>60492 libXm.a /usr/lib/libXm.a bin:bin 644
>24297 libXm.so /usr/shlib/libXm.so bin:bin 644
I was able to install the patch with the revised INVENTORY file - but it didn't
solve my dxnotepad/xtpu problem.
Tim said:
>We have experienced this problem with dxnotepad on OSF/1 V3.2. The
>first workaround DEC provided was to use the binary from V3.0. This
>works and we continue to go with it. The second workaround DEC
>supplied was a replacement for /usr/shlib/_null/libXm.so. This came
>initially with incorrect instructions, and no official documentation,
>so I have not used it so far.
Fortunately, one of our machines had not been upgraded, so I grabbed the
3.0 binaries for dxnotepad and dxcalendar (which dies under year view) and
put them on our other machines. Using the old binaries seems to be the most
convenient solution to the problem.
Muchas Gracias, all
-amy
__________________________________________________________________________
Amy Skowronek Solar Data Analysis Center
amy_at_aloha.gsfc.nasa.gov NASA/Goddard Space Flight Center
Received on Thu Jun 15 1995 - 21:59:22 NZST