Re: Tom Lane 2012-12-18 <8705.1355845...@sss.pgh.pa.us>
> > The correct fix, IMO/IIRC, is to add LDFLAGS=-Wl,--as-needed before
> > running most of the configure checks, instead of after.
>
> Meh. It's not clear to me at all that that fixes the issue here,
> or at least that it does so in any way
Peter Eisentraut writes:
> On Mon, 2012-12-17 at 18:02 +0100, Christoph Berg wrote:
>> I have no clue why no one else has seen this bug before, but the
>> reason for the error seems to be that configure is invoking the
>> setproctitle test including -ledit. libedit.so is linked to libbsd.so,
>> wh
Re: Tom Lane 2012-12-18 <26465.1355798...@sss.pgh.pa.us>
> I think we should assume that the libedit developers are utterly
> clueless about not trampling on application namespace, and just cut
> that library out of *all* our link checks except for the symbols we
> specifically expect to get from l
On Mon, 2012-12-17 at 18:02 +0100, Christoph Berg wrote:
> I have no clue why no one else has seen this bug before, but the
> reason for the error seems to be that configure is invoking the
> setproctitle test including -ledit. libedit.so is linked to libbsd.so,
> which in turn contains setproctitl
On 12/17/2012 09:44 PM, Tom Lane wrote:
I think we should assume that the libedit developers are utterly
clueless about not trampling on application namespace, and just cut
that library out of *all* our link checks except for the symbols we
specifically expect to get from libedit/libreadline.
Christoph Berg writes:
> We are regularly teaching PostgreSQL courses at linuxhotel.de.
> Starting from the course in November, PG doesn't compile anymore on
> their default Debian Squeeze install laptops they hand out to the
> participants. After ./configure && make, the error looks like this:
>
