On Thu, Sep 01, 2005 at 08:28:24PM +0200, Andreas Jellinghaus wrote:
> On Thursday 01 September 2005 16:52, Bob Friesenhahn wrote:
> > So it seems that a libtool-provided macro should be used in
> > configure.ac to test for an installed libltdl. Testing for it in a
> > simple way could well inde
On Thursday 01 September 2005 20:41, Ralf Wildenhues wrote:
> Dependent libraries it has, CFLAGS should not be necessary. Everything
> else would be a bug in ltdl.
>
> > is there something that works like AC_CHECK_LIB, except that AC_CHECK_LIB
> > seems to have no clue about *.la files, so is th
On Thu, 1 Sep 2005, Andreas Jellinghaus wrote:
now I wonder: if the libtool *.la files contain all information about
the dependencies etc, then shouldn't there be some macro that searches
for that *.la files, gets the dependencies from it, does the compile
and link test and sets up CFLAGS and LI
Hi Andreas,
* Andreas Jellinghaus wrote on Thu, Sep 01, 2005 at 08:28:24PM CEST:
> On Thursday 01 September 2005 16:52, Bob Friesenhahn wrote:
> >
> > I may be missing something, but all the libltdl-related macros I see
> > are for the case of when libltdl is bundled with the package. I don't
On Thursday 01 September 2005 16:52, Bob Friesenhahn wrote:
> So it seems that a libtool-provided macro should be used in
> configure.ac to test for an installed libltdl. Testing for it in a
> simple way could well indeed result in false negatives due to libltdl
> depending on some other librar
On Thursday 01 September 2005 12:30, Howard Chu wrote:
> If you use libtool for linking, and the libltdl.la file is installed,
what about configure code? which configure macro will look for libltdl.la?
can I use
dnl use ltdl
AC_CHECK_LIB(ltdl, lt_dlopen,, [AC_MSG_ERROR([libltdl not found])])
?
On Thu, 1 Sep 2005, Howard Chu wrote:
I guess I should better probe for libdl and
link with it, too? anthing else?
If you use libtool for linking, and the libltdl.la file is installed, then
dependencies are taken care of automatically. If you're not using libtool for
linking, then you're mak
Andreas Jellinghaus wrote:
Howard Chu wrote:
In OpenLDAP's configure.in we use
...
so does libltdl never need any libraries
linked to it? like "-ldl" on some systems
or something else? all that complexity
is usualy hidden in an m4 macro package,
a libfoo-config script or a pkgconfig/libfoo.
Howard Chu wrote:
> In OpenLDAP's configure.in we use
...
so does libltdl never need any libraries
linked to it? like "-ldl" on some systems
or something else? all that complexity
is usualy hidden in an m4 macro package,
a libfoo-config script or a pkgconfig/libfoo.pc
file.
I guess I should bet
