| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Nolan <htfoot(at)gmail(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: undefined symbol when installing pgcrypto on 16.1 |
| Date: | 2024-01-25 01:35:55 |
| Message-ID: | 246864.1706146555@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Michael Nolan <htfoot(at)gmail(dot)com> writes:
> Including --with-openssl does include the crypto library, but if I
> don't do a 'make clean' before doing a make, I get errors when
> compiling postgresql. Apparently is it always a good idea to do make
> clean when reconfiguring postgresql.
Indeed. In theory, if you use --enable-depend, you needn't do
"make clean". But I don't trust that a whole lot personally.
I find that using ccache gets most of the win with fewer assumptions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sasmit Utkarsh | 2024-01-25 03:17:30 | Clarification regarding managing advisory locks in postgresql |
| Previous Message | Michael Nolan | 2024-01-25 01:32:07 | Re: undefined symbol when installing pgcrypto on 16.1 |