From davidl@lmert.com

Trying to build today's "latest.tar.gz" on Windows XP (32-bit) using
Visual Studio 2008, I get a "No such file or directory" error
building one of the encodings​:

cp Encode.pm ..\..\lib\Encode.pm
cp lib/Encode/Encoding.pm ..\..\lib\Encode\Encoding.pm
cp lib/Encode/JP/H2Z.pm ..\..\lib\Encode\JP\H2Z.pm
cp lib/Encode/GSM0338.pm ..\..\lib\Encode\GSM0338.pm
cp lib/Encode/Guess.pm ..\..\lib\Encode\Guess.pm
cp lib/Encode/MIME/Header.pm ..\..\lib\Encode\MIME\Header.pm
cp Encode/encode.h ..\..\lib\Encode\encode.h
  nmake -f Makefile all -nologo
cp Byte.pm ..\..\..\lib\Encode\Byte.pm
  ..\..\..\miniperl.exe "-I..\..\..\lib" ..\bin\enc2xs -"Q" -"O" -o byte_t
.c -f byte_t.fnm
Use of uninitialized value $cname in -f at ..\bin\enc2xs line 155.
Use of uninitialized value $cname in concatenation (.) or string at ..\bin\enc2x
s line 156.
Use of uninitialized value $cname in concatenation (.) or string at ..\bin\enc2x
s line 156.
Cannot open :No such file or directory at ..\bin\enc2xs line 156.
NMAKE : fatal error U1077​: '..\..\..\miniperl.exe' : return code '0x2'
Stop.
NMAKE : fatal error U1077​: '"c​:\Program Files\Microsoft Visual Studio 9.0\VC\BIN
\nmake.EXE"' : return code '0x2'
Stop.
Unsuccessful make(cpan/Encode)​: code=512 at ..\make_ext.pl line 490.
NMAKE : fatal error U1077​: '..\miniperl.exe' : return code '0x2'
Stop.

More specifically, I did an "nmake clean" and then "nmake" in the "win32"
directory using the following compiler​:

Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 for 80x86
Copyright (C) Microsoft Corporation. All rights reserved.

usage​: cl [ option... ] filename... [ /link linkoption... ]

--
DLL

From @tonycoz

On Fri May 31 16​:34​:23 2013, davidl@​lmert.com wrote​:

Trying to build today's "latest.tar.gz" on Windows XP (32-bit) using
Visual Studio 2008, I get a "No such file or directory" error
building one of the encodings​:
...

Does the name of directory you attempted to build perl in contain spaces?

Tony

The RT System itself - Status changed from 'new' to 'open'

From davidl@lmert.com

On 06/02/2013 10​:12 AM, Tony Cook via RT wrote​:

On Fri May 31 16​:34​:23 2013, davidl@​lmert.com wrote​:

Trying to build today's "latest.tar.gz" on Windows XP (32-bit) using
Visual Studio 2008, I get a "No such file or directory" error
building one of the encodings​:
...
Does the name of directory you attempted to build perl in contain spaces?

Tony
No. "C​:\src\perl-5.18.0", I ran "nmake" from the "win32" directory
below that.

--
David L Lambert
Member ACM (david.lee.lambert@​acm.org)
Phone 616-676-7375 * IM "davidleelambert" (Yahoo!, Skype, Google)
"Justicia, Tierra y Libertad"

From @tonycoz

On Mon, Jun 03, 2013 at 01​:16​:07PM -0400, David L Lambert wrote​:

On 06/02/2013 10​:12 AM, Tony Cook via RT wrote​:

On Fri May 31 16​:34​:23 2013, davidl@​lmert.com wrote​:

Trying to build today's "latest.tar.gz" on Windows XP (32-bit) using
Visual Studio 2008, I get a "No such file or directory" error
building one of the encodings​:
...
Does the name of directory you attempted to build perl in contain spaces?

Tony
No. "C​:\src\perl-5.18.0", I ran "nmake" from the "win32" directory
below that.

From looking at enc2xs it should be using the "byte_t.c" argument as
$cname on lines 155 and 156, so I can't see why you're getting that
warning and error.

Did you edit win32/Makefile to set CCTYPE to MSVC90 ?

Besides that you might try editing cpan/Encode/bin/enc2xs to dump the
contents of %opt before line 154 to try and diagnose the problem.

Tony

From @steve-m-hay

Is there any progress on this ticket? I cannot reproduce the problem
using VC++ 2010 and the tarball from the "snapshot" link on this page​:

http​://perl5.git.perl.org/perl.git/commit/d2a68ca8e9f23a357624176e0b4b7a3d63913441

(That's about the date and time of the latest.tar.gz that you referred
to, and I don't see any changes to Encode soon before or after that time.)

Do you have the same problem with current bleadperl (currently the
"snapshot" link on this page​:

http​://perl5.git.perl.org/perl.git/commit/b75763d608047188e76fcf5249a427b3ad13e87a

)?

Do you have the same problem with perl-5.18.0 (since that is mentioned
in the subject of this ticket)?

What OS are you using? Specifically, is it Windows XP 32-bit or 64-bit?
If it is the 64-bit version then you must set WIN64=undef in the
Makefile to build a 32-bit perl.exe with the 32-bit cl.exe.

All I do (on Windows 7 x64) is extract the tarballs into a folder with
no space, "cd" into the win32 folder and run​:

nmake CCTYPE=MSVC100 WIN64=undef

In your case, it would be​:

nmake CCTYPE=MSVC90 WIN64=undef

if you are on 64-bit, or​:

nmake CCTYPE=MSVC90

if you are on 32-bit.

From @steve-m-hay

On Thu Jun 13 00​:45​:59 2013, shay wrote​:

What OS are you using? Specifically, is it Windows XP 32-bit or 64-
bit?
If it is the 64-bit version then you must set WIN64=undef in the
Makefile to build a 32-bit perl.exe with the 32-bit cl.exe.

All I do (on Windows 7 x64) is extract the tarballs into a folder with
no space, "cd" into the win32 folder and run​:

nmake CCTYPE=MSVC100 WIN64=undef

In your case, it would be​:

nmake CCTYPE=MSVC90 WIN64=undef

if you are on 64-bit, or​:

nmake CCTYPE=MSVC90

if you are on 32-bit.

(Sorry, I just noticed that you said you're on 32-bit. So it's just

nmake CCTYPE=MSVC90

that you need.

There's no need to run "nmake [...] clean" first, btw... unless you've
made a previous attempt at building in the same source tree, of course.

In that case I think the "distclean" target does a fuller job than
"clean", but if you have got files from a previous build attempt laying
around then it would be worth deleting the whole folder and extracting
the tarball afresh to be absolutely sure you're doing a clean build.)

From @tonycoz

On Thu, Jun 13, 2013 at 12​:46​:00AM -0700, Steve Hay via RT wrote​:

Is there any progress on this ticket? I cannot reproduce the problem
using VC++ 2010 and the tarball from the "snapshot" link on this page​:

http​://perl5.git.perl.org/perl.git/commit/d2a68ca8e9f23a357624176e0b4b7a3d63913441

(That's about the date and time of the latest.tar.gz that you referred
to, and I don't see any changes to Encode soon before or after that time.)

Do you have the same problem with current bleadperl (currently the
"snapshot" link on this page​:

http​://perl5.git.perl.org/perl.git/commit/b75763d608047188e76fcf5249a427b3ad13e87a

latest.tar.gz is a symlink to the latest stable build - 5.18.0.

Tony

From itcharlie@gmail.com

Windows XP and Perl 5.18 is no longer supported and this ticket has not been updated since 2013. I will wait 2-3 days and ping someone from p5p group who can mark this ticket as won't fix.

Charlie Gonzalez

From [Unknown Contact. See original ticket]

Windows XP and Perl 5.18 is no longer supported and this ticket has not been updated since 2013. I will wait 2-3 days and ping someone from p5p group who can mark this ticket as won't fix.

Charlie Gonzalez

From @jkeenan

On Sat, 18 Feb 2017 16​:07​:02 GMT, itcharlie wrote​:

Windows XP and Perl 5.18 is no longer supported and this ticket has
not been updated since 2013. I will wait 2-3 days and ping someone
from p5p group who can mark this ticket as won't fix.

Charlie Gonzalez

Since you now have RT access, please close at your leisure. (We don't have a WONTFIX status -- that's Bugzilla -- so you can mark it Rejected.)

Thank you very much.

--
James E Keenan (jkeenan@​cpan.org)

From itcharlie@gmail.com

Marking this ticket "rejected" since Windows XP and Perl 5.18 is no longer supported.

Best,

Charlie

itcharlie@gmail.com - Status changed from 'open' to 'rejected'