Front page | perl.perl5.porters |
Postings from May 2003
On Tue, May 20, 2003 at 12:42:50PM -0400, Andy Dougherty wrote:
> Hmm. Tricky. If perl is built and configured with -Duseshrplib, then
> libperl.a never gets built (at least by default). The actual library
> that gets built is available as $Config{libperl}.
>
> Part of the problem is that it's not at all obvious to me what the
> ultimate intent here is. This perl was built with -Duseshrplib, but this
> particular extension is being "statically linked" in. If MakeMaker is
> changed to look for $Config{libperl}, then this extension will be
> statically linked into a new binary, but that binary will still use the
> libperl.so (or whatever the platform-specific suffix is). Is this the
> user's intent? I have no idea. I never imagined this scenario.
>
> Some distributors are apparently going to the extra effort of providing
> their users with both libperl.so and libperl.a, but stock perl won't
> do that for you.
I think I just have no idea how to do static builds.
--
Cuius rei demonstrationem mirabilem sane detexi hanc subcriptis
exigutias non caperet.
Thread Previous