On Fri, Jan 29, 2016 at 10:14:39PM +0900, Norbert Preining wrote: > Hi > > Big thanks, I guess it is time to reopen the asy bug, or blame it on gcc? > > I guess my next step is disabling mips for asy for the next upload, wdyt? > > Norbert > > On January 29, 2016 9:46:35 PM GMT+09:00, Julian Gilbey <j...@debian.org> > wrote: > >Tried that - no better. It fails with exactly the same error.
I've reported it upstream; John Bowman responded to the last report very quickly indeed (thanks, John!), so I suggest we wait a couple of days before disabling mips. Alternatively, one could argue that it is just this one bug - it is not the whole package which is affected - and exclude this one problematic file from the build. (We'd have to check whether there are other similarly problematic files first, obviously.) Julian
