Tried to build GNU tar 1.28 in Unixware 7.1.4 (*), got the below:
(*) $ uname -a: UnixWare unixware 5 7.1.4 i386 x86at SCO UNIX_SVR5 $ echo $PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/java2-1.5.0/bin:/usr/local/sbin:/usr/ccs/bin:/usr/sbin:/usr/java/bin $ sh configure --prefix=/usr/local checking for a BSD-compatible install... /usr/local/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/local/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... no checking whether UID '152' is supported by ustar format... yes checking whether GID '1' is supported by ustar format... yes checking how to create a ustar tar archive... plaintar UX:rm: ERROR: Incorrect usage UX:rm: TO FIX: Usage: rm [-fiRr] 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. $ which rm /usr/bin/rm
