Re: linking hba.c

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
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 02:45:37
Message-ID: 200108270245.f7R2jbQ07717@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > > > 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.

There is not much there. I can use a -Ddefine in ODBC and just
conditionally define what I need when I am compiling in ODBC. Isn't
worth a DLL.

Can you help me add MD5 to ODBC? I am getting lost in the way they do
passwords, and I don't even have a MSWin machine to test it once I am
done.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-08-27 04:01:48 Upcoming events
Previous Message Larry Rosenman 2001-08-27 02:02:32 Re: pg_dump failure, can't get data out...