Perfect! I've update my m4 to version 1.4.13 from: http://ftp.openbsd.org/pub/OpenBSD/4.9/packages/amd64/m4-1.4.13.tgz the problem solved perfectly! Thank You !!!
# /usr/bin/gm4 --version m4 (GNU M4) 1.4.13 Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by Rene' Seindal. # # M4=/usr/bin/m4 /usr/bin/bison -d -o pl_gram.with_OpenBSD_4.9_original_m4.c gram.y # M4=/usr/bin/gm4 /usr/bin/bison -d -o pl_gram.with_GNU_m4_1.4.13.c gram.y # diff -u pl_gram.with_OpenBSD_4.9_original_m4.c pl_gram.with_GNU_m4_1.4.13.c --- pl_gram.with_OpenBSD_4.9_original_m4.c Wed Oct 19 04:55:38 2011 +++ pl_gram.with_GNU_m4_1.4.13.c Wed Oct 19 04:55:46 2011 @@ -400,7 +400,7 @@ #endif #if ! defined YYSTYPE && ! defined YYSTYPE_IS_DECLARED -typedef union +typedef union YYSTYPE #line 115 "gram.y" { core_YYSTYPE core_yystype; @@ -453,8 +453,8 @@ PLpgSQL_stmt_fetch *fetch; PLpgSQL_case_when *casewhen; } -/* Line 193 of yacc.c. */ -#line 458 "pl_gram.with_OpenBSD_4.9_original_m4.c" +/* Line 187 of yacc.c. */ +#line 458 "pl_gram.with_GNU_m4_1.4.13.c" YYSTYPE; # define yystype YYSTYPE /* obsolescent; will be withdrawn */ # define YYSTYPE_IS_DECLARED 1 @@ -479,7 +479,7 @@ /* Line 216 of yacc.c. */ -#line 483 "pl_gram.with_OpenBSD_4.9_original_m4.c" +#line 483 "pl_gram.with_GNU_m4_1.4.13.c" #ifdef short # undef short @@ -4077,7 +4077,7 @@ /* Line 1267 of yacc.c. */ -#line 4081 "pl_gram.with_OpenBSD_4.9_original_m4.c" +#line 4081 "pl_gram.with_GNU_m4_1.4.13.c" default: break; } YY_SYMBOL_PRINT ("-> $$ =", yyr1[yyn], &yyval, &yyloc); # On Wed, Oct 19, 2011 at 03:01, Tom Lane <t...@sss.pgh.pa.us> wrote: > I wrote: >> A little bit of googling suggests that this is a bug or incompatibility >> with openbsd's m4 (a tool that bison relies on): >> http://comments.gmane.org/gmane.comp.parsers.bison.bugs/2708 > > Scratch that: closer reading of the page says that the complainant was not > using some openbsd-specific copy of m4, but GNU m4 1.4.4, and that the > problem is not reproducible with newer versions of m4. So what it seems > to boil down to is "get a newer m4". Especially if you've got 1.4.4. > > regards, tom lane > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs