Problems Compiling

• The configuration information may be incorrect.
  • If configure is run after it has previously been run, it may use information that was gathered during its previous invocation.
    • This information is stored in config.cache.
    • When configure starts up, it looks for config.cache and reads its contents if it exists.
    • It assumes the information is still correct.
    • That assumption is invalid when reconfigure occurs.
  • To prevent old configuration information or object files from being used, run these commands before re-running configure:

    rm config.cache
    

    make clean

• If virtual memory is exhausted because compiling MySQL requires a lot of memory, then try:

  ./configure --with-low-memory

What are the post-installation procedures?

---

---

© 2007 John Michael Pierobon

Notes