Bob Harris
*nix forums beginner
Joined: 23 Mar 2005
Posts: 39
|
 Posted: Wed Mar 30, 2005 12:34 am Post subject:
Re: Binary compatibility
|
|
|
In article <40c9e591.0503290829.109003d@posting.google.com>,
the_edge123.nospam@club-internet.fr (Fabien R) wrote:
| Quote: | Hello,
May a binary generated on a DEC OSF/1 V4.0 run safely on a Tru64 v4.0F OS ?
Regards,
Fabien
|
was it safe before?
Generally speaking the Tru64 UNIX developers attempt to allow
executables compiled on older versions of the operating system to run,
unmodified, on newer versions of the OS.
The exception to this is device drivers or any kernel loadable module.
These may need to be re-compiled for a major release (like going from v4
to v5).
If your v4.0 executable does not run, then you should file a bug report.
Bob Harris
X-Digit who spent over 6 months
making sure stat(), lstat(),
fstat(), statfs(), fstatfs(),
getmntinfo(), and getfsstat()
worked for v5.0 as well as all
pre-v5.0 releases of Tru64 UNIX
(aka Digital UNIX, aka Digital
OSF/1). This included
dynamically linked, statically
linked, users of ftw(), users of
getcwd(), programs that used
syscall.h and syscall(), pass
the X/Open standards tests, and
worked for Digital C, C++, as
well as gcc and g++. And in
addition to the work that went
into v5.0, there were several
bug fixes for situations that
cropped up after v5.0 shipped.
Tru64 UNIX developers have always
strived to make sure that older
programs would continue to run
on newer versions of the OS.
Disclaimer:
Your Mileage may very.
Objects may be closer than they
appear.
I no longer work for HP, and in
no way do I speak for the
company! |
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index
»
*nix
»
Tru64
