| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Garbage contents after running autoconf 2.69 |
| Date: | 2018-12-30 06:25:43 |
| Message-ID: | 20181230062543.GF608@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 29, 2018 at 10:36:02AM -0500, Tom Lane wrote:
> Project practice is to use plain-vanilla autoconf 2.69. Vendor
> packages tend to contain various "improvements" that will cause you
> to get different results than other committers do. Fortunately
> autoconf is pretty trivial to install: grab from the GNU archive,
> configure, make, make install should do it.
Ah, thanks. I did not know that bit.
> Hmm, I thought this was documented somewhere, but I'm not awake
> enough to remember where.
I could not find any reference on the wiki or in the code, but I may
have missed a reference of course. Anyway, I got it sorted out now.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-12-30 06:32:19 | Removing --disable-strong-random from the code |
| Previous Message | Michael Paquier | 2018-12-30 06:22:20 | Re: Poor buildfarm coverage of strong-random alternatives |