Added another FAQ item to README-1ST
This commit is contained in:
parent
2149a8e773
commit
435677eea4
1 changed files with 21 additions and 7 deletions
28
README-1ST
28
README-1ST
|
|
@ -1,37 +1,49 @@
|
||||||
|
|
||||||
|
|
||||||
README FIRST!!!
|
README FIRST!!!
|
||||||
|
|
||||||
|
===============================================================================
|
||||||
|
|
||||||
To build this code after doing a Git clone, run:
|
To build this code after doing a Git clone, run:
|
||||||
|
|
||||||
$ acprep update
|
$ ./acprep update
|
||||||
|
|
||||||
If you try to configure/build on your own, you are almost certainly going to
|
If you try to configure/build on your own, you are almost certainly going to
|
||||||
run into problems.
|
run into problems. In future, you can run this command again and it will keep
|
||||||
|
you updated with the very latest version.
|
||||||
|
|
||||||
|
===============================================================================
|
||||||
|
|
||||||
F.A.Q.
|
F.A.Q.
|
||||||
|
|
||||||
|
----------------------------------------------------------------------
|
||||||
|
|
||||||
- Q: The build fails saying it can't find utf8.h
|
- Q: The build fails saying it can't find utf8.h
|
||||||
|
|
||||||
A: You didn't run acprep update.
|
A: You didn't run ./acprep update.
|
||||||
|
|
||||||
|
----------------------------------------------------------------------
|
||||||
|
|
||||||
- Q: The build fails saying it can't find boost_regex
|
- Q: Configure fails saying it can't find boost_regex
|
||||||
|
|
||||||
A: Look in config.log and search for "boost_regex", then scroll down a bit
|
A: Look in config.log and search for "boost_regex", then scroll down a bit
|
||||||
until you see the exact compile error. Usually it's failing because
|
until you see the exact compile error. Usually it's failing because
|
||||||
your include directory is different from anything acprep is expecting to
|
your include directory is different from anything acprep is expecting to
|
||||||
see. It could also be failing because your Boost library have a custom
|
see. It could also be failing because your Boost libraries have a
|
||||||
"suffix" on them.
|
custom "suffix" on them.
|
||||||
|
|
||||||
Let's say your Boost was installed in ~/boost, and every library has the
|
Let's say your Boost was installed in ~/boost, and every library has the
|
||||||
suffix '-xgcc42'. This is what you would run:
|
suffix '-xgcc42'. This is what you would run:
|
||||||
|
|
||||||
CPPFLAGS=-I$HOME/boost acprep --boost=xgcc42 update
|
CPPFLAGS=-I$HOME/boost acprep --boost=xgcc42 update
|
||||||
|
|
||||||
|
----------------------------------------------------------------------
|
||||||
|
|
||||||
|
- Q: Configure fails saying it can't find MPFR
|
||||||
|
|
||||||
|
A: You need MPFR version 2.4.0 or higher. This version does not come with
|
||||||
|
most Debian distributions, so you will need to build it.
|
||||||
|
|
||||||
|
----------------------------------------------------------------------
|
||||||
|
|
||||||
- Q: Something else fails, or Ledger crashes on startup
|
- Q: Something else fails, or Ledger crashes on startup
|
||||||
|
|
||||||
|
|
@ -45,3 +57,5 @@ run into problems.
|
||||||
(gdb) bt
|
(gdb) bt
|
||||||
|
|
||||||
Send me that backtrace output, and the output from "ledger --version".
|
Send me that backtrace output, and the output from "ledger --version".
|
||||||
|
|
||||||
|
----------------------------------------------------------------------
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue