Sanity checking for ./configure options? - Mailing list pgsql-hackers

From Jim Nasby
Subject Sanity checking for ./configure options?
Date
Msg-id 56B29531.4080506@BlueTreble.com
Whole thread Raw
Responses Re: Sanity checking for ./configure options?
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: pg_dump data structures for triggers
Next
From: Kouhei Kaigai
Date:
Subject: Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c)