On Mar 16, 2012 3:12 PM, "Ivan Lazar Miljenovic"
wrote:
>
> On 17 March 2012 09:02, Erik de Castro Lopo 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
On 17 March 2012 09:02, Erik de Castro Lopo 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 available?).
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 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
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 the
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 wrote:
> The problem is that many of the people trying out Yesod are newcomers to
> Haskell. They are going to
On 16 March 2012 21:56, Erik de Castro Lopo 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 the scope of
>
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 wh
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...
>
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.
10 matches
Mail list logo