Re: MirBSD patch for bmake (again)

[Benny Siegert <bsiegert%gmail.com@localhost>]

On Sun, Mar 13, 2011 at 17:19, Christos Zoulas <christos%astron.com@localhost> 
wrote:
> Why can't MirBSD use echo?

The default shell, mksh, which is used to execute the commands,
interprets \x followed by two hex characters as the corresponding
ASCII character. \x is used as an invalid escape sequence in one of
the tests. This expands to a null byte in the output with mksh.

It seems that the interpretation of escape sequences in echo is not
portable, and that only printf gives a reproducible output
interpretation. However, in the last discussion of this patch,
concerns were voiced about the availability of printf on all platforms
supported by pkgsrc, and about possible slowdowns. This is why I use
printf only on MirBSD here, where it is known to be needed.

--Benny.

-- 
The first essential in chemistry is that you should perform practical
work and conduct experiments, for he who performs not practical work
nor makes experiments will never attain the least degree of mastery.
        -- Abu Musa Jabir ibn Hayyan (721-815)