multi language branch (was: ltconfig decision in creating shared (c++) libraries on solaris.)

Hi, Alexandre wrote: > C++ support is under development in the multi-language-branch of the > libtool CVS tree. Feel free to give it a try, and please report any > problems you find. When running bootstrap on the sources from the multi-language-branch I get the following error messages: ca

Re: multi language branch (was: ltconfig decision in creating shared (c++) libraries on solaris.)

Hi, Sorry about the wrong PGP signature. Here is the corrected version: Alexandre wrote: > C++ support is under development in the multi-language-branch of the > libtool CVS tree. Feel free to give it a try, and please report any > problems you find. When running bootstrap on the sources from

libtool / C++ / inter library dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I am trying the following: Shared C++ Library liba.so, Shared C++ Library libb.so, libb.so depends on liba.so. Is this possible with any libtool/automake/autoconf version? I tried without success: Ma

RE: libtool / C++ / inter library dependencies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Ossama wrote: > > Result: > > > > - ->ldd libb.so > > liba.so.0 => ./liba.so.0 > > libstdc++.so.2.10.0 => (file not found) > > libm.so.1 => /usr/lib/libm.so.1 > > libc.so.1 => /usr/lib/libc.so.1 > >

LD_RUN_PATH (was: libtool / C++ / inter library dependencies)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I wrote: > Shared C++ Library liba.so, > Shared C++ Library libb.so, > > libb.so depends on liba.so. > > [...] > > ->ldd libb.so > liba.so.0 => ./liba.so.0 > libstdc++.so.2.10.0 => (file not found) I know now, what the pr

LDFLAGS / LDADD / LIBADD (was: libtool / C++ / inter library dependencies)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Another question: What is the difference between xy_LDFLAGS = -lz and xy_LDADD = libz.la and which of them should I use? Please just ignore the -L and -R flags and the library path for this case. I know (I hope :-) how to h