diff options
author | Chris Lattner <sabre@nondot.org> | 2007-02-14 07:40:16 +0000 |
---|---|---|
committer | Chris Lattner <sabre@nondot.org> | 2007-02-14 07:40:16 +0000 |
commit | 31d041935ec93742d827b617a65dbb5154752434 (patch) | |
tree | 8942d5c3b015bf4c9a649ead958f0bf00f9243ae /docs/FAQ.html | |
parent | e5ff00870a67a03d53973166782542c0c7e057c2 (diff) | |
download | external_llvm-31d041935ec93742d827b617a65dbb5154752434.zip external_llvm-31d041935ec93742d827b617a65dbb5154752434.tar.gz external_llvm-31d041935ec93742d827b617a65dbb5154752434.tar.bz2 |
remove an obsolete question
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34274 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/FAQ.html')
-rw-r--r-- | docs/FAQ.html | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/docs/FAQ.html b/docs/FAQ.html index d540edd..b67fae3 100644 --- a/docs/FAQ.html +++ b/docs/FAQ.html @@ -36,7 +36,6 @@ <li><a href="#build">Build Problems</a> <ol> <li>When I run configure, it finds the wrong C compiler.</li> - <li>I compile the code, and I get some error about <tt>/localhome</tt>.</li> <li>The <tt>configure</tt> script finds the right C compiler, but it uses the LLVM linker from a previous build. What do I do?</li> <li>When creating a dynamic library, I get a strange GLIBC error.</li> @@ -216,22 +215,6 @@ explicitly.</p> </div> <div class="question"> -<p>I compile the code, and I get some error about <tt>/localhome</tt>.</p> -</div> - -<div class="answer"> - -<p>There are several possible causes for this. The first is that you didn't set -a pathname properly when using <tt>configure</tt>, and it defaulted to a -pathname that we use on our research machines.</p> - -<p>Another possibility is that we hardcoded a path in our Makefiles. If you see -this, please email the LLVM bug mailing list with the name of the offending -Makefile and a description of what is wrong with it.</p> - -</div> - -<div class="question"> <p>The <tt>configure</tt> script finds the right C compiler, but it uses the LLVM linker from a previous build. What do I do?</p> </div> |