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

[Emilio Pozuelo Monfort]

On 20/12/15 13:30, John Paul Adrian Glaubitz wrote:
> On 12/20/2015 01:21 PM, Emilio Pozuelo Monfort wrote:
>> needs a lot of work != someone is doing a lot of work on it. So unless someone
>> is and you didn't say it, or you are volunteering to do it, I'm not sure how the
>> situation is going to improve.
> 
> Well, the person who made the change which broke ghc on armel said that
> and I assume he is working on it in the future. His change, on the other
> hand, improved ghc on armhf. So nothing is saying he is not improved
> ghc on armel, too.
> 
> I don't understand the point of your message. I know that someone has
> to do the work and I myself have already done a lot of work, too, not
> just ghc. The message from the ghc is simply "we know it's broken and
> we're going to fix it", that's all.
> 
> I assume ghc upstream development hasn't stopped, has it? Or what
> exactly did you try to convey here?

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.

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.

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.

Cheers,
Emilio