slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: rearrange troubleshooting

Browse Source
This commit is contained in:
Simon Michael 2010-09-06 19:18:28 +00:00
parent 314ff84fc1
commit 4ef9d7b2a0
1 changed files with 29 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
MANUAL.markdown
View File

@ -1002,16 +1002,10 @@ sailing. Here are some known issues and things to try:
- **Do you have a new enough version of GHC ?** hledger supports GHC 6.10 - **Do you have a new enough version of GHC ?** hledger supports GHC 6.10
and 6.12. Building with the `-fweb` flag requires 6.12 or greater. and 6.12. Building with the `-fweb` flag requires 6.12 or greater.
- **Do you have a new enough version of cabal-install ?** - **An error while building non-hledger packages.**
Recent versions tend to be better at resolving dependencies. The error Resolve these problem packages one at a time. Eg, cabal install pkg1.
`setup: failed to parse output of 'ghc-pkg dump'` is another symptom of Look for the cause of the failure near the end of the output. If it's
this. To update, do: not apparent, try again with `-v2` or `-v3` for more verbose output.
$ cabal update
$ cabal install cabal-install
$ cabal clean
then try installing hledger again.
- **Could not run trhsx.** - **Could not run trhsx.**
You are installing with `-fweb610`, which needs to run the `trhsx` executable. You are installing with `-fweb610`, which needs to run the `trhsx` executable.
@ -1051,6 +1045,21 @@ sailing. Here are some known issues and things to try:
- **A ghc: panic! (the 'impossible' happened)** might be - **A ghc: panic! (the 'impossible' happened)** might be
[this issue](http://hackage.haskell.org/trac/ghc/ticket/3862) [this issue](http://hackage.haskell.org/trac/ghc/ticket/3862)
- **This package indirectly depends on multiple versions of the same package.**
You may have previously installed some of hledger's dependencies
depending on different versions of (eg) parsec. Then cabal install hledger gives
an error like this:
Warning: This package indirectly depends on multiple versions of the same
package. This is highly likely to cause a compile failure.
package yesod-0.5.0.3 requires parsec-2.1.0.1
package csv-0.1.1 requires parsec-3.1.0
...
The above example could be resolved by, eg:
$ cabal install yesod --reinstall --constraint 'parsec == 3.1.0"
- **Another error while building a hledger package.** - **Another error while building a hledger package.**
The current hledger release might have a coding error, or dependency The current hledger release might have a coding error, or dependency
error. You could try installing the error. You could try installing the
@ -1067,25 +1076,16 @@ sailing. Here are some known issues and things to try:
$ cd .. $ cd ..
$ cabal install [-f...] $ cabal install [-f...]
- **An error while building non-hledger packages.** - **Do you have a new enough version of cabal-install ?**
Resolve these problem packages one at a time. Eg, cabal install pkg1. Recent versions tend to be better at resolving dependencies. The error
Look for the cause of the failure near the end of the output. If it's `setup: failed to parse output of 'ghc-pkg dump'` is another symptom of
not apparent, try again with `-v2` or `-v3` for more verbose output. this. To update, do:
- **This package indirectly depends on multiple versions of the same package.** $ cabal update
You may have previously installed some of hledger's dependencies $ cabal install cabal-install
depending on different versions of (eg) parsec. Then cabal install hledger gives $ cabal clean
an error like this:
then try installing hledger again.
Warning: This package indirectly depends on multiple versions of the same
package. This is highly likely to cause a compile failure.
package yesod-0.5.0.3 requires parsec-2.1.0.1
package csv-0.1.1 requires parsec-3.1.0
...
The above example could be resolved by, eg:
$ cabal install yesod --reinstall --constraint 'parsec == 3.1.0"
- **cabal fails to resolve dependencies.** - **cabal fails to resolve dependencies.**
It's possible for cabal to get confused, eg if you have It's possible for cabal to get confused, eg if you have