Re: openexr

2016-04-22 Thread John Paul Adrian Glaubitz
On 04/22/2016 12:05 PM, Andreas Schwab wrote: > John Paul Adrian Glaubitz writes: > >> I can do the same for m68k, although the FTBFS on m68k is most >> likely releated to a bug in qemu-m68k and not openexr. > > 4a80 is "tst.l %d0", pretty strange that it is ma

Re: openexr

2016-04-22 Thread Andreas Schwab
John Paul Adrian Glaubitz writes: > I can do the same for m68k, although the FTBFS on m68k is most > likely releated to a bug in qemu-m68k and not openexr. 4a80 is "tst.l %d0", pretty strange that it is marked illegal. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG

Re: openexr

2016-04-22 Thread John Paul Adrian Glaubitz
Hi Mathieu! On 04/22/2016 10:25 AM, Mathieu Malaterre wrote: > https://buildd.debian.org/status/fetch.php?pkg=openexr&arch=sparc64&ver=2.2.0-10&stamp=1461249335 > > As far as I know there are no porterbox for sparc64: I can set you up an account on a local porterbox. P

openexr

2016-04-22 Thread Mathieu Malaterre
[CC me please] I am trying to debug openexr FTBFS: https://buildd.debian.org/status/fetch.php?pkg=openexr&arch=m68k&ver=2.2.0-10&stamp=1460951911 As far as I know there are no porterbox for m68k: https://db.debian.org/machines.cgi Anyone could try to dump a full backtrace