[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: distributing libltdl with my package fails

From: Ralf Wildenhues
Subject: Re: distributing libltdl with my package fails
Date: Wed, 20 Apr 2005 10:17:46 +0200
User-agent: Mutt/1.4.1i

Hi Gideon,

* Gideon Go wrote on Tue, Apr 19, 2005 at 02:11:32AM CEST:
> However, I got trouble distributing libltdl with my package if I use 
> AC_CONFIG_AUX_DIR(config) in configure.ac.  Without this line, everything 
> works fine, but the base directory becomes a bit messy. 

Hmm.  It should work fine with the line included.

> I use:
> libtool v1.5.14
> autoconf v2.59
> automake v1.9.3
> gcc 3.3.1 on Linux SUSE 9.0
> I followed all directions as stated in "libtool.info:Distributing libltdl" 
> about what to include in configure.in:  
> and Makefile.am:
> SUBDIRS = libltdl
> etc...
> Then, I did:
> $ mkdir config
> $ libtoolize --ltdl
> $ autoreconf --verbose --install --symlink
> I got:
> ...
> libltdl/Makefile.am:5: INSTALL_LTDL does not appear in AM_CONDITIONAL
> libltdl/Makefile.am:12: CONVENIENCE_LTDL does not appear in AM_CONDITIONAL
> ...
> autoreconf: automake failed with exit status: 1

Do you have Automake, Autoconf and Libtool installed under the same
$prefix (like /usr/local)?  If not: please do this and retry.

> Then I added AC_LIB_LTDL just after AC_PROG_LIBTOOL.  This lets me build my 
> package successfully. (Yay!)

This should not be necessary AFAIK.

> Then I did
> $ make dist
> and tried to build from my distribution.
> Running ./configure from my distribution ends with:
> ...
> configure: configuring in libltdl
> configure: WARNING: no configuration information is in libltdl

Did running `autoconf' create libltdl/configure?

> Obviously, running make then halts with:
> make[1]: *** No rule to make target `config.h', needed by `ltdl.lo'.  Stop.
> I hope this gives you enough information to find out what goes wrong.  I'm 
> trying all kind of combinations for days now...

It's unfortunately not enough to be able to reproduce the problem(s).
It would be great if you could create a small example package and show
the exact steps you did (plus the output) to recreate the failures.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]