Re: 7.3.3 COMPILE FAILURE: pg_dump (fwd)

Where did getopt_long() come from and why is there no header file to go
along with it?

Larry Rosenman writes:

>
> --On Saturday, June 07, 2003 10:42:31 -0500 Larry Rosenman <ler@lerctr.org>
> wrote:
>
> > cc -O -g -I../../../src/interfaces/libpq -I../../../src/include
> > -I/usr/local/include -DBINDIR=\"/usr/local/pgsql/bin\"  -c -o pg_dump.o
> > pg_dump.c UX:cc: WARNING: debugging and optimization mutually exclusive;
> > -O disabled UX:acomp: ERROR: "pg_dump.c", line 192: incomplete
> > struct/union/enum option: long_options UX:acomp: ERROR: "pg_dump.c", line
> > 193: too many struct/union initializers UX:acomp: ERROR: "pg_dump.c",
> > line 193: cannot recover from previous errors gmake[3]: *** [pg_dump.o]
> > Error 1
> > gmake[3]: Leaving directory
> > `/home/ler/pg-dev/postgresql-7.3.3/src/bin/pg_dump' gmake[2]: *** [all]
> > Error 2
> > gmake[2]: Leaving directory `/home/ler/pg-dev/postgresql-7.3.3/src/bin'
> > gmake[1]: *** [all] Error 2
> > gmake[1]: Leaving directory `/home/ler/pg-dev/postgresql-7.3.3/src'
> > gmake: *** [all] Error 2
> > $
> > on UnixWare 7.1.3
>
> modifying pg_config.h to NOT define GETOPT_LONG fixes it.
>
>
>

-- 
Peter Eisentraut   peter_e@gmx.net