Skip to contentSkip to conversation

postgresql: bump to 10.1

PATCH New Adam Duskett 2 participants 2 messages Nov 20, 2017 – Nov 22, 2017

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 postgresql: bump to 10.1

changes:

- Add a hash for the license file.

- PostgreSQL 10.0 and above will default to checking for /dev/urandom if an SSL library is not found, which will fail when cross compiling. The workaround is to add --disable-strong-random to the configure options if a SSL library not selected.

---
 package/postgresql/postgresql.hash | 7 ++++---
 package/postgresql/postgresql.mk   | 4 +++-
 2 files changed, 7 insertions(+), 4 deletions(-)
package/postgresql/postgresql.hash +4 -3
index e628389..e234770 100644
@@ -1,4 +1,5 @@
-# From https://ftp.postgresql.org/pub/source/v9.6.6/postgresql-9.6.6.tar.bz2.sha256
-sha256 399cdffcb872f785ba67e25d275463d74521566318cfef8fe219050d063c8154  postgresql-9.6.6.tar.bz2
+# From https://ftp.postgresql.org/pub/source/v10.1/postgresql-10.1.tar.bz2.sha256
+sha256	3ccb4e25fe7a7ea6308dea103cac202963e6b746697366d72ec2900449a5e713	postgresql-10.1.tar.bz2
+
 # License file, Locally calculated
-sha256 7dc8de32741ad1b03e21710771b55a1b9d460671d47f28a8840f917e38c66676  COPYRIGHT
+sha256	7dc8de32741ad1b03e21710771b55a1b9d460671d47f28a8840f917e38c66676	COPYRIGHT
package/postgresql/postgresql.mk +3 -1
index 50ce212..d1f231b 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-POSTGRESQL_VERSION = 9.6.6
+POSTGRESQL_VERSION = 10.1
 POSTGRESQL_SOURCE = postgresql-$(POSTGRESQL_VERSION).tar.bz2
 POSTGRESQL_SITE = http://ftp.postgresql.org/pub/source/v$(POSTGRESQL_VERSION)
 POSTGRESQL_LICENSE = PostgreSQL
@@ -56,6 +56,8 @@ endif
 ifeq ($(BR2_PACKAGE_OPENSSL),y)
 POSTGRESQL_DEPENDENCIES += openssl
 POSTGRESQL_CONF_OPTS += --with-openssl
+else
+POSTGRESQL_CONF_OPTS += --disable-strong-random
 endif
 
 ifeq ($(BR2_PACKAGE_OPENLDAP),y)
Signature · 1 line
2.13.6
#1 lore raw

PATCH 1/1 postgresql: bump to 10.1

Hello,

Quoted 4 lines

- PostgreSQL 10.0 and above will default to checking for /dev/urandom if an SSL library is not found, which will fail when cross compiling. The workaround is to add --disable-strong-random to the configure options if a SSL library not selected.

Since /dev/urandom is guaranteed to be provided on Linux systems, I believe a better solution is to pass ac_cv_file__dev_urandom=yes in POSTGRESQL_CONF_ENV, so that the PostgreSQL configure script knows that /dev/urandom will be available on the target.

Could you test this instead?

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com