* Herbert Xu said: > On Thu, Oct 21, 1999 at 03:04:07PM +0200, Marek Habersack wrote: > > The latest ash package (0.3.5-7) has a broken 'echo' builtin > > implementation. It should accept the -e and -n parameters, but it doesn't. > > That breaks many things for those who use ash as their /bin/sh - for example > > Linux compile process (makefile uses @echo -n ... to generate UTS_VERSION in > > include/linux/compile.h, which gets output as '-n #define UTS_VERSION ...'). > > The attached patch fixes the command to accept BOTH parameters. It parses > > the first args to echo searching for -n and/or -e. First argument starting > > with anything else than '-' or not being -n or -e causes echo to output the > > rest of commandline. > > It's not broken. The Single Unix Specification says that echo must not > support any options. The kernel makefile should be fixed. During the Debian packages upgrade I saw many, many '-n something' messages, meaning that many packages use -n. Perhaps SUS should be changed? The echo manpage from ash says it supports -n and -e paramerters. The shellutils echo also supports these options. I don't see what's the rationale behind the SUS restriction? Why wouldn't echo support options that are so commonly used? marek
Attachment:
pgpgPgBy6eVHP.pgp
Description: PGP signature