| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marko Kreen <marko(at)l-t(dot)ee> |
| Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgcrypto 3des failure, OpenSSL 0.9.8, Solaris 9/sparc |
| Date: | 2005-07-05 19:36:06 |
| Message-ID: | 26404.1120592166@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marko Kreen <marko(at)l-t(dot)ee> writes:
> On Tue, Jul 05, 2005 at 02:55:07PM -0400, Tom Lane wrote:
>> Hm ... libpq manages to build code that requires openssl without
>> needing a generated Makefile, so why do we need it here?
> Now, looking more into it, it indeed does work.
> But it breaks pgcrypto build for USE_PGXS case.
How exactly?
> Can I break USE_PGXS?
Nope, that's right out. If we have to use a Makefile.in we will,
but I'd like to understand why we have to.
> I'd like to eliminate hand-config.
That would be very good. In practice no one is likely to do any manual
configuration down inside a contrib module ... certainly none of the RPM
distributions do any such thing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2005-07-05 19:48:38 | Re: pgcrypto 3des failure, OpenSSL 0.9.8, Solaris 9/sparc |
| Previous Message | Marko Kreen | 2005-07-05 19:32:21 | Re: pgcrypto 3des failure, OpenSSL 0.9.8, Solaris 9/sparc |