Sanity checking for ./configure options?

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Sanity checking for ./configure options?
Date: 2016-02-04 00:02:57
Message-ID: 56B29531.4080506@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I just discovered that ./configure will happily accept '--with-pgport='
(I was actually doing =$PGPORT, and didn't realize $PGPORT was empty).
What you end up with is a compile error in guc.c, with no idea why it's
broken. Any reason not to have configure or at least make puke if pgport
isn't valid?
--
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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kouhei Kaigai 2016-02-04 00:43:10 Re: CustomScan under the Gather node?
Previous Message Tom Lane 2016-02-03 23:16:01 Re: Idle In Transaction Session Timeout, revived