RE: Kerberos libs dependancy in linking with mmc created module
"Shay Harding" <sharding-YCNXYxaMkU/[email protected]> Mon, 3 Feb 2003 05:56:42 -0700
| Newsgroups | gmane.comp.lang.moto.devel |
|---|---|
| Organization | CCBill |
| Message-ID | <000d01c2cb83$b312e730$7500000a@ccbill22ms668m> |
Yeah, I saw this last time I built the Postgres driver. I don't think we
need to link openssl with postgres unless the postgres database was
built with support for it. MySQL will soon be faced with the same
problem as they just got their 4.1 build to use SSL layering as well.
MySQL has had it in their code for a while now, but it never worked
until recently.
For Postgres we might want to add a test that does something like:
# Find pg_config path
$PATH/pg_config --configure|grep "\-\-with\-openssl"
if [ $? -eq 0 ]
then
# Add support for Openssl
fi
I'll find out how to do it for MySQL as soon as they stabalize the 4.1
release. Their newest release is only available from CVS right now. I'll
check the latest stables to see if they snuck the SSL stuff is in there
as well.
Shay
> -----Original Message-----
> From: David Hakim [mailto:dhakim-Gkm/TONP9n1Wk0Htik3J/[email protected]]
> Sent: Sunday, February 02, 2003 3:06 PM
> To: Stefano Corsi
> Cc: [email protected]
> Subject: Re: [moto-devel] Kerberos libs dependancy in linking
> with mmc created module
>
>
> Ok, so the way to get things working on your system is to modify
> mx/codex/db/pgsql/PGSQL.i adding the appropriate Library or
> Archive. So
> if the symbols you need were defined in libkerberos.so you would add:
>
> Library: -lkerberos
>
> at the top of the PGSQL.i file
>
> The bigger question is "How do we identify the postgres drivers
> dependencies on any particular platform and build a moto driver that
> reflects those dependencies ?". Right now there is a
> configure.in file
> in the pgsql extension which does:
>
> AC_CHECK_LIB(crypt,crypt,[MXLIBCRYPT="Library: -lcrypt"])
> AC_CHECK_LIB(crypto,ERR_reason_error_string,[MXLIBCRYPTO="Library:
> -lcrypto"])
> AC_CHECK_LIB(ssl,SSL_free,[MXLIBSSL="Library: -lssl"])
>
> These configure variables get substituted into PGSQL.i.in
>
> @MXLIBCRYPT@
> @MXLIBSSL@
> @MXLIBCRYPTO@
>
> That result in a configured PGSQL.i that looks like
>
> Library: -lssl
> Library: -lcrypto
>
> So what's going on now is that the driver is being built with
> at least
> some of the possible dependencies for postgres. But on
> certain systems
> postgres doesn't depend on libcrypt/libcrypto/or libssl ... and on
> other systems like yours it depends on further additional libraries.
> What the configure script should be doing is identifying the
> dependencies for pgsql on the system moto is being built on and
> including those (and only those) in the moto driver.
>
> Let me know the name of the library the kerberos dependencies are
> defined in so it can be added to the pgsql configuration
> process in the
> future.
>
> -Dave
>
>
> On Sunday, February 2, 2003, at 05:44 PM, Stefano Corsi wrote:
>
> >> Are you sure its libcodex ? If so than this is a big problem,
> >> libcodex should in no way be relying on any sort of crypto
> libs. See
> >> if you can verify this by using the 'nm' utility on
> libcodex.a . My
> >> suspicion is still that the problem is with the moto
> postgres driver.
> >
> > I meaned that one, sorry, I didn't mean the main libcodex.
> This is how
> > I began suspecting on a dependence:
> >
> > [root@localhost root]# grep -r krb /usr/mx/codex/
> > Binary file
> /usr/mx/codex/db/pgsql/libmx_codex_db_pgsql.so.1.0 matches
> > Binary file
> /usr/mx/codex/db/pgsql/libmx_codex_db_pgsql.so.1 matches
> > Binary file /usr/mx/codex/db/pgsql/libmx_codex_db_pgsql.so matches
> >
> > Doesn't this mean that libmx_codex_db_pgsql.so is using some krb
> > symbols (or
> > more probably linking them from some postgres library)?
> >
> > Stefano
> >
> >
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.449 / Virus Database: 251 - Release Date: 1/27/2003