Re: cleaning without -f

[Robert Boehne]

Wesley,

Adding "-f" only supresses the error message, and mode=clean requires
you to give it the "rm" program so why not use
--mode=clean 'rm -f' 
Or does that not work?

Robert

"Wesley W. Terpstra" wrote:
> 
> Oh, and there is another bug in --mode=clean. (not fixed by my previous patch)
> This one needs a decision by the libtool maintainers.
> 
> When cleaning out an libtool executable (shell script) WIHOUT 'rm -f' and
> only 'rm', you will get this error:
> 
> rm main/test main/.libs/test main/.libs/testS.o main/.libs/lt-test
> rm: cannot remove `main/.libs/testS.o': No such file or directory
> 
> The problem is that .libs/lt-test and .libs/testS.o do not necessarily
> exist. They are only created at some points in the execute/install cycle.
> 
> Please note, this bug has always existed. It doesn't matter if the
> executable is in a subdirectory or not. Simply cleaning without '-f' with
> any dynamically linked executables (and prior to running & installing them)
> will trigger it.
> 
> I think there are at least three solutions:
>         implicitly add '-f' to all invokations of --mode=clean
>         implicitly add '-f' to executable cleaning
>         test executable shell script existence in ltmain.in and give an
>                 error ourselves if it doesn't exist, if it does, use '-f'
> 
> I am in favour of the last one, but ... not my code.
> 
> --
> Wesley W. Terpstra <address@hidden>
> 
> _______________________________________________
> Libtool-patches mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/libtool-patches