inaries - unzip -
if a supporting XS is not found.
Archive::Extract is easily installed in on a legacy system without compiler.
--
Reini Urban
http://cpanel.net/ http://www.perl-compiler.org/
x27;s Object::Remote?
A pure-perl PAR would fill that role better. It was made for this case,
but nobody can use it so far.
> > People on the list might correct me, but I think the major use of the
> > PAR family of modules is not to create jar-like archives, but
> > to create standalone executables.
Yes, but the first idea for par was jar, not parl and PAR::Packer. Ask
Audrey.
--
Reini Urban
http://cpanel.net/ http://www.perl-compiler.org/
a obfuscated and bleached (and possibly encrypted)
> PAR files
>
> Does anyone have any major objection to me using the PAR namespace in this
> way and anyone want to help in task ?
>
> I think that, it I get this working reliably, it could result a new
> popularity for perl
Reini Urban
rur...@x-ray.at
On Mar 7, 2013, at 3:05 AM, Roderich Schupp
wrote:
> On Wed, Mar 6, 2013 at 10:51 PM, Reini Urban wrote:
>> All this because of a wrong logic in the main Makefile.PL ("double
>> negation always causes trouble")
>
> From your pat
On Wed, Mar 6, 2013 at 3:22 PM, Reini Urban wrote:
> On Wed, Mar 6, 2013 at 2:48 AM, Roderich Schupp wrote:
>> Why do you want to use PAR::Packer on Cygwin at all?
>> If you just want to create a standalone executable from a Perl application:
>> Are you aware that the resul
handling, and is not needed.
PAR-1.007 tested ok
PAR-Packer-1.013:
windres -F pei-i386 -i winres/pp.rc -o winres/pp.res
windres -o ppresource.coff winres/pp.res
windres: unexpected version string length 68 != 32 + 8
That's a known mingw/cygwin binutils bug, and should be not fatal. The
resourc
; Warning: prerequisite Module::ScanDeps 1.09 not found. We have 1.08.
> Warning: prerequisite PAR 1.005 not found.
--
Reini Urban
http://cpanel.net/ http://www.perl-compiler.org/
wngrade Perl to
> 5.10.1.
> At that point I gave up.
Did 5.14.1 worked for you at all?
I deleted that package because the EUMM rules were broken.
It's looking better now but still not ready to package.
--
Reini Urban
http://cpanel.net/ http://www.perl-compiler.org/
y)
heuristics in the walker
the deps might too heavy but they work mostly.
--
Reini Urban
http://cpanel.net/ http://www.perl-compiler.org/
er (par.exe) must link it in. You may want
> to check the link command that produces par.exe (I have only mail access
> for the next few days).
Phil,
I fixed my packaging mistake yesterday.
I just missed Cwd.a, so ExtUtils::Embed::ldopts did not find it.
Fixed now.
--
Reini Urban
d in Perl 5.12.3.
>
> Please try the attached patch to PAR::Packer, should make
> the hack work on both old and new versions of XSLoader.pm.
> Note: you must rebuild and reinstall PAR::Packer and then repack executables
> to see any effect.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
#x27;t check Module::Scandeps if it uses all the weird needed
logic to detect it (FileHandle), but that would be my first guess.
The workaround would to add IO manually (-m IO) in pp.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
work
> too, but using $Config{ptrsize} seems more directly connected to the
> question.
$Config{ivsize} can be fooled, $Config{ptrsize} not.
In fact cygwin is shipped with 64bit ivsize=8 on 32-bit windows.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
open
> Ticket https://rt.cpan.org/Ticket/Display.html?id=55994 >
>
>
> On Mon May 24 17:27:05 2010, DJIBEL wrote:
>> Sorry, that is the real patch.
>
> Looks reasonable to me, except for the
>
> if ($^O eq 'MSWin32') ...
>
> tests. Is there any
2009/7/29 Angelos Karageorgiou :
> anyone alive and corporeal monitoring this list?
alive yes
corporeal ??
monitoring no
r is this coming from:
# Check for path:
if( $dllname =~ /.*[\/\\]/){
$dllname = $';
$path = $&;
$path =~ s,[/\\](\.[/\\])*,/,g;
}
so path is the dirname of the given dll.
do not use "-o ./par.dll", just "-o par.dll"
I (as cygwin's perl maintaine
the zip
content into the .data section or as resource.
I was toying with this idea in
http://code.google.com/p/perl-compiler/source/browse/trunk/script/pl2exe.pl
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
Gabor Szabo schrieb:
On Wed, Aug 27, 2008 at 9:33 PM, Reini Urban <[EMAIL PROTECTED]> wrote:
and I have forgotten to tell about the vi-style autocompletion that we
already had back then.
Since then it just improved thanks to the efforts of AdamK.
emacs has also autocompletion. Is vi dif
Gabor Szabo schrieb:
On Mon, Aug 25, 2008 at 11:05 PM, Reini Urban <[EMAIL PROTECTED]> wrote:
Gabor Szabo schrieb:
./padre_0.05_linux_t1
./padre_0.05_linux_t1: /lib/tls/libc.so.6: version `GLIBC_2.4' not
found (required by ./padre_0.05_linux_t1)
Does that mean it I'll also
glibc_2.2, maybe even 2.0
This kind of packaging works actually quite nice. :)
Just watched your yapc::eu 08 lightning talk about padre btw.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
technically possible
(just link the available dll's),
but you will not be able to publish the fixed headers. Licensing issues.
DirectX libs can be compiled though.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
kipped.
Well, for a virgin system without cygwin installed and a truly
standalone par exe,
the list of needed dll's is fine, with the exception of unitialized
mounts points (registry)
and /etc/{passwd,groups}.
But the test case will not run on such a virgin system, and a virgin
system is very "virgin",
without users and mounts.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
2008/5/21 Robert Davis <[EMAIL PROTECTED]>:
> The test of PAR::Packer fails and I think I found the fix.
>
> Basically the exe's produced from pp still depend on the cygwin dll's and
> setting the path to one directory prevents them from being found.
Thanks. This is correct.
to the target machines. I looked in the
> cache directory and found libperl.dll.a when I omitted the "-d" option.
> Shouldn't the absence of the "-d" option include cygperl5_8.dll on
> cygwin PAR distributions?
It should. But I never checked because it makes not much sense on cygwin.
We support no parallel perls, only a single perl version.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
2008/5/12 Marco Estrada Martinez <[EMAIL PROTECTED]>:
> the workaround, that can I use a symbolic-link under linux to par-exe is
> very good. can i use this under widows, when yes, how?
In windows you can use junctions, which are hardlinks.
junction.exe is at sysinternals.com
--
t some time to get to the bottom of it and
> possibly improve it, if someone can tell me where to look... Why isn't
> it found (even with '--execute'), and how does it work for shared
> libraries?
Look at your /usr/bin/perlld
Maybe you mixed up your installations.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
http://spacemovie.mur.at/ http://helsinki.at/
with
their own, then you may not be seeing the perlpad window you expected.
cygwin setup works also this way,
a LOT of people use this and
nobody cared about DNS poisoning so far.
--
Reini Urban
http://phpwiki.org/ http://murbreak.at/
http://helsinki.at/ http://spacemovie.mur.at/
Joe Landman schrieb:
Working on trying a build on cygwin 1.5.19 (will upgrade to 1.5.21 next
week). Tried both 0.942 and 0.950 beta. Same problem in both cases
...
main.o:main.c:(.text+0x67): undefined reference to `_boot_'
collect2: ld returned 1 exit status
perlld: *** system() failed to e
s works ok,
but the testsuite detected a Win32::GetShortPathName bug on cygwin.
So I needed the attached patch.
Which probably should not go into the package...
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
http://phpwiki.org/
cygwin perl5.8.6 Win32::GetShortPathName apparently is broken
. There an
external .pod file would make more sense. Maybe pod2usage should try to
find an external .pod file also on binary scripts, before trying to
fetch a magic stream, which should be provided by p5p.
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
http://phpwiki.org/
30 matches
Mail list logo
