[Top][All Lists]

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

LT_OUTPUT and config.status --recheck

From: Peter Rosin
Subject: LT_OUTPUT and config.status --recheck
Date: Fri, 20 Mar 2009 12:16:20 +0100
User-agent: Thunderbird (Windows/20090302)


I think it is a bug that LT_OUTPUT does not create the libtool
script when you do "./config.status --recheck".

(I think the bug crept in because LT_OUTPUT shares code with the
config.status machinery, and is therefore sharing the handling of
the --no-create option which is added to the configure invocation
by config.status --recheck)

Or, am I missing something?

This testsuite addition exposes the problem:

diff --git a/tests/early-libtool.at b/tests/early-libtool.at
index 75e26a2..7cc40b9 100644
--- a/tests/early-libtool.at
+++ b/tests/early-libtool.at
@@ -222,4 +222,8 @@ LT_AT_EXEC_CHECK([./hell], [0], [stdout])
 AT_CHECK([grep 'Welcome to GNU Hell' stdout], [], [ignore])
 AT_CHECK([grep 'This is not GNU Hello.' stdout], [], [ignore])

+# Make sure config.status --recheck updates the libtool script
+rm libtool
+AT_CHECK([$SHELL ./config.status --recheck],[0],[ignore],[ignore])


reply via email to

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