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

2015-12-21 Thread Erik de Castro Lopo
Joachim Breitner wrote: > Am Sonntag, den 20.12.2015, 13:30 +0100 schrieb John Paul Adrian Glaubitz: > > > > 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

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

2015-12-20 Thread John Paul Adrian Glaubitz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/20/2015 11:02 PM, Joachim Breitner wrote: > ah, I was mislead by the mail address you use, but you are an > uploading DD – so since you have built it anyways, why don’t you > simply upload it? No problem, will do. Just currently test-building

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

2015-12-20 Thread Emilio Pozuelo Monfort
On 20/12/15 14:02, John Paul Adrian Glaubitz wrote: > 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)

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

2015-12-20 Thread John Paul Adrian Glaubitz
Emilio, On 12/20/2015 11:42 PM, Emilio Pozuelo Monfort wrote: > Cool. So now worrying about the situation and long-term status of a key > package > in a release architecture is called nonsense. Way to go. Could you just please stop trolling, you're not helping, ok? ARM is not dead by far

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

2015-12-20 Thread Joachim Breitner
Am Sonntag, den 20.12.2015, 13:30 +0100 schrieb John Paul Adrian Glaubitz: > > 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

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

2015-12-20 Thread Joachim Breitner
Dear haskell-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

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

2015-12-20 Thread 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

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

2015-12-20 Thread John Paul Adrian Glaubitz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Joachim! On 12/20/2015 10:36 PM, Joachim Breitner wrote: > 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

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

2015-12-20 Thread Joachim Breitner
Hi, Am Sonntag, den 20.12.2015, 22:52 +0100 schrieb John Paul Adrian Glaubitz: > Hi Joachim! > > On 12/20/2015 10:36 PM, Joachim Breitner wrote: > > 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,

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

2015-12-20 Thread John Paul Adrian Glaubitz
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

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

2015-12-20 Thread 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

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

2015-12-20 Thread John Paul Adrian Glaubitz
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

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

2015-12-20 Thread 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

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

2015-12-20 Thread John Paul Adrian Glaubitz
On 12/20/2015 11:09 AM, John Paul Adrian Glaubitz wrote: > 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: PS: I will clean the patch up after I have verified it to work. So please don't add it

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

2015-12-20 Thread Emilio Pozuelo Monfort
On 20/12/15 11:09, John Paul Adrian Glaubitz wrote: > 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

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

2015-12-20 Thread John Paul Adrian Glaubitz
On 12/20/2015 11:18 AM, John Paul Adrian Glaubitz wrote: > PS: I will clean the patch up after I have verified it to work. > So please don't add it as-is. Alright, the fix works. Attaching a debdiff with my suggested changes. As I said before, this package should be built on an armel box and

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

2015-12-07 Thread Joachim Breitner
Hi, this is unfortunate, but known. GHC (and hence all of Haskell) will be removed from the archive soonish. See  https://lists.debian.org/debian-arm/2015/11/msg00010.html and https://lists.debian.org/debian-arm/2015/12/msg00020.html Greetings, Joachim Am Freitag, den 04.12.2015, 11:14 +0100

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

2015-12-04 Thread Emilio Pozuelo Monfort
Source: ghc Version: 7.10.3-2 Severity: serious Your package failed to build on armel: "inplace/bin/ghc-stage1" -static -H32m -O -lffi -optl-pthread -optl-B/usr/bin/ld.gold -Iincludes -Iincludes/dist -Iincludes/dist-derivedconstants/header -Iincludes/dist-ghcconstants/header -Irts