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
Hi,
Am Samstag, den 05.11.2011, 16:21 +0100 schrieb Daniel Fischer:
On Saturday 05 November 2011, 16:00:40, Ivan Lazar Miljenovic wrote:
On 6 November 2011 01:52, Victor Miller victorsmil...@gmail.com wrote:
Lately whenever I try to install a cabal package it fails with the
following
Lately whenever I try to install a cabal package it fails with the
following error message:
Could not find module `Control.Monad.State':
Perhaps you haven't installed the profiling libraries for
package `mtl-2.0.1.0'?
Use -v to see a list of the files searched for.
The strange thing
On 6 November 2011 01:52, Victor Miller victorsmil...@gmail.com wrote:
Lately whenever I try to install a cabal package it fails with the
following error message:
Could not find module `Control.Monad.State':
Perhaps you haven't installed the profiling libraries for
package `mtl-2.0.1.0'?
On Saturday 05 November 2011, 16:00:40, Ivan Lazar Miljenovic wrote:
On 6 November 2011 01:52, Victor Miller victorsmil...@gmail.com wrote:
Lately whenever I try to install a cabal package it fails with the
following error message:
Could not find module `Control.Monad.State':
14 matches
Mail list logo
