From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Neil Padgett <npadgett(at)redhat(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Re: Proposal for encrypting pg_shadow passwords |
Date: | 2001-08-15 21:29:03 |
Message-ID: | Pine.LNX.4.30.0108152326510.677-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian writes:
> > Hmm... I used to be able to build in a separate tree than my source
> > tree. Since this patch was applied, I can't. It seems that the
> > preprocessor is finding the system md5.h (i.e. /usr/include/md5.h)
> > rather than the PostgreSQL md5.h. Suggestions on how to fix?
I kind of doubt that, since the new code does #include "libpq/md5.h".
> Ewe, you have md5.h somewhere else. Let me rename it to pgmd5.h. Is
> that OK for everyone? Or maybe I should move it all into crypt.h. That
> seems to make more sense.
No, the problem is that you are not supposed to have include files in the
backend subtree. I'm surprised the code builds at all.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Padgett | 2001-08-15 21:30:17 | Re: Fix for fetchone() and fetchmany() in Python interface |
Previous Message | Bruce Momjian | 2001-08-15 21:26:42 | Re: Re: Proposal for encrypting pg_shadow passwords |