bug#17478: "No such file or directoryn" due to incorrect escaping

[Bob Friesenhahn]

On Mon, 12 May 2014, Egmont Koblinger wrote:
> PROMPT$ ./src/vte-2.91
> gcc: error: vte_2_91-app.o: No such file or directory
> gcc: error: vte_2_91-appresources.o: No such file or directory
> gcc: error: ./.libs/libvte-2.91.so: No such file or directorynPROMPT$
>
> Notice that a literal "n" is printed after the 3rd error message,
> rather than a newline.
>
> The libtool-generated src/vte-2.91 script contains:
> printf %s\n "$relink_command_output" >&2
>
> where the backslash is swallowed by the shell and it becomes a literal
> "n".  It should be either double-backslashed, or enclosed between
> quotes.
>
> If you google "No such file or directoryn" with that extra "n" at the
> end, you'll see plenty of matches, so probably this is a common
> problem.

I am not seeing this on any of my systems here.

What version of libtool is being used (output of './libtool --version' 
in build tree).

What operating system is being used (output of 'uname -a')?

What is the output from 'config.guess' in the source tree?

What is the value of $SHELL?

What is the origin of the printf used?

Bob
--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/