Package: libtool
Version: 2.2.6a-1
Tags: fixed-upstream

In libtool from experimental, ECHO is set as follows in
/usr/bin/libtool line 161:

        # An echo program that does not interpret backslashes.
        ECHO="echo"

But in POSIX shells, echo is not guaranteed not to interpret
backslashes (and dash's echo does interpret backslashes). Thus e.g.
when building gtk+2.0 2.14.7-2 (which was libtoolized with libtool
from experimental), I found that a sed -n  -e 's/^.* ... /\1 \2 \2/p'
had caused .libs/libgdk_pixbuf-2.0.exp to contain literal \001 and
\002 characters.

Luckily, the solution is simple.  Upstream commit a0283899e "Implement
$ECHO with print -r, printf or cat in a shell function." sets
ECHO='printf "%s\n"' when building libtool with either bash or dash as
sh, fixing the problem.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to