aboutsummaryrefslogtreecommitdiff
path: root/docs/FAQ.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/FAQ.html')
-rw-r--r--docs/FAQ.html17
1 files changed, 0 insertions, 17 deletions
diff --git a/docs/FAQ.html b/docs/FAQ.html
index d540edd81b..b67fae3abe 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>