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

Re: linking hba.c

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: linking hba.c
Date: 2001-08-25 23:26:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> 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.

  Bruce Momjian                        |
  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


pgsql-hackers by date

Next:From: Christof GlaserDate: 2001-08-25 23:36:58
Previous:From: Tom LaneDate: 2001-08-25 23:18:26
Subject: Re: linking hba.c

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