Re: .so and .a libs, tcl, postgres = in over my head

[Stephen Zander <gibreel@pobox.com>]

>>>>> "Jason" == Jason Gunthorpe <jgg@gpu.srv.ualberta.ca> writes:
    Jason> Now when you move to the case with apache you have a
    Jason> problem, libperl.so is loaded, but it doesn't load into the
    Jason> global scope (that is what the patch hacks in) so when you
    Jason> go to load a perl module it blows up because it can't find
    Jason> the symbols.

All what perl binary modules? No dynamic perl module (ie all of them)
ever goes near libperl.{a,so} when it's being built.

    Jason> With a libperl.so all of the binary perl modules can link
    Jason> directly against it and then in the apache case the
    Jason> RTLD_GLOBAL flag can be removed as the dlinker will be able
    Jason> to properly locate the symbols.

FUD.  No perl extension is at all useful without a perl interpreter.
Therefore, in apache, mod_perl has to do all the loading of perl
extensions.  If mod_perl exists, libperl.{a,so} must also exist and
there are no symbol issues at all.


-- 
Stephen
---
all coders are created equal; that they are endowed with certain
unalienable rights, of these are beer, net connectivity, and the
pursuit of bugfixes...  - Gregory R Block


--  
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org