Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

John Paul Adrian Glaubitz glaubitz at physik.fu-berlin.de
Sun Dec 20 13:02:13 UTC 2015


On 12/20/2015 01:42 PM, Emilio Pozuelo Monfort wrote:
> I know nothing about haskell upstream, so the fact that armel got broken for so
> long even though it was pointed out by Joachim in several mails made me think
> that arm(el) development had indeed been stopped.

Sorry, but this is complete non-sense. Joachim's simply made a premature
reaction by requesting the removal of ghc:armel from the archive because
he assumed the problem was unfixable. But that's not the case, but
rather that ghc upstream haven't gotten around fixing the issue yet.

And I don't consider 4 months long time, it still worked with 7.10.2
and then Erik de Castro Lopo made an upstream change to improve ghc on
ARM without realizing that armel isn't compatible with this change. It's
simply a case of not testing your own changes. That's all.

> So your mail wasn't clear wrt whether development had been restarted/continued,
> or your patch was just a one-off that wasn't going to improve things in the long
> term.

Again, the situation is as follows: Erik was making general ARM
improvements and while doing that he broke something. He is aware of
that and realized in order to fix the problem properly, he will need
to make some larger changes which is understandable since ghc upstream
made the mistake that were lumping armel and armhf together even though
these should be considered as separate architectures.

So, the proper workaround here is simply to revert this change for
just armel and leave the patch applied for armhf where it actually
improved things.

> So while I understand that you have made an effort to fix this particular issue,
> I just wanted to make sure that this wasn't going to break again in one month
> with noone noticing or caring, and armel support breaking again. It is good that
> you have clarified that upstream is still actively working on arm*, so thanks
> for the clarification.

Of course not. Heck, I am fixing Debian on way more obscure or older
architectures like sh4 and m68k. armel is way too ubiquotous that we
should just drop it right away. Please let's keep Debian universal.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz at debian.org
`. `'   Freie Universitaet Berlin - glaubitz at physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



More information about the Pkg-haskell-maintainers mailing list