emacs-bug-tracker
[Top][All Lists]
Advanced

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

bug#42529: closed (configure: error: Your 'rm' program is bad, sorry.)


From: GNU bug Tracking System
Subject: bug#42529: closed (configure: error: Your 'rm' program is bad, sorry.)
Date: Sat, 21 Nov 2020 02:21:05 +0000

Your message dated Fri, 20 Nov 2020 19:20:01 -0700
with message-id <202011210220.0AL2K1vi031505@freefriends.org>
and subject line Re: bug#42529: configure: error: Your 'rm' program is bad, 
sorry.
has caused the debbugs.gnu.org bug report #42529,
regarding configure: error: Your 'rm' program is bad, sorry.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
42529: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=42529
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: configure: error: Your 'rm' program is bad, sorry. Date: Sat, 25 Jul 2020 09:27:31 -0500 (CDT) User-agent: Alpine 2.20 (GSO 67 2015-01-07) On an OpenIndiana system without the GNU utilities in the executable search path, configure of autoconf-2.69b fails spectacularly. This failure was actually not unexpected since it is due to a ksh93 built-in bug which was never fixed. The problem does not occur if I do this (forcing use of bash, which is in the executable search path):

CONFIG_SHELL=/usr/bin/bash /home/bfriesen/src/gnu/autoconf-2.69b/configure

This is what actually happened:

weerd:~/build/autoconf-2.69b% /home/bfriesen/src/gnu/autoconf-2.69b/configure
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/gmkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
Usage: rm [-cFdfirRuv] file ...
Oops!

Your 'rm' program seems unable to run without file operands specified
on the command line, even when the '-f' option is present.  This is contrary
to the behaviour of most rm programs out there, and not conforming with
the upcoming POSIX standard: <http://austingroupbugs.net/view.php?id=542>

Please tell bug-automake@gnu.org about your system, including the value
of your $PATH and any error possibly output before this message.  This
can help us improve future automake versions.

Aborting the configuration process, to ensure you take notice of the issue.

You can download and install GNU coreutils to get an 'rm' implementation
that behaves properly: <http://www.gnu.org/software/coreutils/>.

If you want to complete the configuration process using your problematic
'rm' anyway, export the environment variable ACCEPT_INFERIOR_RM_PROGRAM
to "yes", and re-run configure.

configure: error: Your 'rm' program is bad, sorry.

--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
Public Key,     http://www.simplesystems.org/users/bfriesen/public-key.txt



--- End Message ---
--- Begin Message --- Subject: Re: bug#42529: configure: error: Your 'rm' program is bad, sorry. Date: Fri, 20 Nov 2020 19:20:01 -0700
Hi Bob - (sorry for the delayed reply)

    On an OpenIndiana system without the GNU utilities 
    ...
    Usage: rm [-cFdfirRuv] file ...]

So, it seems that system's rm does not accept "rm -f" (with no file
operands)? (I don't have access to any such system to check.)  If so, it
seems the error message is correctly reporting the state of things,
including the possible workaround, so I don't see anything to do?
Closing this now. Feel free to reopen (or just reply) if there is
something more automake should be doing. Thanks for the report. -k



--- End Message ---

reply via email to

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