Re: Linking custom library problem

[Sebastien Pierre]

Hi Nicola!

Le mer 26/02/2003 à 18:53, Nicola Pero a écrit :
 
> For example,
> 
> cd {wherever exampleTests is}
> ldd exampleTests

My exampleTests does not generate an executable, as it not able to find
osip symbols.

> Then, try doing
> 
> cd {wherever libPSS.so is}
> ldd libPSS.so

I tried it, and the result is:

<snip>
ldd
/mnt/projects/SIP/PSS/shared_obj/ix86/linux-gnu/gnu-gnu-gnu/libPSS.so
        libPiranhas.so.1 =>
/usr/GNUstep/Local/Libraries/ix86/linux-gnu/gnu-gnu-gnu/libPiranhas.so.1
(0x40016000)
        libosip-0.9.4.so.0 => /usr/local/lib/libosip-0.9.4.so.0
(0x40027000)
        libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
</snip>

So I guess that libosip does not contains (or exports ?) the symbols I
need -- I tried to make a `grep osip_init
/usr/local/lib/libosip-0.9.4.so.0', but this did not match anything... I
searched for a utility to list symbols in a shared object, but was not
able to find a command that would do that :/

I wrote a simple example in C, and compiled it with gcc -losip, and it
did not find the required symbols either... I will try to dig this out,
but as I'm not very familiar with this kind of issues, any help would be
appreciated :)

Cheers,

  -- Sebastien