[sr #108987] libtool doesn't like simple RM defined (without options)

[Richard PALO]

Additional Item Attachment, sr #108987 (project libtool):

File name: 0001-avoid-issues-if-CP-MV-or-RM-are-predefined-in-the-ex.patch
Size:1 KB
File name: 0002-avoid-issues-if-CP-MV-or-RM-are-predefined-in-the-ex.patch
Size:0 KB


___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/


___
https://lists.gnu.org/mailman/listinfo/libtool

avoid issues if CP, MV or RM are predefined in the execution environment

[Richard PALO]

Please see problem report and submitted patches 
https://savannah.gnu.org/support/index.php?108987
It would be great if these could be included in the upcoming release.

Currently, and since many years, pkgsrc has patched libtool to simply 'unset' 
CP, MV & RM

This patchset 'fixes' the use as documented, that is to respect the environment 
if these variables
are set, but naturally -- if set -- they will be just the path to the tool and 
as such can in no
way expect that '-f' is specified (which is '--force' under the Gnu flavours of 
these tools).
-- 
Richard PALO


___
https://lists.gnu.org/mailman/listinfo/libtool