summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSergei Trofimovich <slyfox@gentoo.org>2019-03-09 19:56:20 +0000
committerSergei Trofimovich <slyfox@gentoo.org>2019-03-10 00:19:16 +0000
commitcb16168c4ea6976b638148758a18992eafdfd235 (patch)
tree896fcdb174fcb14aa70bf599ce132cf9f62d3596 /dev-scheme
parentdev-scheme/guile-cairo: drop ppc keywords, bug 679462 (diff)
downloadgentoo-cb16168c4ea6976b638148758a18992eafdfd235.tar.gz
gentoo-cb16168c4ea6976b638148758a18992eafdfd235.tar.bz2
gentoo-cb16168c4ea6976b638148758a18992eafdfd235.zip
app-emulation/qemu: fix init.d/qemu-binfmt for mksh, bug #679168
Handling of escaped by echo is an implementation-defined behaviour according to POSIX: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/echo.html "A string to be written to standard output. If the first operand is -n, or if any of the operands contain a <backslash> character, the results are implementation-defined." Practically this makes $ echo '\xFF' behave differently on bash/dash and mksh: bash outputs '\xFF' string of 4 bytes while mksh outputs single 0xFF into stdout. The change is to use "printf '%s\n' '\xFF'" to get consistent behaviour. Reported-by: Jimmy.Jazz@gmx.net Reviewed-by: Matthias Maier Closes: https://bugs.gentoo.org/679168 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
Diffstat (limited to 'dev-scheme')
0 files changed, 0 insertions, 0 deletions