-
Notifications
You must be signed in to change notification settings - Fork 691
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
cabal is not reading or respecting ~/.cabal/config #760
Comments
(Imported comment by @dcoutts on 2010-11-27) This is quite peculiar. I assume it is something odd in your particular setup or situation, since cabal definitely does read its config file (or very little would work for anyone). Double check a few things:
|
I'm having the same problem. I've made the following change my ~/.cabal/config: 22c22 < -- library-profiling: False
But still, when I try to install a package, it won't build profiling libraries or documentation: marcot@ioiozinho:Mon Jul 30 10:15:40:~$ cabal install --reinstall iconv Codec/Text/IConv/Internal.hs:46:1: I need to pass the command line arguments to make it work: marcot@ioiozinho:Mon Jul 30 10:15:46:~$ cabal install --enable-documentation --enable-library-profiling --reinstall iconv Codec/Text/IConv/Internal.hs:46:1: Codec/Text/IConv/Internal.hs:46:1: dist/build/tmp23353/Codec/Text/IConv/Internal.hs:46:1: The file is being read, as can be checked by strace: marcot@ioiozinho:Mon Jul 30 10:17:39: |
Am I correct that the relevant lines in your |
Closing this issue, which appears to be user error. |
(Imported from Trac #770, reported by guest on 2010-11-27)
I changed my ~/.cabal/config file to keep global packages under /usr/local/lib/haskell and /usr/local/share/haskell to avoid cluttering the main /usr/local/lib and /usr/local/share/doc directories. ghc-pkg finds them just fine, and ghc-pkg recache works as expected. However, when I do 'cabal install whatever --global' it still throws everything into the old default directories, and more distressingly it isn't updating the access timestamp on ~/.cabal/config (as revealed by ls -u.)
cabal --version reports 0.8.2 using library 1.8.0.6, nothing else unusual about my setup.
The text was updated successfully, but these errors were encountered: