From: | imacat <imacat(at)pristine(dot)com(dot)tw> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Compiling PL/Perl and Pl/Python on x86_64 |
Date: | 2006-05-22 15:33:35 |
Message-ID: | 20060522233259.E3BA.IMACAT@pristine.com.tw |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 21 May 2006 16:35:24 -0700 (PDT)
gede wawan <gde_wawan(at)yahoo(dot)com> wrote:
> relocation R_X86_64_32 can not be used when making a shared object;
> recompile with -fPIC
May I ask how? I have tried to edit src/makefiles/Makefile.linux
and changed -fpic to -fPIC, but it does not help. Maybe I should set
the flag elsewhere?
Actually, I have made some tests. I found that in the PostgreSQL
document, Perl must be built as shared library:
> 14.2. Requirements
> To build the server programming language PL/Perl you need a full Perl
> installation, including the libperl library and the header files. Since
> PL/Perl will be a shared library, the libperl library must be a shared
> library also on most platforms. This appears to be the default in recent
> Perl versions, but it was not in earlier versions, and in any case it is
> the choice of whomever installed Perl at your site.
But, on my i386 machine, I can build PL/Perl with static library
(libperl.a). But I can't do that on x86_64 anymore. Can somebody tell
me why, or where should I referring to?
The same issue goes to PL/Python. I'm not good at Python, but I
know that I was building static library before, and it works for
PL/Python on i386. But it does not work anymore on x86_64, too.
--
Best regards,
imacat ^_*' <imacat(at)mail(dot)imacat(dot)idv(dot)tw>
PGP Key: http://www.imacat.idv.tw/me/pgpkey.txt
<<Woman's Voice>> News: http://www.wov.idv.tw/
Tavern IMACAT's: http://www.imacat.idv.tw/
TLUG List Manager: http://lists.linux.org.tw/cgi-bin/mailman/listinfo/tlug
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-05-22 15:41:59 | Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) |
Previous Message | Dawid Kuroczko | 2006-05-22 15:30:12 | Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) |