[Top][All Lists]

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

Re: Can't open configure

From: Ralf Wildenhues
Subject: Re: Can't open configure
Date: Mon, 6 Oct 2008 21:53:49 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

* Braden McDaniel wrote on Mon, Oct 06, 2008 at 03:29:46AM CEST:
> On Sun, 2008-10-05 at 19:36 +0200, Ralf Wildenhues wrote:
> > OK, the issue is that in the libltdl directory, aclocal.m4 is
> > regenerated, and configure is a symlink that points to a read-only
> > location.
> Aha... So the serial number message is more-or-less unrelated (and
> nonfatal).


> > Can you be bothered to retry with the current Libtool and libltdl
> > (2.2.6) and current Autoconf (2.63) and report back, please?
> I'll see if I can get to this.


> > Please note that a workaround for this is to use the --no-recursive
> > option for the upper autoreconf, to keep it from entering the libltdl
> > directory.
> Unfortunately that means it wouldn't recurse into my other
> AC_CONFIG_SUBDIRS, either.  A more palatable workaround (for me) is to
> use "libtoolize -c"; configure can then be overwritten.


> I'm coming around to the conclusion, though, that regardless of this
> problem, "libtoolize --ltdl" is not what I want for my project.
>       * My project is a library; thus, using libltdl as a convenience
>         library is not generally desirable.  While I wouldn't mind
>         giving users this approach as an option, the potential
>         side-effects are such that I'd want to make a user ask
>         specifically for this mode of operation.
>       * I think the notion of having arbitrary projects install libltdl
>         is not philosophically sound.  Thus, I would not care to enable
>         my project to potentially participate in this.

Fair points.


reply via email to

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