Hello Matthew,
I just received this bug-report for Debian. Please keep
[email protected] in the cc: for tracking.
On Mon, Mar 30, 2009 at 05:09:30PM -0700, Daniel Schepler wrote:
> Package: ike
> Version: 2.1.4+dfsg-1
> Severity: serious
>
> From my pbuilder build log:
@Daniel: Next time please ass the version of g++ you're using, since
gcc-4.3.2-2 is what's causing the problem. I think the handling of
#include files and/or forward-definitions was changed.
> ...
> [ 18%] Building CXX object source/iked/CMakeFiles/iked.dir/conf.parse.o
> [ 19%] Building CXX object source/iked/CMakeFiles/iked.dir/conf.token.o
> In file included from /tmp/buildd/ike-2.1.4+dfsg/source/iked/iked.h:82,
> from conf.token.ll:48:
> conf.parse.yy:67: error: ISO C++ forbids declaration of 'BDATA' with no type
> conf.parse.yy:67: error: expected ';' before '*' token
> conf.parse.hpp:277: error: expected `)' before '&' token
> conf.parse.hpp:437: error: ISO C++ forbids declaration of 'IKED' with no type
> conf.parse.hpp:437: error: expected ';' before '&' token
> In file included from conf.token.ll:48:
> /tmp/buildd/ike-2.1.4+dfsg/source/iked/iked.h:151: error: 'IKED' has not been
> declared
> conf.token.ll: In function 'yy::conf_parser::token::yytokentype
> yylex(yy::conf_parser::semantic_type*,
> yy::location*, IKED&)':
> conf.token.ll:261: error: 'union yy::conf_parser::semantic_type' has no
> member named 'bval'
The Scanner/Lexer/Tokenizer conf.token.ll #includes "iked.h"
iked.h:82 #include "conf.parser.hpp"
iked.h:101 #include "libidb.h"
iked.h:342 typedef class _IKED { ... } IKED
conf.parse.yy:67 uses BDARA
And here is the cycle:
* The parser .hpp file needs BDATA and IKED
* IKED is defined in "iked.h" which needs the parser
The depenency on BDATA can be solved by putting a
%top{
#include "libidb.h"
}
in conf.token.ll, but the cycle on IKED is more tricky. I don't see an
easy solution and I'm to tired noew to continue.
BYtE
Philipp
--
Philipp Matthias Hahn <[email protected]>
GPG/PGP: 9A540E39 @ keyrings.debian.org
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
