On Wed, 1 Oct 2008, Mitchell, Neil wrote:
The error comes from using QuickCheck 2, which happens to
also use the
operator (). I can see two ways to solve the problem:
(1) Add 2 after QuickCheck in the Wired.cabal file.
(2) Add hiding (()) after import Test.QuickCheck in
On Wed, 2008-10-01 at 03:04 +0200, Cetin Sert wrote:
Hi,
what is the best action to take if a package from hackage fails to
build? Is there a recommended/established common way to deal with
build failures/runtime bugs etc.?
Most packages specify a maintainer which is conventionally an email
Hi Cetin!
Glad to see at least one person trying my package :)
The error comes from using QuickCheck 2, which happens to also use the operator
(). I can see two ways to solve the problem:
(1) Add 2 after QuickCheck in the Wired.cabal file.
(2) Add hiding (()) after import Test.QuickCheck
Emil Axelsson wrote:
[...]
The error comes from using QuickCheck 2, which happens to also use the
operator (). I can see two ways to solve the problem:
(1) Add 2 after QuickCheck in the Wired.cabal file.
(2) Add hiding (()) after import Test.QuickCheck in
Data/Hardware/Internal.hs
Emil,
The error comes from using QuickCheck 2, which happens to
also use the
operator (). I can see two ways to solve the problem:
(1) Add 2 after QuickCheck in the Wired.cabal file.
(2) Add hiding (()) after import Test.QuickCheck in
Data/Hardware/Internal.hs
Emil,
my
Stephan Friedrichs skrev:
Emil Axelsson wrote:
[...]
The error comes from using QuickCheck 2, which happens to also use the
operator (). I can see two ways to solve the problem:
(1) Add 2 after QuickCheck in the Wired.cabal file.
(2) Add hiding (()) after import Test.QuickCheck in
Hi,
what is the best action to take if a package from hackage fails to build? Is
there a recommended/established common way to deal with build
failures/runtime bugs etc.?
For example:
[EMAIL PROTECTED]:~/Links/Elite/ac cabal install wired
Resolving dependencies...
Downloading Wired-0.1.1...
