From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dave Cramer <davecramer(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: building HEAD on macos fails with #error no source of random numbers configured |
Date: | 2016-12-09 15:43:24 |
Message-ID: | 17468.1481298204@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave Cramer <davecramer(at)gmail(dot)com> writes:
> Looking at src/port/pg_strong_random.c this would be a bug in autoconf
It looks more like self-inflicted damage from here:
> ./configure --prefix=/usr/local/pgsql/10 --enable-debug --with-python
> --with-openssl --with-libraries=/usr/local/opt/openssl/lib
> --with-includes=/usr/local/opt/openssl/include/ --no-create --no-recursion
Why are you using either --no-create or --no-recursion? The former
*definitely* breaks things:
$ ./configure --help | grep create
-n, --no-create do not create output files
Presumably the proximate cause of that error message is that configure
hasn't updated pg_config.h from some ancient version thereof, as a
consequence of this switch.
I'm not sure what --no-recursion does, but I would say that we'd
consider that unsupported as well.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-12-09 15:46:04 | Re: `array_position...()` causes SIGSEGV |
Previous Message | Alvaro Herrera | 2016-12-09 14:52:09 | Re: tzdata 2016j |