Re: Solaris getopt_long and PostgreSQL

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Chuck McDevitt <cmcdevitt(at)greenplum(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Solaris getopt_long and PostgreSQL
Date: 2009-03-30 10:01:28
Message-ID: 1238407288.1329.12.camel@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Tom Lane píše v so 28. 03. 2009 v 14:36 -0400:
> I wrote:
> > After reviewing this thread and the one that led up to the 8.3 behavior,
> > it seems clear that we failed to draw a distinction between getopt and
> > getopt_long when we should have. We don't like Solaris' getopt but
> > there seems no reason not to use Solaris' getopt_long. So Zdenek's
> > suggestion to change configure seems the correct fix, and I've done
> > that.
>
> So my reward for that is to find that every one of the Solaris 11
> buildfarm members is failing today:

I'm going to look on that.

Zdenek

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2009-03-30 10:11:48 8.3.5: Crash in CountActiveBackends() - lockless race?
Previous Message Dave Page 2009-03-30 08:34:31 Re: New shapshot RPMs (Mar 27, 2009) are ready for testing