From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <stark(at)mit(dot)edu> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Michael Meskes <meskes(at)postgresql(dot)org>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>, postgres-xc-developers(at)lists(dot)sourceforge(dot)net |
Subject: | Re: Building on S390 |
Date: | 2013-11-23 05:10:05 |
Message-ID: | 2262.1385183405@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark <stark(at)mit(dot)edu> writes:
> On Fri, Nov 22, 2013 at 8:51 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> According to the Debian build logs, postgres-xc compiles the entire
>> backend with -fPIC. Not sure what sense that makes.
> Debian policy is to always use -fPIC
> IIRC -fpic is good enough as long as the total size of the library is below
> some limit. I'm not sure precisely what this size is that has to be below
> the limit but if I recall correctly it's something you have no way to
> determine in advance for a general purpose library. So Debian decided long
> long ago to just use -fPIC always.
Well, in that case they did a really crappy job of applying that policy to
their Postgres packages, because it sure sounds like there's still some
-fpic switches laying about in their builds. But in any case, that
seems to me like a pretty brain-dead policy (hint: if you need -fPIC,
you'll get build failures that tell you so), so I feel no need to adopt
it for standard Postgres builds.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2013-11-23 05:15:09 | Re: Proof of concept: standalone backend with full FE/BE protocol |
Previous Message | Gurjeet Singh | 2013-11-23 04:06:35 | Re: Shave a few instructions from child-process startup sequence |