From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Vincas Dargis <vindrg(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz> |
Subject: | Re: Issues cross-compiling libpq 14.x to MacOS armv8 |
Date: | 2021-11-30 21:33:14 |
Message-ID: | 1636357.1638307994@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I wrote:
> It seems like a useful test when *not* cross compiling, which is most
> of the time. I'd just wrap that bit in
> if test "$cross_compiling" = no; then
Or actually, since we should print something, it looks like this will do:
diff --git a/configure.ac b/configure.ac
index a5c10b8d56..7257afda20 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2287,6 +2287,8 @@ if test x"$with_ssl" = x"openssl" ; then
AC_MSG_RESULT([OpenSSL])
elif test x"$PORTNAME" = x"win32" ; then
AC_MSG_RESULT([Windows native])
+elif test x"$cross_compiling" = x"yes"; then
+ AC_MSG_RESULT([assuming /dev/urandom])
else
AC_MSG_RESULT([/dev/urandom])
AC_CHECK_FILE([/dev/urandom], [], [])
Off to see if I can verify that before pushing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2021-11-30 21:43:12 | Re: Issues cross-compiling libpq 14.x to MacOS armv8 |
Previous Message | Tom Lane | 2021-11-30 21:04:02 | Re: Issues cross-compiling libpq 14.x to MacOS armv8 |