Re: Bug #865: PostgreSQL 7.3 and 7.3.1 fails to compile pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: wright(at)pair(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #865: PostgreSQL 7.3 and 7.3.1 fails to compile pg_dump
Date: 2003-01-08 00:34:36
Message-ID: 29396.1041986076@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

pgsql-bugs(at)postgresql(dot)org writes:
> Then, when I run gmake, I get the following error:

> pg_dump.c:192: elements of array `long_options' have incomplete type
> pg_dump.c:193: warning: excess elements in struct initializer after `long_options[0]'
> pg_dump.c:193: `no_argument' undeclared (first use in this function)

Apparently, our configure script thinks you have getopt_long(), but you
really don't. Can you look into the situation and figure out why
configure is confused?

It surprises me that this would happen when 7.2 worked okay --- I don't
think we changed that configure test since 7.2. Are you sure nothing
changed on your machine since you last built 7.2?

A stopgap solution is just to remove #define HAVE_GETOPT_LONG from the
pg_config.h file made by configure; but if you don't want to fight the
problem in future, you'll need to help us figure out why configure is
making the wrong choice.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message D'Arcy J.M. Cain 2003-01-08 02:51:48 Re: [ADMIN] pgdb.py is still wrong in Postgres 7.3.1 rpm
Previous Message pgsql-bugs 2003-01-08 00:03:25 Bug #865: PostgreSQL 7.3 and 7.3.1 fails to compile pg_dump