aboutsummaryrefslogtreecommitdiff
path: root/src/backend/jit/llvm/llvmjit_error.cpp
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-11-30 17:18:04 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2021-11-30 17:18:04 -0500
commit175edafd1f30a78643359b56c5545b5e7aabfb50 (patch)
treec3e08ed290a0519c14ab03b91c6e5b9cf178943c /src/backend/jit/llvm/llvmjit_error.cpp
parent5550a9c385198ac51d2f3b17be2f6ff9f886d76d (diff)
downloadpostgresql-175edafd1f30a78643359b56c5545b5e7aabfb50.tar.gz
postgresql-175edafd1f30a78643359b56c5545b5e7aabfb50.zip
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
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_error.cpp')
0 files changed, 0 insertions, 0 deletions