Re: configure still looking for crypt()?

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: configure still looking for crypt()?
Date: 2019-08-21 20:15:47
Message-ID: 012fb5eb-abd6-09ca-4026-cd57abf64946@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-08-20 16:07, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> I noticed that configure is still looking for crypt() and crypt.h.
>> Isn't that long obsolete?
>> If so, I suggest to remove it with the attached patch.
>
> +1

done

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-08-21 20:16:22 Re: "ago" times on buildfarm status page
Previous Message Sergei Kornilov 2019-08-21 20:01:25 Re: Change ereport level for QueuePartitionConstraintValidation