Re: Configure can't find com_err on OpenBSD for --with-krb5 - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Configure can't find com_err on OpenBSD for --with-krb5
Date
Msg-id 200703250151.l2P1p7s07230@momjian.us
Whole thread Raw
In response to Re: Configure can't find com_err on OpenBSD for --with-krb5  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Configure can't find com_err on OpenBSD for --with-krb5  (Jim Rosenberg <jr@amanue.com>)
List pgsql-general
Tom Lane wrote:
> Jim Rosenberg <jr@amanue.com> writes:
> > Here's the problem: when configure tries to compile the code snippet to
> > check for com_err, it needs to do this with -lcrypto added, but it's not
> > using that. What's the "right" way to fix this? I could probably get it to
> > work by brutally hacking configure, but there's got to be a better way.
>
> I think the "right" fix is probably to add -lcrypto to these lines in
> configure.in, which are already accounting for random other possible
> dependencies of libkrb5:
>
>      AC_SEARCH_LIBS(com_err, [krb5 'krb5 -ldes -lasn1 -lroken' com_err], [],
>                     [AC_MSG_ERROR([could not find function 'com_err' required for Kerberos 5])])
>      AC_SEARCH_LIBS(krb5_sendauth, [krb5 'krb5 -ldes -lasn1 -lroken'], [],
>                     [AC_MSG_ERROR([could not find function 'krb5_sendauth' required for Kerberos 5])])
>
> but I'm not sure why no one else would've complained before, if that
> were necessary...

Where are we on this?

--
  Bruce Momjian  <bruce@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-general by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Lifecycle of PostgreSQL releases
Next
From: Bruce Momjian
Date:
Subject: Re: Why can't I put a BEFORE EACH ROW trigger on a view?