From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Cope with cross-compiling when checking for a random-number sour
Date: Tue, 30 Nov 2021 22:18:17 +0000
Message-ID: <E1msBS5-0000ZE-ML@gemulon.postgresql.org> (raw)
Cope with cross-compiling when checking for a random-number source.
Commit 16f96c74d neglected to consider the possibility of cross-compiling,
causing cross-compiles to fail at the configure stage unless you'd
selected --with-openssl. Since we're now more or less assuming that
/dev/urandom is available everywhere, it seems reasonable to assume
that the cross-compile target has it too, rather than failing.
Per complaint from Vincas Dargis. Back-patch to v14 where this came in.
Discussion: https://postgr.es/m/0dc14a31-acaf-8cae-0df4-a87339b22bd9@gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/b637101644aa84dccc7da4f30bad40452939b57a
Modified Files
--------------
configure | 5 ++++-
configure.ac | 4 +++-
2 files changed, 7 insertions(+), 2 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us
Subject: Re: pgsql: Cope with cross-compiling when checking for a random-number sour
In-Reply-To: <E1msBS5-0000ZE-ML@gemulon.postgresql.org>
References: <E1msBS5-0000ZE-ML@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox