Peter Prymmer <[EMAIL PROTECTED]> writes:
> On Thu, 14 Dec 2000, Charles Lane wrote:
>> I recently found that embedded perl couldn't use "Socket" routines,
>> even though they were built as a static extension. It seems that
>> the perl code for generating the embedded Perl interface looks at
>> the Config.pm parameter "static_ext", and we don't add Socket when
>> built as a static extension.
> Actually - this (the current behavior) seems to be in keeping with other
> platforms in that "nothing" is listed in the $static_ext variable, not
> even Dynaloader (I thought that was weird on OSF/1 some time ago). I
> guess that VMS differs only in that Socket is added statically, unlike
> most other platforms.
Well, if you poke around in ExtUtils::Embed you'll see that Dynaloader
is handled as a special case. No doubt because if Dynaloader is added
to static_ext then bad things happen. But you do need static_ext to
get the boot code generated for static extensions.
No doubt the "proper" fix is to correctly generate static_ext and
dynamic_ext on the fly in CONFIGURE.COM, but it's not clear that it
is really worth it. Maybe if we had more of a mix of static and
dynamic extensions.
--
Drexel University \V --Chuck Lane
======]---------->--------*------------<-------[===========
(215) 895-1545 _/ \ Particle Physics
FAX: (215) 895-5934 /\ /~~~~~~~~~~~ [EMAIL PROTECTED]
