On Wed, Jan 04, 2006 at 12:23:44AM +0100, Ralf Wildenhues wrote: > > Do you have any idea which system might expose this? None of the > ones I have access to do, and it helps both for adding a note to > the Autoconf doc portability section, and assessing whether we > should check the autotools for more instances of this.
Try, um, older Solaris /bin/sed? I don't honestly remember how long ago I tripped over this -- I've just been sticking the semicolon in defensively ever since. I had thought, though, that the proprietary Unix vendors froze the utilities in /bin and /usr/bin in a pre-SuS state, and thus that any such problem would be present always and forevermore. A *lot* of these issues are masked if you put the directory with the standard-compliant binaries (usually /usr/xpg4/bin or something like that) ahead of /usr/bin in your PATH, or if your sysadmin installs GNU coreutils on everything. zw
