Dixi quod…

>antlr3  RSP.g
>warning(205): RSP.g:1:8: ANTLR could not analyze this decision in rule Tokens; 
>often this is because of recursive rule references visible from the left edge 
>of alternatives.  ANTLR will re-analyze the decision with a fixed lookahead of 
>k=1.  Consider using "options {k=1;}" for that decision and possibly adding a 
>syntactic predicate.
>error(10):  internal error: 
>org.antlr.tool.Grammar.createLookaheadDFA(Grammar.java:1279): could not even 
>do k=1 for decision 12; reason: timed out (>1000ms)
>
>Apparently, our buildds are too slow for this hard-coded timeout.

Hm, so what can we do here? Increase the timeout in antlr3 for
“slow” platforms? (Could it look at /proc/cpuinfo or something?
Except, that file is platform-specific… so a list of known to
be slow platforms would help.) Or is this a GCJ vs. OpenJDK issue?

Thanks,
//mirabilos (current hat: m68k buildd admin)
-- 
<igli> exceptions: a truly awful implementation of quite a nice idea.
<igli> just about the worst way you could do something like that, afaic.
<igli> it's like anti-design.  <mirabilos> that too… may I quote you on that?
<igli> sure, tho i doubt anyone will listen ;)


--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/pine.bsm.4.64l.1501020921190.6...@herc.mirbsd.org

Reply via email to