On Thursday, January 24, 2013, Jason Barrett wrote:
>
> I change the exit expr to something other than 0 (e.g.: exit 1), the script
> runs and sets the error level as expected. However, it will no
> longer compile:
>
> >pp -o test4.exe -x test4.pl
> Set up gcc environment - 3.4.5 (mingw-vista spec
I have a perl script with a single line:
exit 0
It properly sets the error level and will pack into an .exe just fine. If
I change the exit expr to something other than 0 (e.g.: exit 1), the script
runs and sets the error level as expected. However, it will no
longer compile:
>pp -o test4.exe
2011/3/31 Mark Dootson :
> Hi,
>
> $Config{ptrsize} seems the definitive method. It is 4 or 8 for 32bit / 64bit
> Perl and gets you the right answer if you are running a 32 bit Perl on 64
> bit Windows.
>
> I think $Config{ivsize} as used in current pp makefiles should always work
> too, but using
From: Roderich Schupp
Sent: Thursday, March 31, 2011 3:47 AM
To: Bob R
Cc: Mark Dootson ; Travis Williams ; par@perl.org
Subject: Re: PP failure
On Thu, Mar 31, 2011 at 4:41 AM, Bob R wrote:
Thank you all for your efforts on this. Let me start out by saying I got
the
packer running on
On Thu, 31 Mar 2011, Mark Dootson wrote:
>
> $Config{ptrsize} seems the definitive method. It is 4 or 8 for 32bit /
> 64bit Perl and gets you the right answer if you are running a 32 bit
> Perl on 64 bit Windows.
>
> I think $Config{ivsize} as used in current pp makefiles should always
> work too
Hi,
$Config{ptrsize} seems the definitive method. It is 4 or 8 for 32bit /
64bit Perl and gets you the right answer if you are running a 32 bit
Perl on 64 bit Windows.
I think $Config{ivsize} as used in current pp makefiles should always
work too, but using $Config{ptrsize} seems more direct
Bob,
For info,
The only file that gets used out of the zip in your case is win32.coff.
I included the other files as they were used to create win32.coff so
that win32.coff is recreatable / amendable by anyone who might wish to
do so.
The change of requireAdministrator is something that would
s
apparently
already ventured into 64 bit Windows land.
Cheers, Roderich
-- Forwarded message ------
From: Bob R mailto:engin...@fuse.net>>
Date: Wed, Mar 30, 2011 at 10:18 PM
Subject: PP failure
To: rsch...@cpan.org <mailto:rsch...@cpan.org>
Hi,
I downloaded the
t this subject.
I've cc'ed Mark Dootson which maintains Win32::Exe and who has apparently
already ventured into 64 bit Windows land.
Cheers, Roderich
-- Forwarded message --
From: Bob R
Date: Wed, Mar 30, 2011 at 10:18 PM
Subject: PP failure
To: rsch...@cpan.org
Hi,
I
On Thu, Mar 31, 2011 at 1:48 AM, Mark Dootson wrote:
> The zip
>
> http://www.wxperl.co.uk/ppamd64_resource.zip
>
> Contains objects that can be unzipped into the current PAR::Packer source in
> the directory myldr. You want the contained win32.coff / win32.obj to
> replace the originals.
Thanks,
On Thu, Mar 31, 2011 at 4:41 AM, Bob R wrote:
> Thank you all for your efforts on this. Let me start out by saying I got the
> packer running on my machine!
Thanks for testing Mark's modifications.
> no visible difference. I did get one failure on the tests, but it appears to
> be just trying to
Bob R mailto:engin...@fuse.net>>
Date: Wed, Mar 30, 2011 at 10:18 PM
Subject: PP failure
To: rsch...@cpan.org <mailto:rsch...@cpan.org>
Hi,
I downloaded the latest Par-Packer (1.09) today and tried installing
it but it failed. I have to run on Windoze here so
Win32::Exe and who has apparently
> already ventured into 64 bit Windows land.
>
> Cheers, Roderich
>
>
>
> ------ Forwarded message --
> From: Bob R
> Date: Wed, Mar 30, 2011 at 10:18 PM
> Subject: PP failure
> To: rsch...@cpan.org
>
>
> Hi,
>
>
y ventured into 64 bit Windows land.
Cheers, Roderich
-- Forwarded message --
From: Bob R
Date: Wed, Mar 30, 2011 at 10:18 PM
Subject: PP failure
To: rsch...@cpan.org
Hi,
I downloaded the latest Par-Packer (1.09) today and tried installing
it but it failed. I have to run on Wind
On Mon, Jan 24, 2011 at 3:53 PM, Roderich Schupp
wrote:
> Looks more like a problem of Log::Report (which is "use"d by
> Hash::Case::Lower).
Further investigation shows that Log::Report::Dispatcher "require"s some
Log::Report::Dispatcher::$foo with $foo computed at import time
which definitely c
On Sun, Jan 23, 2011 at 10:08 PM, James Bowery wrote:
> ~/ncgi-bin$ cat t.pl
> use Hash::Case::Lower;
> tie my(%lchash), 'Hash::Case::Lower';
> $lchash{StraNGeKeY} = 3;
> print keys %lchash; # strangekey
> ~/ncgi-bin$ pp -M Hash::Case::Lower t.pl
Note that "-M Hash::Case::Lower" isn't necessa
~/ncgi-bin$ cat t.pl
use Hash::Case::Lower;
tie my(%lchash), 'Hash::Case::Lower';
$lchash{StraNGeKeY} = 3;
print keys %lchash; # strangekey
~/ncgi-bin$ pp -M Hash::Case::Lower t.pl
~/ncgi-bin$ ./a.out
Can't locate object method "init" via package
"Log::Report::Dispatcher::Perl" at Log/Report/Di
17 matches
Mail list logo