_F64_stat unresolved in libc.a for pre-V5.1 O/S

From: Richard Bemrose <rb3_at_sanger.ac.uk>
Date: Mon, 26 Mar 2001 12:40:14 +0100 (BST)

Hi all,

We are slowing migrating to Tru64 V5.1+ and during this process
re-compiling selective applications. One application compiled on Tru64
V5.1 reports unresolved symbols when executed on Tru64 pre-V5 O/S.
For example,

Tru64 V5.1:
===========
# odump -Dl /problematic/application
                        ***LIBRARY LIST SECTION***
        Name Time-Stamp CheckSum Flags Version
/problematic/application
        libX11.so Oct 29 14:22:44 2000 0xe862aa18 0
        libdnet_stub.so Aug 25 01:59:17 2000 0x9408a36b 0 osf.1
        libm.so Aug 25 01:54:01 2000 0x07757304 0 osf.1
        libc.so Dec 1 21:02:33 2000 0xe816efbe 0 osf.1

# nm -gAB /usr/lib/libc.a | grep "T _F64_stat"
/usr/lib/libc.a:f64_stat.o: 0x00000000000010 T _F64_stat
/usr/lib/libc.a:f64_statfs.o: 0x00000000000010 T _F64_statfs

Tru64 V4.0D:
============

# odump -Dl /problematic/application
                        ***LIBRARY LIST SECTION***
        Name Time-Stamp CheckSum Flags Version
/problematic/application
        libX11.so Oct 29 14:22:44 2000 0xe862aa18 0
        libdnet_stub.so Aug 25 01:59:17 2000 0x9408a36b 0 osf.1
        libm.so Aug 25 01:54:01 2000 0x07757304 0 osf.1
        libc.so Dec 1 21:02:33 2000 0xe816efbe 0 osf.1

# nm -gAB /usr/lib/lib*.a | grep "F64_stat"
(no output)


How do we progress from here?

  1) *(preferred solution)* resolve these unresolved symbols eg _F64_stat
  2) recompile on V5.1 with "-expect_unresolved pattern" flag to cc
     (see man cc)
  3) compile application on both pre-V5 and V5.1 O/S and use wrapper
  4) err..

Thank you.


Regards,
Rich

Dr Richard Bemrose | The Sanger Centre | Email: rb3_at_sanger.ac.uk
Senior Systems Admin. | Genome Campus | Tel: +44 (0)1223 494798
Special Projects Team | Hinxton, Cambridge | Fax: +44 (0)1223 494919
Systems Support Group | CB10 1SA, UK | http://www.sanger.ac.uk
Received on Mon Mar 26 2001 - 11:41:06 NZST