On 16 August 2015 at 15:47, Gavin Smith <gavinsmith0...@gmail.com> wrote: > On 16 August 2015 at 15:29, Eli Zaretskii <invalid.nore...@gnu.org> wrote: >> Follow-up Comment #2, bug #45759 (project texinfo): >> >> The problems you are having happen because ActiveState Perl produces file >> names with backslashes, which MSYS Bash then treats as escape characters. >> For >> example, see how this: >> >> c:\NOS_PR~1\msys\MINGW-~1\I686-4~1.0-P\mingw32\bin\gcc.exe >> >> became this: >> >> c:NOS_PR~1msysMINGW-~1I686-4~1.0-Pmingw32bingcc.exe >> > > I think we need to double backslashes in the output of "perl -V:cc". I > thought that that was Perl code that was output but it may actually be > shell code.
Like this, for example: Index: tp/Texinfo/Convert/XSParagraph/configure.ac =================================================================== --- tp/Texinfo/Convert/XSParagraph/configure.ac (revision 6499) +++ tp/Texinfo/Convert/XSParagraph/configure.ac (working copy) @@ -7,17 +7,13 @@ conf_value=`${PERL} -V:$1` echo got "$conf_value" # This turns a string like "cc='cc';" into a string like "cc". - # We also turn \" into ", \' into ' and \\ into \. There may - # be other \ sequences we want to process as well. This is - # the escape sequence for single-quoted strings in Perl. + # We also double backslashes. conf_value=`echo $conf_value \ | sed -e 's/^@<:@^=@:>@*= *//' \ -e 's/^'\\''//' \ -e 's/ *; *$//' \ -e 's/'\\''$//' \ - -e 's/\\\\"/"/g' \ - -e 's/\\\\'\\''/\\'\\''/g' \ - -e 's/\\\\\\\\/\\\\/g' ` + -e 's/\\\\/\\\\\\\\/g' ` echo got "$conf_value" }