Note that there are some explanatory texts on larger screens.

plurals
  1. POUnable to install yesod-bin
    primarykey
    data
    text
    <p>I'm updating my yesod framework to the latest yesod 1.2 version. I've installed yesod-platform (painfully....had to manually delete old dependency....cabal hell), now I need to install yesod-bin and it should be done. However, after <code>sudo cabal install yesod-bin</code> I'm getting the following error.</p> <pre><code>Building yesod-bin-1.2.0... Preprocessing executable 'yesod-ld-wrapper' for yesod-bin-1.2.0... [1 of 1] Compiling Main ( ghcwrapper.hs, dist/build/yesod-ld-wrapper/yesod-ld-wrapper-tmp/Main.o ) Linking dist/build/yesod-ld-wrapper/yesod-ld-wrapper ... /usr/bin/ld: cannot find -lHStar-0.4.0.1 /usr/bin/ld: cannot find -lHSoptparse-applicative-0.5.2.1 /usr/bin/ld: cannot find -lHSghc-paths-0.1.0.9 /usr/bin/ld: cannot find -lHSfsnotify-0.0.6 /usr/bin/ld: cannot find -lHShinotify-0.3.5 collect2: ld returned 1 exit status Failed to install yesod-bin-1.2.0 cabal: Error: some packages failed to install: yesod-bin-1.2.0 failed during the building phase. The exception was: ExitFailure 1 </code></pre> <p>According to <a href="http://hackage.haskell.org/trac/ghc/ticket/3794" rel="nofollow">this</a>, I feel it may have something to do with privileges I'm not sure. </p> <p>EDIT: So I only found the following two libraries.</p> <pre><code>/usr/lib/haskell-packages/ghc/lib/tar-0.3.2.0/ghc-7.4.1/libHStar-0.3.2.0.a /usr/lib/haskell-packages/ghc/lib/ghc-paths-0.1.0.8/ghc-7.4.1/libHSghc-paths-0.1.0.8.a </code></pre> <p>I'm trying to update <code>libghc-tar-dev</code> to the newest version 0.4.0.1. However, 0.3.2.0 is the newest version on <code>apt-get</code> what are my options?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload