Hi, Am Mittwoch, den 03.12.2014, 23:02 +0100 schrieb Joachim Breitner: > Trying to use it, but ghc fails to install in the schroot, and using > just dd-schroot-cmd, I cannot debug this. Does installing ghc work > properly for you? > > $ dd-schroot-cmd -c ghc apt-get install ghc > Reading package lists... > Building dependency tree... > Reading state information... > ghc is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. > 1 not fully installed or removed. > Conf ghc (7.6.3-20 Debian:unstable [armhf]) > Do it for real [Y/n]: > Reading package lists... > Building dependency tree... > Reading state information... > ghc is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Download complete and in download only mode > Reading package lists... > Building dependency tree... > Reading state information... > ghc is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Setting up ghc (7.6.3-20) ... > Illegal instruction > Illegal instruction > dpkg: error processing package ghc (--configure): > subprocess installed post-installation script returned error exit status 132 > Errors were encountered while processing: > ghc > E: Sub-process /usr/bin/dpkg returned an error code (1) > Command apt-get --assume-yes -o Dpkg::Options::=--force-confnew install -- ghc exited with exit code 1. there is more things strage with this machine. The above was the "sid" schroot (presuambly arm64). On the armel chroot on that machine I can install ghc, but cannot run it successfully: ~/ghc-7.8.20141119 $ ghc Illegal instruction ~/ghc-7.8.20141119 $ ghc --version Illegal instruction (This is calling the ghc from the package from unstable.) Should I use a different machine to debug armel build failures? Or is ghc in unstable (and hence testing) that broken on armel? Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part