> 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
So my reward for that is to find that every one of the Solaris 11
buildfarm members is failing today:
pg_regress: initdb failed
Examine /export/home/tmp/pg-test/build-suncc/HEAD/pgsql.6320/src/test/regress/log/initdb.log for the reason.
Command was: "/export/home/tmp/pg-test/build-suncc/HEAD/pgsql.6320/src/test/regress/./tmp_check/install//export/home/tmp/pg-test/build-suncc/HEAD/inst/bin/initdb" -D "/export/home/tmp/pg-test/build-suncc/HEAD/pgsql.6320/src/test/regress/./tmp_check/data" -L "/export/home/tmp/pg-test/build-suncc/HEAD/pgsql.6320/src/test/regress/./tmp_check/install//export/home/tmp/pg-test/build-suncc/HEAD/inst/share/postgresql" --noclean --no-locale > "/export/home/tmp/pg-test/build-suncc/HEAD/pgsql.6320/src/test/regress/log/initdb.log" 2>&1
make: *** [check] Error 2
================== pgsql.6320/src/test/regress/log/initdb.log ===================
initdb: too many command-line arguments (first is "-L")
Try "initdb --help" for more information.
Running in noclean mode. Mistakes will not be cleaned up.
Apparently the system version of getopt_long is broken on Solaris 11.
My patience for this grows short.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Jeff Davis||Date: 2009-03-28 18:55:31|
|Subject: Re: TODO item|
|Previous:||From: Dave Page||Date: 2009-03-28 18:33:47|
|Subject: Re: 8.4 open items list|