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

[Joachim Breitner]

Dear debian-arm,

Adrian has invested the time and come up with a way to keep GHC alive
on armel. (Thanks a lot!)

Unfortunately, there was a race condition with him coming up with a
solution and my removal bug being acted upon by the ftp-masters, which
now means that we have to re-bootstrap GHC on armel to get Adria’s fix
in. Due to the restricted possibility of installing additional and out-
of-archive-packages in the porterbox schroots, I cannot do that dance.

Does any DD on this list have full access to a sufficiently strong
armel machine and is willing to doe the steps as described by Adrian,
described in the mail below? That would be great!

Thanks,
Joachim

Am Sonntag, den 20.12.2015, 11:09 +0100 schrieb John Paul Adrian
Glaubitz:
> Hi!
> 
> So, here's my suggestion on how to fix this issue.
> 
> First, copy the attached patch to the ghc source package but do
> not add it to the series file. Instead, add the following to
> debian/rules:
> 
> ifeq (armel,$(DEB_HOST_ARCH))
> 
>         patch -p1 < debian/patches/armel-revert-ticket-10375.patch
> endif
> 
> This will revert the fix from upstream ticket 10375 but only for
> armel which will make the package build on armel again (I am
> currently
> doing a testbuild to verify this but it's still building after two
> days on armel on qemu).
> 
> Then manually build ghc on an armel machine with the above changes
> in a prepared changeroot with the build dependencies taken from
> snapshots.debian.org. This way we workaround the fact that ghc
> is BD-Uninstallable on armel.
> 
> Then create a new version of hscolour (can be just a cosmetic change
> just so that we can create a new package version) and build and
> upload
> the package manually on armel.
> 
> This should resolve this issue and make ghc build all the haskell
> packages on armel again.
> 
> I have also talked to upstream and the general opinion is that ARM
> support generally still needs lots of work, independent of this
> particular bug now so I assume that in the future, we will be able
> to drop this workaround again and hopefully have ghc's build system
> differenriate between armel and armhf which is what would have
> prevented
> this regression in the first place.
> 
> Cheers,
> Adrian
> 
-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-haskell-maintainers/attachments/20151220/26134b88/attachment.sig>