[Top][All Lists]

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

Re: LT_OUTPUT and config.status --recheck

From: Ralf Wildenhues
Subject: Re: LT_OUTPUT and config.status --recheck
Date: Sat, 21 Mar 2009 19:58:08 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

Hi Peter,

* Peter Rosin wrote on Fri, Mar 20, 2009 at 02:05:54PM CET:
> Den 2009-03-20 12:16 skrev Peter Rosin:
>> I think it is a bug that LT_OUTPUT does not create the libtool
>> script when you do "./config.status --recheck".

> Ok to push as attached?

Hmm, this goes only to show that it would have been a bad idea to let
LT_OUTPUT be the default mode: --no-create is intended to not create
output files.

In the long run, we should add macros to do compile/link tests that use
libtool variables, but not `./libtool', I guess.  Or only a temporary

But yes, for the current semantics, I guess your patch is the best we
can do.  Please apply, thanks.


> commit 301ebd4d3c2dc6c7f4d22996cf3b35e78b2ff492
> Author: Peter Rosin <address@hidden>
> Date:   Fri Mar 20 13:43:26 2009 +0100
>     LT_OUTPUT should always create the libtool script.
>     * libltdl/m4/libtool.m4 (LT_OUTPUT): Make LT_OUTPUT Ignore the
>     --no-create configure option, and assume that the user wants
>     to use an up-to-date libtool script if the LT_OUTPUT macro is
>     present.
>     * tests/early-libtool.at: Make sure we do not regress.

reply via email to

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