Hi, Am Samstag, den 10.11.2012, 13:14 +0000 schrieb Ryan Kavanagh: > On Tue, Nov 06, 2012 at 09:35:28AM +0100, Joachim Breitner wrote: > > your xmonad package is failing to build on architectures that do not > > have support for GHCi, because you use runghc in debian/rules: > > > > General rule of thumb: Never use runghc in packaging scripts. Can you > > fix that? > > I've pushed the changes, please let me know if they're correct or need > revision. From looking at the changelog, looks good. > Yes, I tried building it in a clean experimental chroot and it FTBFS. > However, I managed to properly generate the manpage with > `dpkg-buildpackage -b' and the clean target successfully cleans up the > temporarily generated binary. > > Did something that once depended on libghc-extensible-exceptions-* loose that > dependency? I also get the following FTBFS when trying to build xmonad proper: > XMonad/Core.hs:36:8: > Could not find module `Control.Exception.Extensible' > Perhaps you haven't installed the profiling libraries for package `extensible-exceptions-0.1.1.4'? > Use -v to see a list of the files searched for. > If this is intended / not a temporary issue, let me know and I'll add it > to the B-D. Generally, do not rely on „I don’t have to depend on X because I depend on Y which depends on X“ logic; always list all build dependencies from the .cabal file. Exception: Libraries that are shipped via GHC. You can check the Provides: line in "apt-cache show ghc" if unsure. And indeed extensible-exception used to be provided by GHC, but is not any more. So you’ll have to add the build depends on that to make it compile again. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part