Re: [HACKERS] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.3.3 COMPILE FAILURE: pg_dump (fwd)
--On Monday, June 16, 2003 16:51:04 +0200 Peter Eisentraut [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.3.3 COMPILE FAILURE: pg_dump (fwd)
Larry Rosenman writes: 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. I'm more interested to know how you got getopt_long() onto your system, so that we don't start designing detection mechanisms based on broken/incomplete installations. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [HACKERS] 7.3.3 COMPILE FAILURE: pg_dump (fwd)
I just did an upgrade of Unixware to 7.1.3 up1 with the upgrade pack, to the best of my knowledge. I need to look further at it. --On Monday, June 16, 2003 21:00:44 +0200 Peter Eisentraut [EMAIL PROTECTED] wrote: Larry Rosenman writes: 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. I'm more interested to know how you got getopt_long() onto your system, so that we don't start designing detection mechanisms based on broken/incomplete installations. -- Peter Eisentraut [EMAIL PROTECTED] -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] 7.3.3 COMPILE FAILURE: pg_dump (fwd)
--On Monday, June 09, 2003 23:12:27 -0400 Tom Lane [EMAIL PROTECTED] wrote: Larry Rosenman [EMAIL PROTECTED] writes: 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 This implies that your system has the getopt_long() subroutine (in one library or another) but getopt.h either doesn't exist or doesn't define struct option. This is not particularly hard to believe, since getopt_long() might be installed in a nonstandard place and its header file too. CVS tip attempts to support long options with or without a system copy of getopt_long(), but I fear that it will still break on platforms like yours, because there is no separate configure check to see if we need to provide a definition of struct option. Peter, what can we do to fix that? for the record, this is a change from 7.3.2 to 7.3.3 that broke here. 7.3.2 compiled just fine. Peter has an account on this box if he wants to look around. I can also make other people accounts. LER regards, tom lane -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.3.3 COMPILE FAILURE: pg_dump (fwd)
Larry Rosenman [EMAIL PROTECTED] writes: for the record, this is a change from 7.3.2 to 7.3.3 that broke here. [ scratches head... ] I don't see anything in the CVS logs that could account for that. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] 7.3.3 COMPILE FAILURE: pg_dump (fwd)
On Tue, 10 Jun 2003, Tom Lane wrote: Larry Rosenman [EMAIL PROTECTED] writes: for the record, this is a change from 7.3.2 to 7.3.3 that broke here. [ scratches head... ] I don't see anything in the CVS logs that could account for that. It might be maintenenace related (7.1.3 UP 1 of UnixWare). I'll investigate when I get back from Houston (Fri 6/13/2003). LER regards, tom lane -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] 7.3.3 COMPILE FAILURE: pg_dump (fwd)
--On Saturday, June 07, 2003 10:42:31 -0500 Larry Rosenman [EMAIL PROTECTED] 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: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org