GNU bug report logs -
#17478
"No such file or directoryn" due to incorrect escaping
Previous Next
Reported by: Egmont Koblinger <egmont <at> gmail.com>
Date: Mon, 12 May 2014 17:37:01 UTC
Severity: normal
Done: Peter Rosin <peda <at> lysator.liu.se>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
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
bfriesen <at> simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
This bug report was last modified 11 years and 11 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.