Solaris getopt_long and PostgreSQL - Mailing list pgsql-hackers

From Chuck McDevitt
Subject Solaris getopt_long and PostgreSQL
Date
Msg-id 2106D8DC89010842BABA5CD03FEA4061B249C901@EXVMBX018-10.exch018.msoutlookonline.net
Whole thread
Responses Re: Solaris getopt_long and PostgreSQL
List pgsql-hackers

About a year ago, you talked to the PostgreSQL people about some problem with Solaris getopt_long, and they changed the build to use the internal getopt_long instead of the Solaris one?

 

What was the problem with Solaris getopt_long?  Does the problem still exist in Solaris 10?

 

My users are unhappy at the change, since normal getopt_long reorders the args, and apparently the built-in one doesn’t, so “psql database –p port” no longer works, since it treats –p as the user name.

 

I don’t know if I should revert that change, or port netBSD getopt_long and replace the PostgreSQL one with that.

pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: small but useful patches for text search
Next
From: Alvaro Herrera
Date:
Subject: Ignore -- testing message-id on footer