Re: 7.3.3 COMPILE FAILURE: pg_dump (fwd) - Mailing list pgsql-hackers

From Larry Rosenman
Subject Re: 7.3.3 COMPILE FAILURE: pg_dump (fwd)
Date
Msg-id 78550000.1055774915@lerlaptop.iadfw.net
Whole thread Raw
In response to Re: 7.3.3 COMPILE FAILURE: pg_dump (fwd)  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: 7.3.3 COMPILE FAILURE: pg_dump (fwd)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers

--On Monday, June 16, 2003 16:51:04 +0200 Peter Eisentraut 
<peter_e@gmx.net> wrote:

> Where did getopt_long() come from and why is there no header file to go
> along with it?
I haven't had a chance to find this, I'll try tonight.  You are welcom to 
use
your peter_e account on lerami.lerctr.org if you'd like.

LER

>
> 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.
>>
>>



-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749





pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [INTERFACES] Some quick notes about extending libpq for new
Next
From: Tom Lane
Date:
Subject: Re: [INTERFACES] Some quick notes about extending libpq for new protocol