cabal-install

Cabal cannot find locally sourced (yet correctly installed) packages

╄→гoц情女王★ 提交于 2020-07-15 03:50:31
问题 I recently upgraded to Cabal 3.2 (and GHC 8.10) and I am running into some major issues that make some of my project non-buildable anymore... Thorough description of the problem Here is a minimal (not) working configuration that fails every time: I start off with a clean Cabal configuration (by deleting ~/.cabal ); the reason for that will appear later in the post. I run cabal update to recreate the .cabal directory and to ensure Cabal is working. I create a project (let's call it test1 )

cabal-install-0.10.2 failed during the building phase

╄→гoц情女王★ 提交于 2020-01-14 05:55:28
问题 I was trying to install haskeline, it's my first time installing using cabal, and here is what I got. What should I do? . sudo cabal install haskeline Password: Config file /Users/arie/.cabal/config not found. Writing default configuration to /Users/arie/.cabal/config Warning: The package list for 'hackage.haskell.org' does not exist. Run 'cabal update' to download it. cabal: There is no package named haskeline . sudo cabal update Downloading the latest package list from hackage.haskell.org

Cabal fails updating of cabal-install

假装没事ソ 提交于 2020-01-13 05:19:07
问题 Every time I install a library, cabal tells me to install a new version of cabal-install. Despite the fact that i run (with apparent success) the procedure that list below, the version of cabal-install remains unchanged. Where I am going wrong? (My OS is Window 7 64-bits) My User PATH is C:\Users\Alberto\AppData\Roaming\cabal\bin System variables: CABAL_DIR = C:\Users\Alberto\AppData\Roaming\cabal BEFORE the update C:\Users\Alberto>cabal -V cabal-install version 1.16.0.2 using version 1.16.0

Cabal getting installed in root directory instead of /home/vagrant directory using Vagrantfile

扶醉桌前 提交于 2020-01-04 05:23:07
问题 THe below is the content of the vagrant file. When I run vagrant up command, it installs cabal as required but it is in the root directory. Hence, it becomes unusable. I want to update the cabal version to latest version using cabal update . But it is not happening. Finally, in my VM, I have old version of cabal which comes with haskell-platform which is of no use to me. However, when I execute these commands separately by explicitly logging into VM, and not putting anything in Vagrantfile,

Stack gives 'dyld: malformed mach-o'

佐手、 提交于 2019-12-23 13:07:19
问题 When I attempt to run stack, for example even just stack --version , I get dyld: malformed mach-o: load commands size (38712) > 32768 What can I do to fix this. This started appearing after some recent updates to Homebrew. 回答1: I'm guessing you've upgraded to macOS Sierra, because that message looks like you're hitting a new limit in its dynamic linker. Might be that your stack executable is dynamically linked with all the Haskell libraries it uses, which is known to exceed the new limit. You