On Sun, Dec 28, 2003 at 10:59:41AM +0800, Autrijus Tang wrote:
> å ä, 2003-12-23 11:50, Andy Balaam åéï
> > More info:
> > After reading Autrijus' message here:
> > http://www.mail-archive.com/[EMAIL PROTECTED]/msg00670.html
> > I tried to do what he said:
>
> Thanks for the input, and sorry that
Looks like my freshly minted perl5.8.2 based vcp.exe is finding an
incompatible XSLoader.pm on a test system with a loitering perl5.8.0
install, see below. Renaming C:\Perl works around the problem.
Added to rt.
- Barrie
Z:\HostShare\VCP>perl -v
This is perl, v5.8.0 built for MSWin32-x86-multi
On Sat, Jan 10, 2004 at 01:52:03AM +0800, Autrijus Tang wrote:
> ?b å, 2004-01-08 12:40, Barrie Slaymaker ?g?D?G
> > Below is a quick patch to make --add actuall add the requested file(s)
> > instead of merely scanning it for dependancies.
>
> Wait, --add really works for me.
On Sun, Jan 11, 2004 at 03:41:15AM +0800, Autrijus Tang wrote:
>
> I just gave it a try, and committed a modified PAR.pm to the snapshot
> version (linked to from http://par.perl.org/). Can you test it a bit to
> see if it works for you or not?
This looks ok with some basic tests, thanks!
I sti
On Wed, Jan 21, 2004 at 06:01:08PM -0700, Mike Schroeder wrote:
> a pp generated exe ... not finding LWP::Simple.
Have you tried --add=LWP::Simple? Not sure if it will be found in the
.exe's archive before the remote fetch is done, and I haven't tried that
with LWP::Simple, but I use it here with
On Wed, Jan 21, 2004 at 11:14:30AM -0500, Barrie Slaymaker wrote:
> On Sun, Jan 11, 2004 at 03:41:15AM +0800, Autrijus Tang wrote:
> >
> > I just gave it a try, and committed a modified PAR.pm to the snapshot
> > version (linked to from http://par.perl.org/). Can you test i
Ok, I reworked my app to work around the [EMAIL PROTECTED] implementation
of PAR, so while I (from the comfort of my armchair) still think
avoiding [EMAIL PROTECTED] is a good idea, at least VCP is ok with
PAR using it.
Thanks for the great app; PAR's a lifesaver.
- Barrie
ny ways to my packager and I'd like to abandon mine and switch to PAR
completely.
On Mon, Jan 26, 2004 at 11:11:24PM +0800, Autrijus Tang wrote:
> ?b ä, 2004-01-23 19:55, Barrie Slaymaker ?g?D?G
> > What is the advantage of using the CODE refs in @INC?
>
> It makes it easier
On Tue, Jan 27, 2004 at 12:42:12AM +0800, Autrijus Tang wrote:
>
> > - The %2E is perhaps best left as a "." when not on VMS and the
> > filename begins with a non-".".
> > - This would make the paths easier to read and work with when
> > spelunking around to see what's
On Mon, Jan 26, 2004 at 07:04:10PM +0800, Autrijus Tang wrote:
> ?b ä, 2004-01-21 22:14, Roderich Schupp ?g?D?G
> > Hi,
> > there's a problem with "pp -M ...". It shows when you
> > compare the result of the following commands
> > i.e. the module itself (both pm and dll in case of an XS module)
>
I built a vcp.exe using a relatively recent PAR snapshot (which works
much better, thanks!) and a VCP user tried to run it on a machine with a
different Perl version. He reports bug 4863 I entered a while ago:
http://rt.cpan.org/NoAuth/Bug.html?id=4863
I can reproduce it by building a foo.ex
Trying the same (other than the binary name)
pp -o vcp-bin -M=... ... bin/vcp
command on RH8 that works on Win32 I get:
/usr/bin/parl: creation of
/tmp/par-barries/cache-b1a427210984eb4e1eb7feac2f4c904246fc7f9c/libperl.so failed -
aborting with 2.
Has anyone seen this or have any adv
On Thu, Jan 29, 2004 at 10:46:20PM -0500, Barrie Slaymaker wrote:
> /usr/bin/parl: creation of
> /tmp/par-barries/cache-b1a427210984eb4e1eb7feac2f4c904246fc7f9c/libperl.so failed -
> aborting with 2.
>
> Has anyone seen this or have any advice?
Blowing away /tmp/par-barrie
I'm trying to build a binary on RedHat 8 using the stock perl5.8.0 for
now. The binary boots and runs, but locks up in an infinite loop.
Running it in the debugger leads me to a line like:
use POSIX qw( dup dup2 );
in my code. POSIX uses AutoLoader. AutoLoader is looking up
$INC{"POSIX.pm"
This patch preemptively extracts the contents of the .zip file and not
unshift &find_par on @INC. This is necessary to, for instance, use
POSIX on Unix platforms. I think it would also address my older issues,
but that's moot.
A minor debugging fix is also added below.
It also adds a dependancy
On 5/23/2011 7:23 AM, Philip Kime wrote:
I don't really understand why this works fine unpacked but doesn't when packed
...
As Mark said below, this happens because the IPC::Run module on Win32
(only) tries to run subprocesses using $^X, which normally contains the
path to perl.exe. However, w
pp looks to be very nice, but I can't seem to get parl.exe to load
reliably on WinXPPro, example session below. Any ideas?
Thanks,
Barrie
C:\Perforce\VCP>parl
C:\Perforce\VCP>parl
C:\Perforce\VCP>parl
C:\Perforce\VCP>parl
C:\Perforce\VCP>pp -o vcp.exe bin/vcp
Can't spawn "C:\Perl\bin\parl.ex
I'm missing something about how to bundle libs with an executable.
Given a standard perl module build where bin/vcp is the script I'm
trying to package with no XS and all .pms are in lib/..., I tried
the below. Sorry if I'm missing the bloody obvious.
- Barrie
C:\Perforce\VCP>pp -o vcp.exe -l li
On Sep 27 2003, Barrie Slaymaker wrote:
pp looks to be very nice, but I can't seem to get parl.exe to load
reliably on WinXPPro, example session below. Any ideas?
More info: parl.exe launches reliably on Win2KPro.
- Barrie
C:\Perforce\VCP>pp -o vcp.exe -l lib bin/vcp
-l=lib fails too, but --lib=lib seems to work. Now to get all the
lazily loaded modules included :).
- Barrie
On Sep 27 2003, Barrie Slaymaker wrote:
On Sep 27 2003, Barrie Slaymaker wrote:
> pp looks to be very nice, but I can't seem to get parl.exe to load
> reliably on WinXPPro, example session below. Any ideas?
More info: parl.exe launches reliably on Win2KPro.
Spoke too soon. Ever
On Sep 27 2003, Autrijus Tang wrote:
?b 六, 2003-09-27 16:49, Barrie Slaymaker ?g?D?G
> > C:\Perforce\VCP>pp -o vcp.exe -l lib bin/vcp
>
> -l=lib fails too, but --lib=lib seems to work. Now to get all the
> lazily loaded modules included :).
-I is --lib (as in perl -I). -l is
On Sep 27 2003, Autrijus Tang wrote:
Bummer. Having no WinXP here I can't test it at all.
However, what version of VC++ are you using to compile parl.exe on
WinXP?
It's a binary install hidden from me by PAR-0.75's Makefile.PL
magic :).
- Barrie
On Sep 27 2003, Autrijus Tang wrote:
?b 六, 2003-09-27 17:28, Barrie Slaymaker ?g?D?G
> It's a binary install hidden from me by PAR-0.75's Makefile.PL
> magic :).
Oh. Yes, the prebuilt pardists are indeed compiled with VC++ 6.0 on
win2k. I wonder if it'd be better if I chan
Here's a diff -U1 between an strace of foo.exe built with:
pp -o foo.exe -e "print STDERR q{Hi\n}"
.
http://users.telerama.com/~rbs/foo_good_and_bad.diff
- Barrie
On Sep 27 2003, Barrie Slaymaker wrote:
Here's a diff -U1 between an strace of foo.exe built with:
Hit Send too quickly. It's a diff between two runs, one good and
one bad. There are a lot of differences in the batch of files it
writes, but the killer difference seems to be in ar
I have an app (VCP) that likes to use Pod::Usage to emit help and that
likes to allow access to help topics by scanning @INC for modules and
.pod files that contain the docs. It also uses the POD in the modules
to insert comments in config files it emits for all the options it
places in there.
PA
On Thu, Dec 11, 2003 at 09:12:56AM -0800, Peter Kay wrote:
> I apoligise if this message doesn't get posted to the
> par mailing list correctly - I'm trying here...
Mine seems to have problems running parl.exe in WinXX VMWare and, when
it does generate an exectable, the resulting executable has tr
ith MinGW). I'm using PAR 0.76.
>
> [Note for those following my previous activity: I gave up on Borland
> BCC55 and
> am now using MinGW, which has worked well for me - PAR compiles at least.]
>
> I am getting the same problems that Barrie Slaymaker reported here:
>
>
29 matches
Mail list logo
