libtool 1.5.20, Solaris, linking in static libraries into the shared libraries

2005-10-31 Thread Pooh
Excuse me, i have forgotten the attach in last message, now i resend. Good day! There is a following problem using CC v5.5 (v5.6 from Studio 10 does show the same behaviour). I compile the sources (attached). test1 prints the message, while test2 doesn't. That is because when we compile stati

Re: libtool 1.5.20, Solaris, linking in static libraries into the shared libraries

2005-10-31 Thread Ralf Wildenhues
Hi Yuri, * Pooh wrote on Mon, Oct 31, 2005 at 11:31:24AM CET: > > There is a following problem using CC v5.5 (v5.6 from Studio 10 does > show the same behaviour). > I compile the sources (attached). > test1 prints the message, while test2 doesn't. > > That is because when we compile static libr

Re: libtool 1.5.20, Solaris, linking in static libraries into the shared libraries

2005-10-31 Thread Pooh
Ralf Wildenhues wrote: (Side note: you mean what in Libtool lingo is called a `convenience archive' rather than a static library; the objects in the archive contain position-independent code, PIC). Oh, yes. I remember that one. libtool --mode=link CC -rpath /tmp -o libcon2.la dummy.lo

Re: libtool 1.5.20, Solaris, linking in static libraries into the shared libraries

2005-10-31 Thread Ralf Wildenhues
Hi Yuri, * Pooh wrote on Mon, Oct 31, 2005 at 03:38:52PM CET: > Ralf Wildenhues wrote: > > > >>libtool --mode=link CC -rpath /tmp -o libcon2.la dummy.lo libcon.la > >>It becomes: > >>CC -G -hlibcon2.so.0 -o .libs/libcon2.so.0.0.0 .libs/dummy.o -Qoption > >>ld -z -Qoption ld allextract,./.libs/l