Bug#751150: fix luajit-related FTBFS
On Thu, 26 Jun 2014, Norbert Preining wrote:
> I have already patches in our git to disable luajittex on
> x32, mips64, mips64el via blacklist, so that is fine.
Erm yes, but please add m68k then.
> On Wed, 25 Jun 2014, Thorsten Glaser wrote:
> > the attached patch should fix the problem for all current and
> > future architectures by using a *white*list for the JIT.
>
> If we go for whitelist, then we should *explicitely* search for those
> archs that allow for building luajit - not a combination of those
Right. I only had made an initial list, and would gladly
leave maintaining the list to the expert, i.e. you. But
I’m deeply convinced that a whitelist, not a blacklist,
is the way to go whenever there is a per-architecture
switch in Debian, especially considering that there are
new (and new-old) ports popping up every now and then.
(Did you know we have a kNetBSD and an Interix port?
Although both are dead at this point. Also, avr32, which
may or may not be revived at some point.)
> For now we are at the blacklist, because I don't want to dig out
> which of the arch/os combinations can build luajit(tex).
Would it help if I dug those out of the actual build logs
served on buildd.debian{,-ports}.org and provided a better
list?
Thanks,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Reply to: