Re: Bug #865: PostgreSQL 7.3 and 7.3.1 fails to compile pg_dump
| От | Tom Lane |
|---|---|
| Тема | Re: Bug #865: PostgreSQL 7.3 and 7.3.1 fails to compile pg_dump |
| Дата | |
| Msg-id | 29396.1041986076@sss.pgh.pa.us обсуждение |
| Ответ на | Bug #865: PostgreSQL 7.3 and 7.3.1 fails to compile pg_dump (pgsql-bugs@postgresql.org) |
| Ответы |
Re: Bug #865: PostgreSQL 7.3 and 7.3.1 fails to compile
|
| Список | pgsql-bugs |
pgsql-bugs@postgresql.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
В списке pgsql-bugs по дате отправления: