Thanks to
John Francini
Mike Iglesias
Dr. Thomas P. Blinn
A clearer indication of the opsys version is in /etc/motd. Another
suggestion was /var/adm/messages, but we lacked privilege for that, or
uerf (my first attempt).
I'm pretty sure the author used standard C routines, and it's a 50-50
chance he used no Motif/Xt/Xlib routines newer than this target host's
distribution, so he'll probably try once or twice to compile on this older
system.
On Thu, 10 Dec 1998, Edwin R Wolfe Jr. wrote:
> One of our users has exported the executable of a C program to
> colleagues at another site. Attempting to run it begets the error:
>
> pid:/path/to/myprog: /sbin/loader: Fatal Error: Main's RLD_VERSION is 2,
> the correct Version should be 1. The command
> strings /sbin/loader
> finds this message.
>
> sizer -v on our system shows DU 4.0D. sizer -c shows cpu "DECST30"
> sizer -v doesn't work on theirs, but sizer -c shows cpu Dec 3000_500 and
> uname shows version 4 release 1.2. (this confuses me - does it mean they
> have ver 4.1.2? I thot the latest version was 4.0.E?. But their vmunix
> was created in 95, so I'm sure our system is newer.)
>
> The program uses Motif/XWindows to display images, and the Motif versions
> are different:
> strings /usr/shlib/libXm.so |grep -i version
> finds
> OSF/Motif Version 1.2.4
> on our machine, but no version # on theirs.
>
> I rather doubt it, but I thot I'd ask if there is any hope of (reasonably
> easily) generating an executable on our machine that will run on theirs
> (we hesitate to release the sources)?
>
Received on Thu Dec 10 1998 - 23:10:46 NZDT