Re: compile failure due to undefined symbol

[Nick Clifton <nickc at redhat dot com>]

Hi Daniel,

> Eww eww eww!  What, if anything, does this do to the installed
> libraries?

I think they are OK.  (I am not an expert in this area though, so please do 
correct me if I am wrong).  I tried running an installed executable and that 
worked:

  % cd shared-build/install/bin
  % ./objdump -f ./objdump
  ./objdump:     file format elf64-x86-64
  architecture: i386:x86-64, flags 0x00000112:
  EXEC_P, HAS_SYMS, D_PAGED
  start address 0x0000000000403370

And checking its dependencies:

  % ldd ./objdump
  libopcodes-2.18.50.20071002.so => 
/work/builds/binutils/current/shared-build/install/lib/libopcodes-2.18.50.20071002.so 
(0x0000002a95557000)
  libbfd-2.18.50.20071002.so => 
/work/builds/binutils/current/shared-build/install/lib/libbfd-2.18.50.20071002.so 
(0x0000002a956d1000)
  libc.so.6 => /lib64/tls/libc.so.6 (0x0000003d51f00000)
  /lib64/ld-linux-x86-64.so.2 (0x0000003d51d00000)

Plus running ldd on the installed library seemed to be OK:

  % ldd ../lib/libopcodes.so
  libbfd-2.18.50.20071002.so => 
/work/builds/binutils/current/shared-build/opcodes/../bfd/.libs/libbfd-2.18.50.20071002.so 
(0x0000002a956d1000)
  libc.so.6 => /lib64/tls/libc.so.6 (0x0000002a958ba000)
  /lib64/ld-linux-x86-64.so.2 (0x000000552aaaa000)

What else should I do to test the library ?

Cheers
  Nick