Package: flexml
Version: 1.3-1
Severity: serious

And you thought you'd get rid of me so easily?  flexml fails to build
on AMD64.  According to a quick search, it seems this is a problem in
your code.  See
   #358174 - ]] in comments screw up flex's generated C code

I might be wrong though.

> Automatic build of flexml_1.3-1 on em64t by sbuild/amd64 1.106
...
> Writing XML processor onto `flexml-act.l'.
> /usr/bin/flex -B -s -v -oflexml-act.c flexml-act.l
> flex version 2.5.33 usage statistics:
>   scanner options: -svB8 -Cem -oflexml-act.c
>   1003/2000 NFA states
>   392/1000 DFA states (1879 words)
>   93 rules
>   Compressed tables always back-up
>   25/40 start conditions
>   636 epsilon states, 395 double epsilon states
>   15/100 character classes needed 234/500 words of storage, 57 reused
>   10019 state/nextstate pairs created
>   895/9124 unique/duplicate transitions
>   433/1000 base-def entries created
>   1365/2000 (peak 3109) nxt-chk entries created
>   287/2500 (peak 2091) template nxt-chk entries created
>   1 empty table entries
>   47 protos created
>   41 templates created, 207 uses
>   51/256 equivalence classes created
>   7/256 meta-equivalence classes created
>   8 (13 saved) hash collisions, 554 DFAs equal
>   0 sets of reallocations needed
>   3903 total table entries needed
> gcc -Wall -ansi -pedantic -O2 -g   -c -o flexml-act.o flexml-act.c
> flexml-act.c:1101: error: expected identifier or '(' before ']' token
> flexml-act.c: In function 'yy_init_buffer':
> flexml-act.c:2583: warning: implicit declaration of function 'fileno'
> flexml-act.l: In function 'fail':
> flexml-act.l:618: warning: implicit declaration of function 'vsnprintf'
> make[1]: *** [flexml-act.o] Error 1
> make[1]: Leaving directory `/build/tbm/flexml-1.3'

The .c file looks like this:

#line 209 "flexml-act.l"
/* State names. */
const char* *statenames=NULL;
#line 1101 "flexml-act.c"
]]

#define INITIAL 0


-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to