From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Perrin <andrew_perrin(at)unc(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PL/Perl without shared libperl.a |
Date: | 2001-05-11 16:40:47 |
Message-ID: | 5513.989599247@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Andrew Perrin <andrew_perrin(at)unc(dot)edu> writes:
> Has anyone got advice on building postgres 7.1 with PL/Perl support
> WITHOUT having one's perl installation built with a shared libperl.a?
Try repeating the Perl build with shared-lib selected and then just
installing the resulting libperl.so beside libperl.a. However:
> I'm happy enough to build a special libperl.a for postgresql's use, but
> I don't want my general perl build to use it since perl's documentation
> notes a significant performance hit when using a shared libperl.
That advice is doubtless platform-specific, and I think it may well be
horsepucky for Intel-based Linux. Isn't *all* code built
position-independent on that platform?
I believe you could actually use a non-shared libperl.a on Intel Linux;
just dike out the test for shared-ness in plperl's Makefile.PL.
The reason it's there is we couldn't think of a direct test for
position-independent code, which is the real requirement...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | larry a price | 2001-05-11 16:42:05 | Re: Nu-B Question |
Previous Message | Philip Crotwell | 2001-05-11 16:36:13 | Re: defunct postmasters |