configure still looking for crypt()?

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: configure still looking for crypt()?
Date: 2019-08-20 12:29:00
Message-ID: 21f88934-f00c-27f6-a9d8-7ea06d317781@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

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

Attachment Content-Type Size
0001-Remove-configure-crypt-detection.patch text/plain 37.5 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-08-20 12:59:52 mingw32 floating point diff
Previous Message Alexander Korotkov 2019-08-20 11:48:37 Re: Make SQL/JSON error code names match SQL standard