[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] compile error in KDE_3_1_BRANCH
From:       David Bishop <tech () bishop ! dhs ! org>
Date:       2002-12-20 15:53:53
[Download RAW message or body]

On Friday 20 December 2002 03:06 am, Adriaan de Groot wrote:
> On Thu, 19 Dec 2002, David Bishop wrote:
> > I'm trying to compile the 3.1 branch on a fairly vanilla Redhat 7.2
> > machine. Everything else has compiled fine (libs, base, network,
> > multimedia, etc). The only thing that doesn't is kdepim.  It gets down to
> > the directory kdepim/libical/src/libicalvcal, and bombs out.  Here's the
> > start of the error: [ dbishop@pelinux4 ] $ make
> > icalvcal.lo `test -f 'icalvcal.c' || echo './'`icalvcal.c
> > In file included from icalvcal.h:30,
> >                  from icalvcal.c:42:
> > vcc.h:25: parse error before `VObject'
> > vcc.h:25: warning: no semicolon at end of struct or union
> > vcc.h:26: warning: data definition has no type or storage class
> > vcc.h:27: parse error before `yylval'
> > vcc.h:27: warning: data definition has no type or storage class
>
> This one is in the archives. The whole directory shouldn't be compiled,
> it's unused code included from the libical distribution. Basically, vcc.h
> as it is in CVS is a hacked version of what's generated by bison from
> vcc.y. If ever bison regenerates vcc.h from vcc.y, all the hacks are lost
> and so are you. Remove vcc.h and vcc.y, cvs update, chmod 444 vcc.h ;
> touch vcc.h to prevent it from being regenerated, and try again.

This did fix the problem, (of course! Adriaan's *never* wrong, hoser!).  But 
as I was using a clean cvs checkout, why did it even happen?  Is it 
--enable-final related? Or just a broken Makefile?

-- 
D.A.Bishop

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]