Hi I'm a Haskell newbie. I just installed Haskell on Windows 7 x64 (Haskell
Platform 2013.2.0.0 containing GHC 7.6.3), and have been using
cabal-install to build/install from Hackage all the helper executables
required and/or supported by EclipseFP, the Eclipse Haskell Plugin.
All the helper
On Thu, Apr 11, 2013 at 1:19 AM, Richard A. O'Keefe o...@cs.otago.ac.nzwrote:
On 11/04/2013, at 12:56 PM, Brandon Allbery wrote:
Xcode 4.2 and on do not use /Developer at all. You have an older Xcode
on your system somehow, which does not understand newer object files; you
should remove the
The basic problem is that the University has a strict policy
that academic staff must not have root access on any machine
that is connected to the University network. I was given an
administrator account so that I could resume the printer and
install (some) stuff, but /Developer is owned by root,
On Thu, Apr 11, 2013 at 7:41 PM, Richard A. O'Keefe o...@cs.otago.ac.nzwrote:
The basic problem is that the University has a strict policy
that academic staff must not have root access on any machine
that is connected to the University network. I was given an
administrator account so that I
On Apr 11, 2013, at 6:53 PM, Brandon Allbery wrote:
/Developer should not exist on a machine with Xcode 4.2 or later installed,
at all.
Unfortunately this is not completely true - there are some SDKs that still
install stuff in /Developer (NVIDIA comes to mind) but it's pretty obvious
Machine:an Intel Core 2 Duo desktop Mac.
OS: Mac OS X 10.7.4
Xcode: 4.6.1 (including command line tools)
Haskell:Haskell Platform 2012.4.0.0 64bit.pkg
downloaded today (GHC 7.4.2)
cabal update advised me to install a new cabal-install.
m%
On Wed, Apr 10, 2013 at 8:36 PM, Richard A. O'Keefe o...@cs.otago.ac.nzwrote:
/Developer/usr/bin/strip: object: /home/cshome/o/ok/.cabal/bin/cabal
malformed object (unknown load command 15)
Xcode 4.2 and on do not use /Developer at all. You have an older Xcode on
your system somehow, which
On 11/04/2013, at 12:56 PM, Brandon Allbery wrote:
Xcode 4.2 and on do not use /Developer at all. You have an older Xcode on
your system somehow, which does not understand newer object files; you should
remove the entire /Developer tree. (Xcode, in order to be distributable via
the App
Hello Albert,
On 04/01/2013 11:41 PM, Albert Y. C. Lai wrote:
On 13-04-01 06:26 AM, Roger Mason wrote:
It turned out that there was a stale version of 'array' lurking in the
ghc package db. In spite of reinstalling ghc it did not go away until I
unregistered it. I think it was persisting
Hello Brent,
On 03/31/2013 04:53 PM, Brent Yorgey wrote:
It looks like your entire Haskell Platform installation is completely
hosed. Sad to say, but I think your best bet is to simply reinstall
the Haskell Platform.
-Brent
___
Haskell-Cafe mailing
On 13-04-01 06:26 AM, Roger Mason wrote:
It turned out that there was a stale version of 'array' lurking in the
ghc package db. In spite of reinstalling ghc it did not go away until I
unregistered it. I think it was persisting because re-installing ghc
simply unpacked over the old directory
On Fri, Mar 29, 2013 at 08:05:47AM -0230, Roger Mason wrote:
Thank you for your response. 'ghc-pkg check' shows some problems:
http://pastebin.ca/2344794
On 03/28/2013 08:01 PM, Patrick Wheeler wrote:
So I printed off the requirements for pandoc on a empty ghc-7.6.2
install you can find
On Thu, 28 Mar 2013 19:08:46 +0100, Roger Mason rma...@mun.ca wrote:
I installed ghc (7.6.2) on an Arch Linux machine. I'm trying to install
pandoc via cabal but it fails:
...
Configuring text-0.11.2.3...
Warning: This package indirectly depends on multiple versions of the same
package.
Thank you for your response. 'ghc-pkg check' shows some problems:
http://pastebin.ca/2344794
On 03/28/2013 08:01 PM, Patrick Wheeler wrote:
So I printed off the requirements for pandoc on a empty ghc-7.6.2
install you can find it at:
http://hpaste.org/84794
I do not see any odd package
Hello,
On 03/29/2013 06:47 AM, Henk-Jan van Tuyl wrote:
On Thu, 28 Mar 2013 19:08:46 +0100, Roger Mason rma...@mun.ca wrote:
I installed ghc (7.6.2) on an Arch Linux machine. I'm trying to
install pandoc via cabal but it fails:
...
Configuring text-0.11.2.3...
Warning: This package
Hello,
On 03/29/2013 08:13 AM, Roger Mason wrote:
Hello,
It appears in my case that cabal may be looking in a strange place for
installed pacckages. At least, that is how I interpret the output I
just pasted here:
http://pastebin.ca/2344794
Thanks,
Roger
ghc-pkg check showed that there
Hello,
I installed ghc (7.6.2) on an Arch Linux machine. I'm trying to install
pandoc via cabal but it fails:
...
Configuring text-0.11.2.3...
Warning: This package indirectly depends on multiple versions of the same
package. This is highly likely to cause a compile failure.
package
To side step the issue, Pandoc is available via the ArchHaskell repos
(package name `haskell-pandoc`):
https://wiki.archlinux.org/index.php/Haskell_package_guidelines
-M
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
hello,
On 03/28/2013 04:11 PM, Mark Fredrickson wrote:
To side step the issue, Pandoc is available via the ArchHaskell repos
(package name `haskell-pandoc`):
https://wiki.archlinux.org/index.php/Haskell_package_guidelines
-M
Yes, I know. I wanted to avoid having a mixture of packages
So I printed off the requirements for pandoc on a empty ghc-7.6.2 install
you can find it at:
http://hpaste.org/84794
I do not see any odd package versions listed in what you posted so far.
No promise I will be able to help afterwards but it might help to see the
full log, and then again with
Hi all,
I'm having some strange issues with cabal install. Some packages
installed via `cabal install $foo` are failing for strange (and
seemingly unrelated) reasons, but install just fine when I do
something like:
cabal unpack network
cd network
cabal configure
cabal install
Below is
On Tue, Mar 12, 2013 at 3:21 PM, Tycho Andersen ty...@tycho.ws wrote:
Below is some sample output from a failing package:
ps168825:~/playground$ cabal install network
Resolving dependencies...
Configuring network-2.4.1.2...
configure: WARNING: unrecognized options: --with-compiler,
On Tue, Mar 12, 2013 at 03:28:08PM -0400, Brandon Allbery wrote:
cabal install unpacks a package into /tmp in order to build it. My guess
is your OS has /tmp mounted noexec. I don't know offhand how you override
this in cabal.
Yep, you're exactly right. Thank you! I also couldn't figure out a
Doesn't Cabal tend to install library packages under the .cabal folder? So
blowing it away gets rid of the problematic ones. (And everything else.)
On 25 Feb 2013, at 16:56, Brent Yorgey wrote:
On Sun, Feb 24, 2013 at 02:33:55PM +, Niklas Hambüchen wrote:
You are right, my ghc-7.4.2 was
On 13-03-01 05:10 AM, Malcolm Wallace wrote:
Doesn't Cabal tend to install library packages under the .cabal folder? So
blowing it away gets rid of the problematic ones. (And everything else.)
You need to perform scientific experiments to refute that claim, then see my
On Fri, Mar 1, 2013 at 12:08 PM, Albert Y. C. Lai tre...@vex.net wrote:
On 13-03-01 05:10 AM, Malcolm Wallace wrote:
Doesn't Cabal tend to install library packages under the .cabal folder?
So blowing it away gets rid of the problematic ones. (And everything
else.)
You need to perform
On Sun, Feb 24, 2013 at 02:33:55PM +, Niklas Hambüchen wrote:
You are right, my ghc-7.4.2 was broken in ghc-pkg list; I fixed the
problem by killing my .cabal folder (as so often).
Surely you mean by killing your .ghc folder? I do not see what effect
killing your .cabal folder could
Yep, I usually kill ~/.ghc and ~/.cabal for this kind of reset.
On Mon 25 Feb 2013 16:56:56 GMT, Brent Yorgey wrote:
On Sun, Feb 24, 2013 at 02:33:55PM +, Niklas Hambüchen wrote:
You are right, my ghc-7.4.2 was broken in ghc-pkg list; I fixed the
problem by killing my .cabal folder (as so
You are right, my ghc-7.4.2 was broken in ghc-pkg list; I fixed the
problem by killing my .cabal folder (as so often).
Do you know if it is possible to make ghc-pkg list print some actual
text when packages are broken instead of writing them in red (which goes
away on output redirection)?
Thanks
On 25 February 2013 01:33, Niklas Hambüchen m...@nh2.me wrote:
You are right, my ghc-7.4.2 was broken in ghc-pkg list; I fixed the
problem by killing my .cabal folder (as so often).
Do you know if it is possible to make ghc-pkg list print some actual
text when packages are broken instead of
Hi,
I just did cabal update and cabal install ghc-mod, and for some reason
it tries to install version 0.3.0 from 3 years ago:
cabal install ghc-mod -v
Reading available packages...
Choosing modular solver.
Resolving dependencies...
Ready to install ghc-mod-0.3.0
Downloading ghc-mod-0.3.0...
On 24 February 2013 12:38, Niklas Hambüchen m...@nh2.me wrote:
Hi,
I just did cabal update and cabal install ghc-mod, and for some reason
it tries to install version 0.3.0 from 3 years ago:
cabal install ghc-mod -v
Reading available packages...
Choosing modular solver.
Resolving
Hi Ozgur,
I'm missing some context here, but I'll release an updated version of
hspec ASAP ;)
Cheers,
Simon
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Hi,
I noticed a weird behaviour with cabal-install. When I run `cabal install
hspec --dry-run -v` cabal-install correctly picks hspec-1.4.3 (the latest
version).
However, when I run `cabal install ansi-terminal hspec --dry-run
-v`cabal-install tries to install hspec-0.3.0 for no apparent reason.
Aha!
I think I know why this happens.
The latest versions of ansi-terminal and hspec do not work together. Cabal
picks the latest ansi-terminal (0.6) first, then the latest hspec that
doesn't conflict with this choice is 0.3.0.
I can confirm this by the following:
$ cabal install hspec
On 25 January 2013 14:46, Ozgur Akgun ozgurak...@gmail.com wrote:
The latest versions of ansi-terminal and hspec do not work together. Cabal
picks the latest ansi-terminal (0.6) first, then the latest hspec that
doesn't conflict with this choice is 0.3.0.
If this happens because the dependency
Hi Max,
On 25 January 2013 15:58, Max Bolingbroke batterseapo...@hotmail.comwrote:
If this happens because the dependency bounds of ansi-terminal are too
tight then please send me a patch.
No, actually it happens because hspec depends on ansi-terminal-0.5.*.
I am cc'ing Simon Hengel, the
...@haskell.org] on
behalf of Eric Velten de Melo [ericvm...@gmail.com]
Sent: Tuesday, November 20, 2012 7:54 PM
To: Johan Tibell
Cc: Gregory Guthrie; haskell-cafe@haskell.org
Subject: Re: [Haskell-cafe] cabal install...
I have a dream of one day being able to install leksah without having
to downgrade ghc
Thanks for the suggestion, I’ll do that. Here goes:
I deleted the ../user/appdata/roaming/ghc and ../cabal files, an uninstalled
Haskell-platform. (No trace of anything ghc on the disk.)
Then reinstalled Haskell, and ran “cabal update”, it said there was a new
cabal-install, but trying to
You should have a ghc directory under appdata, with
i386-mingw32-7.4.2\package.conf.d under it. There GHC tracks what
packages it knows about.
Niklas
From: Gregory Guthrie
Sent: 2012-11-21 15:11
To: Johan Tibell
Cc: haskell-cafe@haskell.org
Subject: Re: [Haskell-cafe] cabal install... Trying
On Wed, Nov 21, 2012 at 9:08 AM, Gregory Guthrie guth...@mum.edu wrote:
The error seems odd to me (cabal-install-1.16.0.2 depends on
Cabal-1.16.0.3 which failed to install.), that an older version depends on
a newer one?
There was a minor bug in the Cabal library necessitating a point
[mailto:allber...@gmail.com]
Subject: Re: [Haskell-cafe] cabal install... Trying to recover
So I split it into sections, and tried the first one; it lists a lot of new
installs, and then fails
(full list at http://pastebin.com/5ywdUjgX)
You're explicitly asking it for a new version of HTTP, which
On Wed, Nov 21, 2012 at 12:06 PM, Gregory Guthrie guth...@mum.edu wrote:
OK; I took HTTP out, but still get the same error;
cabal: The following packages are likely to be broken by the
reinstalls:
QuickCheck-2.4.2
haskell-platform-2012.4.0.0
Use
! ☺
---
Subject: Re: [Haskell-cafe] cabal install... Trying to recover
This is the important part, and what I noted immediately afterward --- did you
happen to notice there was anything in the message after that first part?
(Although I'm not asking this first so it also may not actually exist, I
Hmm,
Now when I tried to run Leksah, I get not only some broken packages (which I
can avoid for my current project), but:
command line: cannot satisfy -package-id
base-4.5.1.0-7c83b96f47f23db63c42a56351dcb917:
base-4.5.1.0-7c83b96f47f23db63c42a56351dcb917 is unusable due to missing or
On Tue, Nov 20, 2012 at 4:10 PM, Gregory Guthrie guth...@mum.edu wrote:
Hmm,
Now when I tried to run Leksah, I get not only some broken packages (which
I can avoid for my current project), but:
** **
command line: cannot satisfy -package-id
On Tue, Nov 20, 2012 at 1:10 PM, Gregory Guthrie guth...@mum.edu wrote:
Hmm,
Now when I tried to run Leksah, I get not only some broken packages (which
I can avoid for my current project), but:
** **
command line: cannot satisfy -package-id
I have a dream of one day being able to install leksah without having
to downgrade ghc. Right now I can't even install cabal-dev with cabal.
It will break ghc if I do.
2012/11/20 Johan Tibell johan.tib...@gmail.com:
On Tue, Nov 20, 2012 at 1:10 PM, Gregory Guthrie guth...@mum.edu wrote:
Hmm,
Hi all,
I've created bug fix release candidates for Cabal and cabal-install to
address the bugs found after the release. If everyone could take some
time to try them out, especially those who had issues with the
previous releases. To install the release candidates run:
cabal install
On Mon, Oct 15, 2012 at 7:16 PM, Johan Tibell johan.tib...@gmail.com wrote:
Hi all,
I've created bug fix release candidates for Cabal and cabal-install to
address the bugs found after the release.
Here's the list of fixed bugs:
Fixed since cabal-install-1.16.0:
* Fix installing from custom
Hi Johan,
On Mon, Oct 15, 2012 at 10:18 PM, Johan Tibell johan.tib...@gmail.com wrote:
Fixed since Cabal-1.16.0.1:
* Fixed warnings on the generated Paths module. The warnings are
generated by the flag '-fwarn-missing-import-lists'.
I tested this issue with Cabal-1.16.0.2 and the issue was
On Tue, Aug 28, 2012 at 6:09 PM, Bryan O'Sullivan b...@serpentine.com wrote:
On Mon, Aug 27, 2012 at 10:52 AM, Bryan O'Sullivan b...@serpentine.com
wrote:
The reason you're seeing build breakage is that the .cabal files of the
broken packages were edited in-place without communicating with
On Tue, Aug 28, 2012 at 6:09 PM, Bryan O'Sullivan b...@serpentine.com
wrote:
On Mon, Aug 27, 2012 at 10:52 AM, Bryan O'Sullivan
b...@serpentine.com
wrote:
Not to flog a dead horse, but:
...
Not to flog a dead horse, but:
All our builds broke again yesterday due to this bug. The package was
On Mon, Aug 27, 2012 at 10:52 AM, Bryan O'Sullivan b...@serpentine.comwrote:
The reason you're seeing build breakage is that the .cabal files of the
broken packages were edited in-place without communicating with any of the
package authors.
Not to flog a dead horse, but:
Just yesterday we
On Mon, Jul 30, 2012 at 3:33 PM, Ross Paterson r...@soi.city.ac.uk wrote:
On Mon, Jul 30, 2012 at 01:46:24PM +0100, Niklas Broberg wrote:
On Wed, Jul 25, 2012 at 12:22 PM, Ross Paterson r...@soi.city.ac.uk wrote:
As I understand it, the plan is to modify the following packages in
On Mon, Aug 27, 2012 at 9:57 AM, Erik Hesselink hessel...@gmail.com wrote:
I'm seeing this again, on abstract-deque-0.1.6. Ross, can you fix it again?
Hang on a second.
The reason you're seeing build breakage is that the .cabal files of the
broken packages were edited in-place without
On Mon, Aug 27, 2012 at 7:52 PM, Bryan O'Sullivan b...@serpentine.com wrote:
On Mon, Aug 27, 2012 at 9:57 AM, Erik Hesselink hessel...@gmail.com wrote:
I'm seeing this again, on abstract-deque-0.1.6. Ross, can you fix it
again?
Hang on a second.
The reason you're seeing build breakage is
On Mon, Aug 27, 2012 at 10:52:59AM -0700, Bryan O'Sullivan wrote:
On Mon, Aug 27, 2012 at 9:57 AM, Erik Hesselink hessel...@gmail.com wrote:
I'm seeing this again, on abstract-deque-0.1.6. Ross, can you fix it again?
Hang on a second.
The reason you're seeing build breakage is that
On Mon, Aug 27, 2012 at 07:39:39PM +0100, Erik Hesselink wrote:
If we do agree that we want to prevent this problem for a while (which
I'm not sure about), we should probably do it by preventing uploads
for packages like this. That way, package maintainers will know what
is going on, just like
On Mon, Aug 27, 2012 at 09:03:18PM +0100, Brent Yorgey wrote:
On Mon, Aug 27, 2012 at 10:52:59AM -0700, Bryan O'Sullivan wrote:
On Mon, Aug 27, 2012 at 9:57 AM, Erik Hesselink hessel...@gmail.com wrote:
I'm seeing this again, on abstract-deque-0.1.6. Ross, can you fix it
again?
On Mon, Aug 27, 2012 at 11:39 AM, Erik Hesselink hessel...@gmail.comwrote:
Yes, you are right. So the question is how long to support systems
with the old cabal 0.10. This is the one included with the previous
haskell platform (and thus lots of linux distro's), which is less than
a year old.
On Mon, Aug 27, 2012 at 4:23 PM, Bryan O'Sullivan b...@serpentine.comwrote:
On Mon, Aug 27, 2012 at 11:39 AM, Erik Hesselink hessel...@gmail.comwrote:
Yes, you are right. So the question is how long to support systems
with the old cabal 0.10. This is the one included with the previous
Well, this one looks like it was my fault because I never read this thread
and this morning I uploaded that package (abstract-deque) with the
conditional in the test-suite. The reason this conditional isn't there now
is that the package was hacked in place to remove tests, which is fine.
On Aug 27, 2012 8:40 PM, Erik Hesselink hessel...@gmail.com wrote:
The other question is how useful test suites in a released package
are. Aren't they much more useful (and used more often) in source
repositories?
Having tests available in a released package allows one to verify that the
On 8/27/12 6:27 PM, Tristan Seligmann wrote:
On Aug 27, 2012 8:40 PM, Erik Hesselink hessel...@gmail.com wrote:
The other question is how useful test suites in a released package
are. Aren't they much more useful (and used more often) in source
repositories?
Having tests available in a
On Wed, Jul 25, 2012 at 12:22 PM, Ross Paterson r...@soi.city.ac.uk wrote:
As I understand it, the plan is to modify the following packages in
hackage in-situ to remove the test sections (which contain the troublesome
conditionals):
HUnit-1.2.5.0
bloomfilter-1.2.6.10
codemonitor-0.1
On Mon, Jul 30, 2012 at 01:46:24PM +0100, Niklas Broberg wrote:
On Wed, Jul 25, 2012 at 12:22 PM, Ross Paterson r...@soi.city.ac.uk wrote:
As I understand it, the plan is to modify the following packages in
hackage in-situ to remove the test sections (which contain the troublesome
On Fri, Jul 20, 2012 at 10:02:18AM +0100, Ross Paterson wrote:
On Fri, Jul 20, 2012 at 09:34:16AM +0100, Simon Hengel wrote:
Hi Ross,
can you fix this on Hackage? My suggested solution is to again just
remove the test-suite sections from the cabal file, if that is fine with
Richard.
On Wed, Jul 25, 2012 at 09:43:48AM +0100, Simon Hengel wrote:
On Fri, Jul 20, 2012 at 10:02:18AM +0100, Ross Paterson wrote:
On Fri, Jul 20, 2012 at 09:34:16AM +0100, Simon Hengel wrote:
Hi Ross,
can you fix this on Hackage? My suggested solution is to again just
remove the test-suite
On Mon, Jul 23, 2012 at 12:51:32PM -0500, Stephen Paul Weber wrote:
Currently you would have to do the upgrade manually, as `cabal-install
cabal-install` won't work (or alternatively edit your local
~/.cabl/packages/hackage.haskell.org/00-index.tar).
Pending a fix on hackage (hopefully)
On Monday, July 23, 2012, Simon Hengel wrote:
On Mon, Jul 23, 2012 at 12:51:32PM -0500, Stephen Paul Weber wrote:
Currently you would have to do the upgrade manually, as `cabal-install
cabal-install` won't work (or alternatively edit your local
Hi Ross,
can you fix this on Hackage? My suggested solution is to again just
remove the test-suite sections from the cabal file, if that is fine with
Richard.
The current situation is unfortunate, as it breaks almost all installs
from Hackage with cabal-install 0.10.2 / Cabal 1.10.1.0, e.g. you
Upgrading to Cabal-1.10.2.0 (or cabal-install-0.14.0 with
Cabal-1.14.0) should fix the problem.
Currently you would have to do the upgrade manually, as `cabal-install
cabal-install` won't work (or alternatively edit your local
~/.cabl/packages/hackage.haskell.org/00-index.tar).
See my other
On Fri, Jul 20, 2012 at 09:34:16AM +0100, Simon Hengel wrote:
Hi Ross,
can you fix this on Hackage? My suggested solution is to again just
remove the test-suite sections from the cabal file, if that is fine with
Richard.
I'll modify the packages in-place if there's a consensus on what to do.
On Wed, Jul 18, 2012 at 05:51:51PM -0600, Richard G. wrote:
What's the best way to fix this? I can see two options:
- Move the test stanzas to a different Cabal file, allowing users to
perform the tests with a little fiddling.
- Remove the conditional statements from the test stanzas, which
Hi all,
All cabal installs using cabal-install-0.10.2 are currently failing
for us. This is due to the cabal file for HUnit-1.2.5.0, which was
recently uploaded to hackage. The ouput I'm getting from cabal is
just:
Reading available packages...
Resolving dependencies...
cabal: Couldn't read
Hi Erik,
A similar thing happened to me with the GraphViz package. As Duncan
explained to me, the problem is that Cabal-1.10.0.0 (and I believe also
1.10.1.0) incorrectly reports an error when conditionals are used in
test suites.
Upgrading to Cabal-1.10.2.0 (or cabal-install-0.14.0 with
Hi Martijn,
Yes, upgrading will obviously fix things (we do use 0.14 on our
development machines), but we have not set up any infrastructure for
building a custom cabal on production servers. We just use the one
from the Ubuntu repositories, which uses Cabal 1.10.1.0 on oneiric. So
until we
On 18-07-12 17:37, Erik Hesselink wrote:
Hi Martijn,
Yes, upgrading will obviously fix things (we do use 0.14 on our
development machines)
Well, to me it wasn't entirely obvious that upgrading to Cabal-1.10.2.0
fixes the problem for cabal-install-0.12, and I still think this is a
good
CCing: Ross Paterson and Richard G.
On Wed, Jul 18, 2012 at 05:54:44PM +0200, Martijn Schrage wrote:
On 18-07-12 17:37, Erik Hesselink wrote:
Hi Martijn,
Yes, upgrading will obviously fix things (we do use 0.14 on our
development machines)
Well, to me it wasn't entirely obvious that
On Wed, Jul 18, 2012 at 05:16:19PM +0100, Simon Hengel wrote:
CCing: Ross Paterson and Richard G.
On Wed, Jul 18, 2012 at 05:54:44PM +0200, Martijn Schrage wrote:
On 18-07-12 17:37, Erik Hesselink wrote:
Hi Martijn,
Yes, upgrading will obviously fix things (we do use 0.14 on our
On Mar 16, 2012 3:12 PM, Ivan Lazar Miljenovic ivan.miljeno...@gmail.com
wrote:
On 17 March 2012 09:02, Erik de Castro Lopo mle...@mega-nerd.com wrote:
Ivan Lazar Miljenovic wrote:
One trivial solution is to assume ~/.cabal/bin is on the PATH and to
ignore system-wide packages, which I
Hi all,
With a base system with just ghc and cabal-install, if I try to install
bytestring-lexing I get:
$ cabal install bytestring-lexing
Resolving dependencies...
Configuring bytestring-lexing-0.4.0...
cabal: The program alex version =2.3 is required but it could not be found.
Hi,
Am Freitag, den 16.03.2012, 21:00 +1100 schrieb Erik de Castro Lopo:
With a base system with just ghc and cabal-install, if I try to install
bytestring-lexing I get:
$ cabal install bytestring-lexing
Resolving dependencies...
Configuring bytestring-lexing-0.4.0...
Joachim Breitner wrote:
no, cabal-install does not automatically install build-tools at all,
only Cabal checks them for compilation. I guess the reason is that
build-tools needs to be put on the PATH, and that is beyond the scope of
cabal-install.
This is rather sub-optimal.
One place where
On 16 March 2012 21:56, Erik de Castro Lopo mle...@mega-nerd.com wrote:
Joachim Breitner wrote:
no, cabal-install does not automatically install build-tools at all,
only Cabal checks them for compilation. I guess the reason is that
build-tools needs to be put on the PATH, and that is beyond
Alex is supplied as part of the Platform though which is the
recommended system for beginners, is Yesod currently in advance of the
Platform?
On 16 March 2012 10:56, Erik de Castro Lopo mle...@mega-nerd.com wrote:
The problem is that many of the people trying out Yesod are newcomers to
The Yesod docs all state very explicitly that we depend on the Haskell
Platform, and in particular that alex needs to be installed. However,
that doesn't stop this issue from confusing people.
I think a good short term solution could be what Alan Zimmerman did
with language-javascript: include
On 3/16/12 6:00 AM, Erik de Castro Lopo wrote:
Hi all,
With a base system with just ghc and cabal-install, if I try to install
bytestring-lexing I get:
$ cabal install bytestring-lexing
Resolving dependencies...
Configuring bytestring-lexing-0.4.0...
cabal: The program
Ivan Lazar Miljenovic wrote:
One trivial solution is to assume ~/.cabal/bin is on the PATH and to
ignore system-wide packages, which I think is even *more* sub-optimal
(why install a new version of alex when it's already available?).
The tool should only install alex in ~/.cabal/bin if alex
On 17 March 2012 09:02, Erik de Castro Lopo mle...@mega-nerd.com wrote:
Ivan Lazar Miljenovic wrote:
One trivial solution is to assume ~/.cabal/bin is on the PATH and to
ignore system-wide packages, which I think is even *more* sub-optimal
(why install a new version of alex when it's already
On 12-02-02 12:12 AM, Scott Lawrence wrote:
When running cabal install with --extra-lib-dirs=./lib, if a package is
found both in ~/.cabal/lib and ./lib, cabal seems to favor the
~/.cabal/lib one. Is there some way to specify the correct precedence to
use?
--extra-lib-dirs is for C libs only.
When running cabal install with --extra-lib-dirs=./lib, if a package is
found both in ~/.cabal/lib and ./lib, cabal seems to favor the
~/.cabal/lib one. Is there some way to specify the correct precedence to
use?
--
Scott Lawrence
signature.asc
Description: OpenPGP digital signature
I've just spent most of a morning trying to get bootstrap.sh
from the cabal-install package to work. The trick is to use
ghc-pkg init pathname to initialise the package file - simply
adding an empty package file or directory doesn't work.
Whoever is responsible for cabal-install, could you
Hello.
I can do cabal install --enable-documentation
which is nice because it does
configure, build, haddock and copy in one go,
but I don't see how to pass options
from cabal install to cabal haddock (e.g., --hyperlink-source)
Any hints appreciated, J.W.
signature.asc
Description: OpenPGP
On 2 December 2011 16:13, Johannes Waldmann waldm...@imn.htwk-leipzig.dewrote:
but I don't see how to pass options
from cabal install to cabal haddock (e.g., --hyperlink-source)
As it seems, it is not possible.
Hi,
On Mac OSX, ghc-6.12.3, I have successfully installed the 'hxt' package:
http://hackage.haskell.org/package/hxt-8.5.2
Registering hxt-9.1.4...
Installing library in /Users/user/.cabal/lib/hxt-9.1.4/ghc-6.12.3
Now when I try to install hSimpleDB (
http://hackage.haskell.org/package/hSimpleDB)
On 8 November 2011 21:58, dokondr doko...@gmail.com wrote:
Hi,
On Mac OSX, ghc-6.12.3, I have successfully installed the 'hxt' package:
http://hackage.haskell.org/package/hxt-8.5.2
Registering hxt-9.1.4...
Installing library in /Users/user/.cabal/lib/hxt-9.1.4/ghc-6.12.3
Now when I try to
This is because hSimpleDB doesn't specify version ranges on its
dependencies, when it should. Since hxt changed its module structure
going from 9.0 to 9.1, hSimpleDB doesn't build against 9.0.
You can try to build it by adding '--constraint=hxt==9.0.\*' after
your cabal-install command. You can
On 8 November 2011 22:10, Erik Hesselink hessel...@gmail.com wrote:
This is because hSimpleDB doesn't specify version ranges on its
dependencies, when it should. Since hxt changed its module structure
going from 9.0 to 9.1, hSimpleDB doesn't build against 9.0.
You can try to build it by
1 - 100 of 225 matches
Mail list logo
