Skip site navigation (1) Skip section navigation (2)

Re: linking hba.c

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: linking hba.c
Date: 2001-08-27 01:54:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > In trying to decide how to keep ODBC compilable standalone, I can't
> > > figure out how to get md5.c in there from backend/libpq.
> >
> > AFAIK ODBC hasn't been compilable standalone for awhile; doesn't it
> > depend on our toplevel configure script now?
> The Unix version is not compilable on its own, but I see no code in
> win32.mak that refers to upper directories.

> >
> > > Is it crazy to
> > > put md5.c in interfaces/odbc and symlink it from there to backend/libpq
> > > and interfaces/libpq?
> >
> > YES, that's crazy.  If you think ODBC should build separately, then give
> > it its own copy of md5.c.  But please first check that your assumption
> > is still valid.
> And I will just throw a note at the top of each mentioning they should
> be identical.

Is it that easy to copy md5.c ?
ms5.c includes postgres.h and libpq/crypt.h.
I prefer to have e.g. md5.dll.

Hiroshi Inoue

In response to


pgsql-hackers by date

Next:From: Larry RosenmanDate: 2001-08-27 02:02:32
Subject: Re: pg_dump failure, can't get data out...
Previous:From: Peter EisentrautDate: 2001-08-27 01:27:44
Subject: Re: pg_dump failure, can't get data out...

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group