Re: static libperl?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: static libperl?
Date: 2005-08-17 00:32:39
Message-ID: 430285A7.8040700@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>
>
>>/usr/bin/ld: /usr/local/lib/perl5/5.6.1/mach/CORE/libperl.a(perl.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC
>>
>>
>
>
>
>>Does that mean that we are attempting to link against a static libperl.a?
>>I thought we were supposed to inhibit that.
>>
>>
>
>Platypus is freebsd though, and we now think we don't need shared
>libraries on that platform:
>http://developer.postgresql.org/cvsweb.cgi/pgsql/src/makefiles/Makefile.freebsd.diff?r1=1.19;r2=1.20
>
>I am wondering if the issue is that you need -fPIC and libperl was only
>made with -fpic.
>
>It could be that platypus was only passing before because it didn't try
>to build plperl.
>
>
>
>

Yeah. I thought we didn't want to link large static libraries into the
backend, regardless of other issues, but I guess I should have read the
makefile more closely.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-08-17 02:56:42 Re: pl/Ruby, deprecating plPython and Core
Previous Message Josh Berkus 2005-08-17 00:14:05 More handles for BGWriter?