Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to compile #24

Open
obcan opened this issue Sep 26, 2015 · 2 comments
Open

Failed to compile #24

obcan opened this issue Sep 26, 2015 · 2 comments

Comments

@obcan
Copy link

obcan commented Sep 26, 2015

$cabal install ./react-haskell
Resolving dependencies...
Configuring react-haskell-2.0.1...
Building react-haskell-2.0.1...
Failed to install react-haskell-2.0.1
Build log ( /home/mule/.cabal/logs/react-haskell-2.0.1.log ):
Configuring react-haskell-2.0.1...
Building react-haskell-2.0.1...
Preprocessing library react-haskell-2.0.1...
[14 of 15] Compiling React.Events ( src/React/Events.hs, dist/build/React/Events.o )

src/React/Events.hs:197:31:
No instance for (Eq JSString) arising from the literal ‘"Enter"’
In the pattern: "Enter"
In the pattern: KeyboardEvent {key = "Enter"}
In an equation for ‘handler’:
handler (KeyboardEvent {key = "Enter"}) = Just s
cabal: Error: some packages failed to install:
react-haskell-2.0.1 failed during the building phase. The exception was:
ExitFailure 1

Ghc version:
7.10.2

Cabal version:
1.22.6.0

Installed versions of packeges which react-haskell depends:

  • base 4.8.1.0
  • transformers 0.4.2.0
  • monads-tf 0.1.0.2
  • deepseq 1.4.1.1
  • lens-family 1.2.0
  • void 0.7, 0.7.1
  • aeson 0.9.0.1, 0.10.0.0
  • text 1.2.0.3
  • unordered-containers 0.2.5.1

Maybe this is the report from Cabal hell? I am trying different versions and the result is the same.

@emmanueltouzery
Copy link

I also had a problem building with no instance of eq jsstring a while back, then gave up.

@johncant
Copy link

I did some hacking on this repo nearly a year ago and this error rings a bell. There's a good chance you'll need to just fix it yourself. Fortunately you're barely even in the first circle of cabal hell, because there's only one package left to install, and it's (only slightly) broken rather than the dependency structure. Good luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants