Re: static build of perl

I don't have a SCO box to test on, but this seems a bit suspicious... You mention Time::HiRes specifically. From Changes5.8 in the 5.8.7 distribution:

 10953 By: jhi                                   on 2001/06/26  12:33:55
        Log: Subject: PATCH ext/Time/HiRes/Makefile.PL perl@10929 Test Fails on SCO
             From: Jonathan Stowe <gellyfish@gellyfish.com>                          
             Date: Tue, 26 Jun 2001 10:29:57 +0100 (BST)   
             Message-ID: <Pine.LNX.4.33.0106261021540.18774-100000@orpheus.gellyfish.com>
             
             SCO OpenServer 5.0.5 needs an explicit -lc for usleep().
     Branch: perl                                                    
           + ext/Time/HiRes/hints/sco.pl
           ! MANIFEST

If I were you, I might try compiling a 5.6 Perl.

Comment on Re: static build of perl - how?

Replies are listed 'Best First'.
Re: static build of perl - how? by ghee2ghee (Novice) on Jul 18, 2005 at 13:37 UTC
Yes - I did see this - but the resulting Makefile doesn't seem to use it. There is a comment about it being a MakeMaker parameter, but it isn't used anywhere else in the Makefile. I have got around this particular issue by adding -Dstatic_ext="Time/HiRes" when configuring - but this isn't really my problem, and there must be a better way than specifying every single module this way. My problem is that I want a static build of perl (executable and modules) that I can send out to my clients - specifically, I need libraries such as curses, openssl and expat, but would rather include them statically in the perl executable than have to use shared objects (some clients may already have these libraries, but older/newer versions, and I don't want to trample all over them). I can live with inflated perl binary sizes. When compiling some of the modules we need, I recall that at least one required a version 5.8.x release of perl - so 5.6.x is a non-starter, unfortuately. Thanks for the suggestion, though ;>	[reply]
Re^2: static build of perl - how? by salva (Canon) on Jul 18, 2005 at 14:03 UTC
maybe you could use a tool like par (or ActiveState Perl Dev Kit, though I think it doesn't support SCO UNIX). It can pack your scripts and modules with libperl, all the dlls required by your program and a small loader in one file for easy distribution.	[reply]