Milter-greylist

Running FBSD-6.0-p9

I've just hit a brick wall on trying to build/install the new gl-2.1.9

Never had any problem installing previous versions, although I've only
reached gl-2.1.5-patched. Trying to re-install that older version gives me
the same error on build. Thus, I guess something has changed on my system.

Any advice on how to get by this error would be appreciated. I am an admin
and not any good at code. Here's the error I get on any of my servers
trying to install:

==============================================================
configure: creating ./config.status
config.status: creating Makefile
config.status: creating milter-greylist.spec
config.status: creating config.h
gcc -g -O2 -Wall -D_BSD_SOURCE -c milter-greylist.c
gcc -g -O2 -Wall -D_BSD_SOURCE -c pending.c
gcc -g -O2 -Wall -D_BSD_SOURCE -c sync.c
sync.c: In function `sync_send':
sync.c:255: warning: long int format, time_t arg (arg 4)
sync.c:255: warning: long int format, time_t arg (arg 4)
gcc -g -O2 -Wall -D_BSD_SOURCE -c dnsrbl.c
gcc -g -O2 -Wall -D_BSD_SOURCE -c list.c
bison -y -p`echo conf_yacc.c|sed 's/^\([^_]\{1,\}_\).*$/\1/'` conf_yacc.y
conf_yacc.y:225.11: parse error, unexpected ":", expecting ";" or "|"
conf_yacc.y:505.16: parse error, unexpected ":", expecting ";" or "|"
conf_yacc.y:505.34-507.37: $3 of `list_clause' has no declared type
conf_yacc.y:513.22-516.39: $3 of `list_clause' has no declared type
*** Error code 1

Stop in /greylist/milter-greylist-2.1.9.
==============================================================

Thanks in advance for any help. I really need this app. as it is essential
for frontline defense.

(^_^)
Happy trails,
Jack L. Stone

System Admin
Sage-american

Hi,

>>>>> On Sun, 30 Jul 2006 11:16:21 -0500
>>>>> "Jack L. Stone" <jacks@...> said:

jacks> Running FBSD-6.0-p9

jacks> I've just hit a brick wall on trying to build/install the new gl-2.1.9

jacks> Never had any problem installing previous versions, although I've only
jacks> reached gl-2.1.5-patched. Trying to re-install that older version gives me
jacks> the same error on build. Thus, I guess something has changed on my system.

I met this problem, too.  But, I've forgot to report this issue.
I believe ports/devel/bison is installed in your system.  Just doing
`pkg_delete bison' make it buildable.
It seems recent milter-greylist is not buildable with bison 1.75.  It
is buildable with bison 2.X and stock yacc.

Sincerely,

--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@...  ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/

At 02:13 AM 7.31.2006 +0900, you wrote:
>Hi,
>
>>>>>> On Sun, 30 Jul 2006 11:16:21 -0500
>>>>>> "Jack L. Stone" <jacks@...> said:
>
>jacks> Running FBSD-6.0-p9
>
>jacks> I've just hit a brick wall on trying to build/install the new gl-2.1.9
>
>jacks> Never had any problem installing previous versions, although I've only
>jacks> reached gl-2.1.5-patched. Trying to re-install that older version
gives me
>jacks> the same error on build. Thus, I guess something has changed on my
system.
>
>I met this problem, too.  But, I've forgot to report this issue.
>I believe ports/devel/bison is installed in your system.  Just doing
>`pkg_delete bison' make it buildable.
>It seems recent milter-greylist is not buildable with bison 1.75.  It
>is buildable with bison 2.X and stock yacc.
>
>Sincerely,
>
>--
>Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
>ume@...  ume@{,jp.}FreeBSD.org
>http://www.imasy.org/~ume/
>

Hajimu: Yes! That did it.... thanks!

(^_^)
Happy trails,
Jack L. Stone

System Admin
Sage-american

Jack L. Stone <jacks@...> wrote:

> bison -y -p`echo conf_yacc.c|sed 's/^\([^_]\{1,\}_\).*$/\1/'` conf_yacc.y
> conf_yacc.y:225.11: parse error, unexpected ":", expecting ";" or "|"
> conf_yacc.y:505.16: parse error, unexpected ":", expecting ";" or "|"
> conf_yacc.y:505.34-507.37: $3 of `list_clause' has no declared type
> conf_yacc.y:513.22-516.39: $3 of `list_clause' has no declared type

Here is the fix for the first two ones. I don't see the problem for the
two last issues, but maybe they are consequences.

Index: conf_yacc.y
===================================================================
RCS file: /cvsroot/milter-greylist/conf_yacc.y,v
retrieving revision 1.52
diff -U2 -r1.52 conf_yacc.y
--- conf_yacc.y 28 Jul 2006 16:44:17 -0000      1.52
+++ conf_yacc.y 30 Jul 2006 20:19:05 -0000
@@ -223,4 +223,5 @@
        ;
 dump_no_time_translation:      DUMP_NO_TIME_TRANSLATION        {
conf.c_dump_no_time_translation = 1; }
+       ;
 logexpired:   LOGEXPIRED { conf.c_logexpired = 1; }
        ;
@@ -502,6 +503,6 @@
                                acl_add_list(quotepath(path, $2,
QSTRLEN));
                        }
-
-netblock_clause:       ADDR IPADDR CIDR{
+       ;
+netblock_clause:       ADDR IPADDR CIDR {
                                acl_add_netblock(SA(&$2),
                            sizeof(struct sockaddr_in), $3);


-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Hajimu UMEMOTO <ume@...> wrote:

> It seems recent milter-greylist is not buildable with bison 1.75.  It
> is buildable with bison 2.X and stock yacc.

I hope we can fix that...

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Jack L. Stone <jacks@...> wrote:

> >I believe ports/devel/bison is installed in your system.  Just doing
> >`pkg_delete bison' make it buildable.
> Hajimu: Yes! That did it.... thanks!

Can you check if the patch I posted fix the problem with the bison you
had?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

Hi,

>>>>> On Sun, 30 Jul 2006 22:21:52 +0200
>>>>> manu@... said:

manu> Jack L. Stone <jacks@...> wrote:

> bison -y -p`echo conf_yacc.c|sed 's/^\([^_]\{1,\}_\).*$/\1/'` conf_yacc.y
> conf_yacc.y:225.11: parse error, unexpected ":", expecting ";" or "|"
> conf_yacc.y:505.16: parse error, unexpected ":", expecting ";" or "|"
> conf_yacc.y:505.34-507.37: $3 of `list_clause' has no declared type
> conf_yacc.y:513.22-516.39: $3 of `list_clause' has no declared type

manu> Here is the fix for the first two ones. I don't see the problem for the
manu> two last issues, but maybe they are consequences.

Your patch fixed the problem.  All of the four lines of error messages
went away.

Sincerely,

--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@...  ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/