Front page | perl.perl5.porters |
Postings from July 2010
On Mon, 05 Jul 2010, Steve Hay wrote: > Steve Hay wrote on 2010-06-29: > > So I've now moved on to trying to build perl (5.12.1) with the > > 64-bit compiler (amd64) on a 64-bit machine, but it still isn't > > working for me. > > > > I opened up the standard VC++ x64 command prompt, set CCTYPE=MSVC90 > > in the win32/Makefile (I'm using Visual Studio 2008 SP1), and typed > > nmake. I cannot reproduce this problem with the free VS2008 compiler from the Windows 7 SDK (running on Windows XP 64). I did a second attempt on a Vista machine that had VS 2008 on it, but probably not SP1, and it didn't show any problems either. Could you provide exhaustive setup information how to reproduce this? > > It started by emitting a mountain of warnings about type conversions > > for every file that it compiles. Is that normal? Then it produced > > this strange error message immediately after linking perl.exe: > > > > ..\miniperl.exe -I..\lib bin\exetype.pl ..\wperl.exe WINDOWS > > 'x' outside of string in unpack at bin\exetype.pl line 39. > > NMAKE : fatal error U1077: '..\miniperl.exe' : return code > > '0xff' Stop. > > FWIW, I eventually got the build working by using $(PERLEXE) instead > of $(MINIPERL) in that command-line, as suggested here: It sounds really weird that it works with one but not the other. Could this be some antivirus interference? Does it still fail if you try to run it manually after waiting a little bit? > http://www.perlmonks.org/?node_id=834521 > > It may be worth applying the suggested patch(es), even though it ducks > the real problem rather than fixing it. I'm not too keen on changing stuff without really understanding the underlying problem first. Given that at least 2 people seem to have run into this it should be possible to reproduce it eventually. Cheers, -JanThread Previous | Thread Next