Hi debian-haskell, i've got a raspbian user here asking questions that
are getting beyond what I (as the main developer of raspbian but not a
haskell user) can handle.
Changes to ghc in raspbian compared to Debian armhf are minimal, just
some hacks to change the minimum cpu requirements.
Ploc wrote:
Hello Peter,
And thanks a lot for your answer.
Le 2014-11-19 02:10, peter green a écrit :
Can you please tell me what is the status of the hledger package for
raspbian ?
Not being built due to unsatisfiable build dependency on
"ghc-ghci". This is the same status as on debian armel and armhf.
My understanding is that ghc-ghci is a virtual package which is
provided by ghc on some but not all platforms representing a feature
(some kind of "interactive environment")of ghc that is available on
some but not all platforms.
Googling reveals some talk about porting ghci to arm upstream but no
evidence that anything has yet come of it.
I've searched on the internet, and I found this interesting post :
http://alenribic.com/posts/2012-08-06-running-haskell-on-raspberry-pi.html
After some searching and asking the ever so helpful Haskellers at
#Haskell for assistance, I quickly learned that there is no current
support for GHCi on ARM type architecture. Effectively, this also
means that there is no support for Template Haskell (TH).
The good news is that in 7.4.2, there is, for the first time,
support for GHCi on ARM. This is really exciting. Debian distro
also seems to have the experimental package for 7.4.2 for ARM which
I haven’t tried as yet.
As raspbian wheezy is offering GHC 7.4.1, and jessie is offering :
7.6.3, I tought that it would now be possible to build this package
for jessie.
MMM, I came across that post from 2012 too but I also came across more
recent posts saying ghci isn't supported on arm. I guess it either broke
or never quite worked properly.
Moreover, I can find that ghc is not a dependency of hledger :
https://packages.debian.org/jessie/hledger
But when you talk about build dependency, do you mean that there can
be differences in dependency depending on if we are during the build
process, or the run process ?
Right, source packages have build dependencies that is packages that
need to be present in the build environment for the package to be build.
On The page you mentioned you will find a link to the page for the
source package "haskell-hledger" from which the binary package hledger
is built. https://packages.debian.org/source/jessie/haskell-hledger
This tells you that there is a build-depends on ghc-ghci which is a
"virtual package provided by ghc" Unfortunately what packages.debian.org
doesn't tell you is that the virtual package ghc-ghci is only provided
by ghc on a subset of architectures.
You can see the build status for haskell-hledger in raspbian jessie and
debian sid at
http://buildd.raspbian.org/status/package.php?p=haskell-hledger&suite=jessie-staging
https://buildd.debian.org/status/package.php?p=haskell-hledger&suite=sid
Are you building raspbian packages on raspberries or are you using
cross compilation ?
Neither, we are building natively on more powerful arm hardware.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: https://lists.debian.org/[email protected]
