automake-patches
[Top][All Lists]
Advanced

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

Re: Automake,cygwin: 'make clean' with libtool wrappers...


From: Charles Wilson
Subject: Re: Automake,cygwin: 'make clean' with libtool wrappers...
Date: Tue, 07 May 2002 13:25:42 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2

Alexandre Duret-Lutz wrote:

"Charles" == Charles Wilson <address@hidden> writes:


 Charles> Without this patch, automake fails two tests:
 Charles> subobj9
 Charles> pr300-ltlib
 Charles> With this patch, automake still fails both tests.

 Charles> However, AFAICT, the reason is not related to the
 Charles> problem fixed by this patch (or, if this patch does
 Charles> fix a problem that would cause subobj9 to fail, it is
 Charles> being hidden by another bug that my patch doesn't
 Charles> address).

So let's make a new test case to be on the safe side.  Could you
try the following and confirm it FAILs before and PASSes after
your patch?


Okay, first I'm not sure how this tests clean-*PROGRAMS, since it doesn't build any executables (on purpose). It only builds a library.

Second, you also need to use --copy with libtool, if you're trying to work around the 'cp -p' bug.

Third, this fails both with and without my patch (actually, I used your version of my patch)

 .PHONY clean-am: clean-%DIR%PROGRAMS
 clean-%DIR%PROGRAMS:
- -test -z "$(%DIR%_PROGRAMS)" || rm -f $(%DIR%_PROGRAMS) +?!LIBTOOL? -test -z "$(%DIR%_PROGRAMS)" || rm -f $(%DIR%_PROGRAMS) +?LIBTOOL? @list='$(%DIR%_PROGRAMS)'; for p in $$list; do \ +?LIBTOOL? f=`echo $$p|sed 's/$(EXEEXT)$$//'`; \ +?LIBTOOL? echo " rm -f $$p $$f"; \ +?LIBTOOL? rm -f $$p $$f ; \ +?LIBTOOL? done

The reason it fails is a longtime annoyance of mine: configure, while running, creates test programs called 'a.exe' -- not 'a.out' or 'a'. So, **configure** doesn't clean up after itself. I think this is an autoconf bug...

If I manually delete the 'a.exe' file -- in both build directories, at the appropriate time -- then I pass the test both with and without my patch. This is because libtool3.test, as written, doesn't actually test whether programs are properly deleted.

--Chuck






reply via email to

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