Re: building HEAD on macos fails with #error no source of random numbers configured

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-11 18:52:57
Message-ID: a2ae619b-9f53-085e-3262-f836061fc103@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/9/16 9:53 AM, Heikki Linnakangas wrote:
>>
>> I'm not sure what --no-recursion does, but I would say that we'd
>> consider that unsupported as well.
>
> Interesting. Running config.status adds those --no-create --no-recursion
> flags automatically. You can see them in the command-line at the top of
> config.log, too. I never bothered to check what they do...

AIUI they have to do with config dependency checking (where a simple
make will detect if config needs to run again or not). I've been bitten
by this in the past as well. Maybe there's a way to get config to spit
out a warning for those options and have make filter the warning out.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2016-12-12 01:02:00 Re: Declarative partitioning - another take
Previous Message Tom Lane 2016-12-11 18:20:18 Re: Optimization for index-only scans with filter conditions