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

[Michael Forster]

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:

cat: ../ltdl.m4: No such file or directory
Makefile.am:5: INSTALL_LTDL does not appear in AM_CONDITIONAL
Makefile.am:12: CONVENIENCE_LTDL does not appear in AM_CONDITIONAL
Makefile.am:18: variable `LIBADD_DL' not defined
Makefile.am:21: variable `LIBADD_DL' not defined
autoconf: Undefined macros:
configure.in:36:AC_LIB_LTDL
cat: ../ltdl.m4: No such file or directory
Makefile.am:5: INSTALL_LTDL does not appear in AM_CONDITIONAL
Makefile.am:12: CONVENIENCE_LTDL does not appear in AM_CONDITIONAL
Makefile.am:18: variable `LIBADD_DL' not defined
Makefile.am:21: variable `LIBADD_DL' not defined
autoconf: Undefined macros:
configure.in:36:AC_LIB_LTDL

Obviously the file ltdl.m4 is missing. Checking out the file from the MAIN
branch:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

cvs update -A ltdl.m4

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.1 Int. for non-commercial use


iQA/AwUBOKur1MeYjj0YYPBiEQLxxQCgqP+RmBToqNRBNsNO0UHT0JQzne4AoK/I
hq7id6GXEfwJytv60n8AxSp1
=BxiH
-END PGP SIGNATURE-


solved this problem, but I have not tested any further yet.

Bye,
Mike

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

[Michael Forster]

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 the multi-language-branch I get
the following error messages:

cat: ../ltdl.m4: No such file or directory
Makefile.am:5: INSTALL_LTDL does not appear in AM_CONDITIONAL
Makefile.am:12: CONVENIENCE_LTDL does not appear in AM_CONDITIONAL
Makefile.am:18: variable `LIBADD_DL' not defined
Makefile.am:21: variable `LIBADD_DL' not defined
autoconf: Undefined macros:
configure.in:36:AC_LIB_LTDL
cat: ../ltdl.m4: No such file or directory
Makefile.am:5: INSTALL_LTDL does not appear in AM_CONDITIONAL
Makefile.am:12: CONVENIENCE_LTDL does not appear in AM_CONDITIONAL
Makefile.am:18: variable `LIBADD_DL' not defined
Makefile.am:21: variable `LIBADD_DL' not defined
autoconf: Undefined macros:
configure.in:36:AC_LIB_LTDL

Obviously the file ltdl.m4 is missing. Checking out the file from the MAIN
branch:

cvs update -A ltdl.m4

solved this problem, but I have not tested any further yet.

Bye,
Mike

libtool / C++ / inter library dependencies

[Michael Forster]

-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:

 Makefile.am

lib_LTLIBRARIES = liba.la libb.la

liba_la_SOURCES = a.cpp

libb_la_SOURCES = b.cpp
libb_la_LIBADD = liba.la



[BTW: which combination of "LIBADD" / "LDADD" / "LDFLAGS" and "liba.la" /
"-la" should I use?]

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
libstdc++.so.2.10.0 =>  
/public/packages/programming/gcc-2.95.2/lib/libstdc++.so.2.10.0
libdl.so.1 =>/usr/lib/libdl.so.1
/usr/platform/SUNW,Ultra-250/lib/libc_psr.so.1

Please note the second line.

Platforms: Solaris 2.6 + 8, Linux
Versions: various, mostly
autoconf 2.49a, 
automake 1.4, 
libtool CVS multi-language-branch, some days ago.
gcc-2.95.2

Greetings, Mike

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.8 for non-commercial use 

iQA/AwUBOc7/18eYjj0YYPBiEQKa8wCgq//SvRRI8BG515OiZ1WsJnTWeyEAn0IE
vj062niAdpoe8bYm2h2xGr/J
=DbSZ
-END PGP SIGNATURE-


___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool

RE: libtool / C++ / inter library dependencies

[Michael Forster]

-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
> > libstdc++.so.2.10.0 =>  
> > /public/packages/programming/gcc-2.95.2/lib/libstdc++.so.2.10.0
> > libdl.so.1 =>/usr/lib/libdl.so.1
> > /usr/platform/SUNW,Ultra-250/lib/libc_psr.so.1
> > 
> > Please note the second line.
> 
> Maybe I'm missing something but isn't that exactly what you wanted,
> i.e. libb.so does indeed appear to depend on liba.so (liba.so.0)?

Well, I meant the second line of the ldd output :-):

> > libstdc++.so.2.10.0 =>   (file not found)

Why are there two references to libstdc++, and only one can be resolved?

Greetings, Mike

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.8 for non-commercial use 

iQA/AwUBOdLWrseYjj0YYPBiEQJDbQCeKyLUlvOiPJGTCedGFA1DwMbi+xwAn0KT
bEvSBeqnCTc3ZGAMWFAC+P55
=BjqP
-END PGP SIGNATURE-


___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool

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

[Michael Forster]

-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 problem was: Our local gcc installation depended on
LD_RUN_PATH to hardcode the libstdc++.so path into binaries. Libtool uses
- -R when linking libb.so. This overrides LD_RUN_PATH.

Suggestion: Should libtool add -R flags for every entry in LD_RUN_PATH?

Mike

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.8 for non-commercial use 

iQA/AwUBOdrd9ceYjj0YYPBiEQKmjACdG3cgplB2aMIRB3kCJwUb9e6rz/UAoN1E
aBUeH3GxnXOIZpQeesEcoIGm
=y37M
-END PGP SIGNATURE-


___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool

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

[Michael Forster]

-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 handle them.

I have this situation:
  * Libraryliba.la
  * Librarylibb.la  depends on liba.a
  * Exceutable cdepends on liba.la and libb.la

i.e. in the dynamic case c should automatically load liba and libb, and
libb should automatically load liba when dlopened. In the static case, c
should include liba and libb, but libb should not include liba.

There are two solutions I have come to:

lib_LTLIBRARIES = liba.la libb.la
bin_PROGRAMS = c

liba_la_SOURCES = a.cpp
libb_la_SOURCES = b.cpp
c_SOURCES = c.cpp

1)

libb_la_LDFLAGS = -la
c_LDFLAGS = -la -lb

2)

libb_la_LIBADD = liba.la
c_LDADD = liba.la libb.la

Both solutions do what I wanted them to do, the libtool documentation
suggests Method 2):

 First, to link a program against a libtool library, just use the
`program_LDADD' variable:

 bin_PROGRAMS = hell
 
 # Build hell from main.c and libhello.la
 hell_SOURCES = main.c
 hell_LDADD = libhello.la

But If I use Method 2) in my case I get the following warning:

ld: warning: file /home/brscratch/forster/at-test/.libs/liba.so: linked to
./.libs/liba.so: attempted multiple inclusion of file

with method 1) I do not. So what should I do? Ignore the warning? Use
Method 1? My problem is that I don't understand the semantical difference
beween 1) and 2). 

[If there's some documentation about this topic I have missed, I'd also be
happy to be pointed to that]

Environment:
  CVS autoconf, CVS automake, CVS ML Libtool, 
  gcc 2.95.2, Solaris 8

Thanks in advance,

Mike

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.8 for non-commercial use 

iQA/AwUBOdt5bMeYjj0YYPBiEQK4vgCfTDgydpsPOid37gphpM7iRQygd68AoPIP
IVPwmUx5T3K3ZrFHez5JzmDr
=AZB8
-END PGP SIGNATURE-


___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool