First of all I'd like to thank everyone who took the time to answer me.
Dr Thomas.Blinn_at_HP.com [tpb_at_doctor.zk3.dec.com]
andy.wagg_at_gb.schneider-electric.com
Romani, Roberto [roberto.romani_at_hp.com]
Brad Bell [brad_at_vaxxine.com]
william_f_fiore_jr_at_speakeasy.net
Situation: We have a static library (.a) compiled for Tru64 V5.1 which we
want to run under V4.0.
Problem arises at link time when trying to link to _F64_stat and _F64_fstat
system functions, which do not exist under V4.0.
All comments agree that we should either upgrade the system to V5.1 or ask
for a V4.0 version of the library to the third party vendor, and that is
what we are doing right now. Trying to force-link against a local version of
the stat functions, or even run the compiled code aimed for V5.1 could have
unpredictable results in V4.0.
So that is what we are pressing for now.
Thanks to everyone for sharing your thoughts.
Eduardo.
============================================
Dr Thomas.Blinn_at_HP.com [tpb_at_doctor.zk3.dec.com]
...
Tru64 UNIX never claimed that a third party or a customer could
build an application or a library on a V5.x system and have it
work correctly on V4.0x. Sometimes you get lucky, but most of
the time you do not.
============================================
andy.wagg_at_gb.schneider-electric.com
...
Unfortunately, you are correct in the two possibilities. Either your
library needs to be built on V4.0 or you need to upgrade to V5.1. Operating
system releases are usually upwardly compatable, i.e. something built on
V4.0 is very likely to work on later versions. However, they are not
backward compatible across major versions, something built on V5.1 won't
work on V4.0. As in this case your libraries reference symbols that exist
ib V5.1.
=============================================
Romani, Roberto [roberto.romani_at_hp.com]
...
_F64_fstat() syscall was created to support the new stat structure which has
larger st_blksize and st_blocks fields to support filesystems greater than 1
terabyte.
Your only two options which you have stated are not viable are:
1. Get a v4.0 version of the library from Cisco
2. Move to V5.x Tru64 Unix.
Sorry I couldn't help further
=============================================
Brad Bell [brad_at_vaxxine.com]
...
You cannot take a library or binary compiled
on a newer version and expect it to work on an older. (This is
especially true of 5 -> 4 versions, since many system calls were
updated in the runtime libraries.).
I would contact cisco and ask them for 4.0 compiled libraries. They
should have them available... If not you may have to do some begging
for source...
Received on Fri Mar 11 2005 - 19:40:37 NZDT