antlr3 on slow machines (was Re: Log for attempted build of forked-daapd

antlr3 on slow machines (was Re: Log for attempted build of forked-daapd_22.0-1 on m68k (dist=unstable))

To: debian-java@lists.debian.org
Cc: debian-68k@lists.debian.org, Bálint Réczey <balint@balintreczey.hu>
Subject: antlr3 on slow machines (was Re: Log for attempted build of forked-daapd_22.0-1 on m68k (dist=unstable))
From: Thorsten Glaser <tg@mirbsd.de>
Date: Tue, 24 Feb 2015 12:23:22 +0000 (UTC)
Message-id: <[🔎] Pine.BSM.4.64L.1502241222160.13375@herc.mirbsd.org>
In-reply-to: <CAK0Odpw14g7FZyBCAghU0Vpttw-YXER6V0YJO+3xG9HG+akCtQ@mail.gmail.com>
References: <CAK0Odpw14g7FZyBCAghU0Vpttw-YXER6V0YJO+3xG9HG+akCtQ@mail.gmail.com>

Dear Java maintainers,

Bálint Réczey dixit:

>Not that I am lazy but I think instead of patching every package using
>antlr antlr itself should be patched to use higher default timeouts on
>slow platforms.

can we please get some sort of feedback on this?
Revisiting because the next forked-daapd build failed.

Thanks,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.		-- Andreas Bogk über boehm-gc in d.a.s.r

Reply to:

Follow-Ups:
- Re: antlr3 on slow machines (was Re: Log for attempted build of forked-daapd_22.0-1 on m68k (dist=unstable))
  - From: Emmanuel Bourg <ebourg@apache.org>

Prev by Date: Re: Please help freeing libcolt-java
Next by Date: Re: antlr3 on slow machines (was Re: Log for attempted build of forked-daapd_22.0-1 on m68k (dist=unstable))
Previous by thread: Re: Looking for help: syncany dependencies
Next by thread: Re: antlr3 on slow machines (was Re: Log for attempted build of forked-daapd_22.0-1 on m68k (dist=unstable))
Index(es):
- Date
- Thread