Hey Richard,
sorry i didn’t see your patch. as i wrote in the beginning, this is one of my
first patches i committed and i might have done something wrong. In this case i
haven’t had a look at the bug list first. sorry for that.
i don’t want to say your patch is not working, since i didn’t try
Le 10/05/16 02:43, Christian a écrit :
> i’ve had a look again at libtool.m4 and don’t really get why RM is set wrong.
> obviously the _LT_CONFIG macro literally requires _LT_FILEUTILS_DEFAULT,
> which should set RM to ‘rm -f’. I also found several uses of $RM with
> different options,
i’ve had a look again at libtool.m4 and don’t really get why RM is set wrong.
obviously the _LT_CONFIG macro literally requires _LT_FILEUTILS_DEFAULT, which
should set RM to ‘rm -f’. I also found several uses of $RM with different
options, sometimes even ‘-f’. So actually i am not sure what
Christian wrote:
so today i gave it a shot again and put a debug output right before the ‘$RM
“$cfgfile”’. For some reason RM is set to ‘/bin/rm’ only. no ‘-f’. i’ll try to
figure out where that might come from.
Perhaps build package is libxslt .
Issue is already reported many times. Project
so today i gave it a shot again and put a debug output right before the ‘$RM
“$cfgfile”’. For some reason RM is set to ‘/bin/rm’ only. no ‘-f’. i’ll try to
figure out where that might come from.
anyway, thx for the hint :)
> On May 8, 2016, at 8:57 PM, Christian wrote:
thx Eric for taking a look at my patch.
it seems to be a good idea to use ‘rm -f’ and i also think it looks like $RM
should already be set to ‘rm -f’. but i don’t get why it should fail than.
what i’ll do next is check if $RM really is set to ‘rm -f’ using a debug
print. couldn’t do it right
On 05/05/2016 11:22 PM, Christian wrote:
> So i found that if you’re running ‘./configure’ on a project that depends on
> libtool, it might happen that the script will end up with the following
> error:
> “/bin/rm: cannot remove 'libtoolT': No such file or directory”. I did some
>
>