On Wed, Feb 03, 2016 at 06:02:57PM -0600, Jim Nasby wrote: > 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?
That seems like a good idea. I've been getting rejection to happen with phrases like --with-pgport=${PGPORT:?} which while it looks a little odd, only adds 4 characters to each shell variable. Cheers, David. -- David Fetter <da...@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers