Jean-Philippe Bernardy:
> Sometimes cabal install refuses to install because of mismatched versions.
> This one should be ignored though:
>
> package ghc-6.8.3 requires Cabal-1.2.4.0
> package yi-0.4 requires Cabal-1.4.0.1
Right, I constantly made sure that this is the only version mismatch I ge
> This was a fresh local darcs get... But I noticed that I was launching
> an old yi because Setup install didn't install the executable. Oh my,
> so I have a cabal problem now, too.
>
Sometimes cabal install refuses to install because of mismatched versions.
This one should be ignored though:
Jean-Philippe Bernardy wrote:
>>> You can probably get by by removing the instance defined in Yi indeed.
>>> Does ghc tell you where is the overlapping one defined?
>> Sorry for not having explored this further;
>
> Too bad, it would have helped narrowing the dependencies.
Right, I'll leave that
On Sun, Jul 6, 2008 at 7:03 PM, Kalman Noel <[EMAIL PROTECTED]> wrote:
>
> Jean-Philippe Bernardy wrote:
>> You can probably get by by removing the instance defined in Yi indeed.
>> Does ghc tell you where is the overlapping one defined?
>
> Sorry for not having explored this further;
Too bad, it
Jean-Philippe Bernardy wrote:
> You can probably get by by removing the instance defined in Yi indeed.
> Does ghc tell you where is the overlapping one defined?
Sorry for not having explored this further; I tried to remedy the
problem by caring for a clean pkg-conf, upgrading to ghc-6.8.3 on the
> Actually, I think the problem was just a dirty build directory. From a
> clean tree I now get compiler errors I've yet to resolve. (Duplicate/
> overlapping IsString instances, in case this rings a bell; perhaps cabal
> picks the wrong bytestring package or something...)
You can probably get
Jean-Philippe Bernardy schrieb:
> It feels like you don't run the correct version of the code.
> It can be tricky to do so if you track the darcs repo.
> Could you try the method described in the README file using -fhacking?
Actually, I think the problem was just a dirty build directory. From a
It feels like you don't run the correct version of the code.
It can be tricky to do so if you track the darcs repo.
Could you try the method described in the README file using -fhacking?
Cheers,
JP.
On Sun, Jul 6, 2008 at 4:43 PM, Kalman Noel <[EMAIL PROTECTED]> wrote:
>
> Some recent patch must
