ghc-pkg检查黑线鳕警告

Question

在重新安装haskell-platform (通过homebrew) (GHC x64 7.6.3)在OSX 10.9.2上时，我在运行ghc-pkg check时会收到以下警告(见下文)

Warning: haddock-interfaces: /Users/user/.cabal/share/doc/x86_64-osx-ghc-7.6.3/ghc-mod-3.1.7/html/ghc-mod.haddock doesn't exist or isn't a file
Warning: haddock-html: /Users/user/.cabal/share/doc/x86_64-osx-ghc-7.6.3/ghc-mod-3.1.7/html doesn't exist or isn't a directory
Warning: haddock-interfaces: /Users/user/.cabal/share/doc/x86_64-osx-ghc-7.6.3/hlint-1.8.59/html/hlint.haddock doesn't exist or isn't a file
Warning: haddock-html: /Users/user/.cabal/share/doc/x86_64-osx-ghc-7.6.3/hlint-1.8.59/html doesn't exist or isn't a directory
Warning: haddock-html: /usr/local/Cellar/haskell-platform/2013.2.0.0/share/doc/mtl-2.1.2/html doesn't exist or isn't a directory
Warning: haddock-interfaces: /usr/local/Cellar/haskell-platform/2013.2.0.0/share/doc/transformers-0.3.0.0/html/transformers.haddock doesn't exist or isn't a file
Warning: haddock-html: /usr/local/Cellar/haskell-platform/2013.2.0.0/share/doc/transformers-0.3.0.0/html doesn't exist or isn't a directory
Warning: haddock-interfaces: /usr/local/Cellar/haskell-platform/2013.2.0.0/share/doc/case-insensitive-1.0.0.1/html/case-insensitive.haddock doesn't exist or isn't a file
Warning: haddock-html: /usr/local/Cellar/haskell-platform/2013.2.0.0/share/doc/case-insensitive-1.0.0.1/html doesn't exist or isn't a directory

根据医生：

ghc-pkg check
    Check the consistency of package depenencies and list broken packages.
    Accepts the --simple-output flag.

我试图运行以下命令来生成黑线鳕文档，但没有效果：

sudo cabal install --reinstall --force-reinstalls --enable-documentation

该命令来自haskell邮件列表中的一个类似的问题。http://www.haskell.org/pipermail/glasgow-haskell-users/2012-February/021780.html

如何安抚ghc-pkg check并删除这些警告？

警告：当我说“新安装”时，我的意思是我已经从零开始安装了Haskell平台，并安装了全局cabal-1.18.0.3，并在我的路径中添加了阴谋集团的bin目录。

Answer 1

那些黑线鳕的警告很烦人，但它们不会引起任何问题，AFAIK。我认为警告是在卡巴勒1.18修正的。我再也见不到他们了。

编辑:好的，所以我们需要遵循科斯米库斯的建议.

mv ~/.cabal ~/.cabal.SAVE
cabal update

这将创建文件~/..cabal/config。如果愿意，可以编辑此文件。

现在试着构建一些东西，看看问题是否已经解决。