Re: Re: patch to fix configure(.in) on openbsd wrt/ krb5/com_err and readline linking

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <stark(at)enterprisedb(dot)com>
Cc: Simon Bertrang <janus(at)errornet(dot)de>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: patch to fix configure(.in) on openbsd wrt/ krb5/com_err and readline linking
Date: 2009-06-10 14:05:36
Message-ID: 123.1244642736@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Greg Stark <stark(at)enterprisedb(dot)com> writes:
> This seems really weird. Firstly, doesn't OpenBSD use ELF? Shouldn't
> the library pull in the indirectly needed libraries automatically? But
> more to the point, why on *earth* would com_err depend on -lssl and
> -lcrypto? com_err is just a standard error handling library. Why
> would it fail to link without ssl and crypto libraries?!?!

And you'd also need to explain why the spoonbill buildfarm member
is building just fine without this ... it does have kerberos
enabled ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dhaval Jaiswal 2009-06-10 14:23:46 Re: to_timestamp error handling.
Previous Message Tom Lane 2009-06-10 13:51:07 Re: BUG #4838: Database corruption after btree_gin index creation