[3238] in SIPB bug reports
Re: vax Ultrix (patriot) sipb binaries
daemon@ATHENA.MIT.EDU (mhpower@Athena.MIT.EDU)
Fri Oct 9 20:20:52 1992
From: mhpower@Athena.MIT.EDU
To: basch@Athena.MIT.EDU
Cc: sipb@Athena.MIT.EDU, bug-sipb@Athena.MIT.EDU
Date: Fri, 09 Oct 92 20:15:47 EDT
>Actually, most "vax_bsd43" binaries will simply run on "vax_ul4" ...
That's great, assuming it doesn't take much longer to check this, than
it does to just build the program on a vax_ul4 machine. How do we tell
if it's going to work? If a binary runs at all, is it then obvious
that it's OK? Or would we need to test all paths through the code?
Is there any way to find out directly (other than reading Ultrix
kernel or library sources, which most of us can't get to)? Can someone
write a perl script to grovel through the binary and spit out 'yay' or
'nay'? Will vax_bsd43 binaries run if and only if they never do DNS
resolver stuff? Are there specific system calls that must not be used?
(Any further mail should probably go to bug-sipb, since this is
now mostly about maintaining software in the sipb locker.)
Matt