[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Windows Build Error, C:Strawberry221perlbinperl.exe command not foun
From: |
Eli Zaretskii |
Subject: |
Re: Windows Build Error, C:Strawberry221perlbinperl.exe command not found |
Date: |
Fri, 15 Dec 2017 10:30:19 +0200 |
> Date: Thu, 14 Dec 2017 21:42:35 -0600
> From: address@hidden
>
> I am automating the Texinfo build process in Perl via my new Alien::Texinfo
> software:
>
> https://github.com/wbraswell/alien-texinfo
>
> This build process works successfully on most operating systems, but a few
> notable exceptions exist.
>
> Using the AppVeyor testing platform for Microsoft Windows, we see an odd
> error:
> C:Strawberry221perlbinperl.exe: command not found
You need to set things up so that the above file name uses forward
slashes, not backslashes, as in "C:/Strawberry221/perl/bin/perl.exe"
Here's the configure command I use to build Texinfo on MS-Windows:
PERL=/d/usr/Perl/bin/perl PERL_EXT_LDFLAGS=-static-libgcc CC='gcc
-static-libgcc' CFLAGS='-O2 -gdwarf-4 -g3' ./configure --prefix=d:/usr
--enable-threads=windows
Change /d/usr/Perl/bin/perl to match your Perl installation,
i.e. /c/Strawberry221/perl/bin/perl, and change --prefix=d:/usr to
match your target installation directory.
> Searching through the entire log, we can see all other references to
> "perl.exe" are the correct full path of
> "C:\Strawberry221\perl\bin\perl.exe", but in this particular error we can see
> that somehow all the backslash
> characters have been stripped to leave us with the obviously-incorrect
> "C:Strawberry221perlbinperl.exe"
> string.
Yes, the backslash is a quote character in Unix shells, so if you want
a literal backslash, you need to double them. In this case, it is
easier to use forward slashes instead.