I see both of my problems discussed in the list archives, but no
resolution, so I guess it's time to have my own go at it.  :)

  I installed the Debian package for AIDE a long time ago, and it's
actually been running fine for months, but I never got around to really
configuring it (the install process initialized the database, and it's
been sending daily reports with increasing degrees of cruft since then)
until today.  So I ran "aide --update" and copied the new DB over, and
ever since I did that I get this every time I run "aide -C":

Not implemented in db_readline_file 310 

  So I go to the mailing list, and the resolution for this problem seems
to be "it's fixed in the CVS".  OK, fair enough.  So I download the CVS,
and now I am running into the problem that was sort of brought up by
Richard van den Berg...the package won't build because of missing *.in
files.  Well, I ran "autoconf" and "automake" in the top-level directory
of the CVS tree, and that got me to the point where I could run
"./configure --with-mhash" without errors.  However, when I run "make",
I get this:

% make
make  all-recursive
make[1]: Entering directory `/home/john/build/aide'
Making all in src
make[2]: Entering directory `/home/john/build/aide/src'
bison -y -d -p conf -o conf_yacc.c /home/john/build/aide/src/conf_yacc.y
/home/john/build/aide/src/conf_yacc.y:144.23-154.5: type clash (`i' `s') on default 
action
/home/john/build/aide/src/conf_yacc.y:154.7: parse error, unexpected ":", expecting 
";" or "|"
/home/john/build/aide/src/conf_yacc.y:217.23: parse error, unexpected ":", expecting 
";" or "|"
/home/john/build/aide/src/conf_yacc.y:251.1-2: parse error, unexpected "%%", expecting 
";" or "|"
make[2]: *** [conf_yacc.c] Error 1
make[2]: Leaving directory `/home/john/build/aide/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/john/build/aide'
make: *** [all-recursive-am] Error 2
%

  Unfortunately, this is where the fact that I'm not a programmer
finally brings me to a halt.  I've never used autoconf/automake before
(well, not directly anyway) and I pretty much fiddled my way this far
along with some lucky guesses, but I have no idea what this means.  :) 

-- 
------------------------------------------------------------------------
 John Buttery
                                     (Web page temporarily unavailable)
------------------------------------------------------------------------

Reply via email to