Your message dated Fri, 20 Oct 2017 14:48:37 +0200
with message-id <727a677a-793a-ea23-0381-4304ad13b...@debian.org>
and subject line Re: Bug#878817: luajit: Please drop mips64el again
has caused the Debian Bug report #878817,
regarding luajit: Please drop mips64el again
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
878817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: luajit
Version: 2.1.0~beta3+dfsg-5
Severity: serious
Control: affects -1 src:neovim src:knot-resolver
neovim and knot-resolver FTBFS with luajit 2.1.0~beta3+dfsg-5:
https://buildd.debian.org/status/logs.php?pkg=neovim&arch=mips64el
https://buildd.debian.org/status/logs.php?pkg=knot-resolver&arch=mips64el
knot-resolver FTBFS on the buildd, but builds for me on eller.
21:10 < jcowgill> bunk: not sure, but i notice both failed on loongsons
21:10 < jcowgill> gcc has a few workarounds disabling some instructions since
loongson doesn't quite implement the mips isa properly
21:14 < bunk> jcowgill: that sounds like possibly related to a jit failing on
this hw
Instead of shipping code that is strongly suspected to be nonworking
on part of the supported hardware of mips64el, it is IMHO better to
disable luajit on mips64el again.
--- End Message ---
--- Begin Message ---
On Wed, 18 Oct 2017 10:23:12 +0100 James Cowgill <jcowg...@debian.org> wrote:
> Control: affects -1 - src:knot-resolver
>
> Hi,
>
> On 16/10/17 21:23, Adrian Bunk wrote:
> > Source: luajit
> > Version: 2.1.0~beta3+dfsg-5
> > Severity: serious
> > Control: affects -1 src:neovim src:knot-resolver
> >
> > neovim and knot-resolver FTBFS with luajit 2.1.0~beta3+dfsg-5:
> > https://buildd.debian.org/status/logs.php?pkg=neovim&arch=mips64el
> > https://buildd.debian.org/status/logs.php?pkg=knot-resolver&arch=mips64el
> >
> > knot-resolver FTBFS on the buildd, but builds for me on eller.
> >
> > 21:10 < jcowgill> bunk: not sure, but i notice both failed on loongsons
> > 21:10 < jcowgill> gcc has a few workarounds disabling some instructions
> > since loongson doesn't quite implement the mips isa properly
> > 21:14 < bunk> jcowgill: that sounds like possibly related to a jit failing
> > on this hw
> >
> > Instead of shipping code that is strongly suspected to be nonworking
> > on part of the supported hardware of mips64el, it is IMHO better to
> > disable luajit on mips64el again.
>
> It turns out the knot-resolver build failure had nothing to do with
> luajit (see #878976). I haven't investigated the neovim failure
> thoroughly yet.
Since there are workarounds (e.g. not enabling lua on mips64el and one of the
two failures is unrelated)
and also, neovim seems to build on a mips64el dchroot, I think closing this one
is the right thing to do
G.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
