I thought that the solutions to this question might be useful to have in
the faq.html.
Index: publish/faq.html
===================================================================
--- publish/faq.html (revision 1431153)
+++ publish/faq.html (working copy)
@@ -282,6 +282,8 @@ validating server certificate</tt> error even thou
<li><a href="#avoiding-compiler-inlining">How do I run a debugger on
Subversion binaries without compiler inlining obfuscating the
source?</a></li>
+<li><a href="#unexplainable-compile-errors">How do I deal with compile errors in
+ source tree which I can't explain by code changes?</a></li>
</ul>
<h4>References:</h4>
@@ -4374,6 +4376,24 @@ installing Subversion from source, by re-running <
</div>
+<div class="h3" id="unexplainable-compile-errors">
+<h3>How do I deal with compile errors in a source tree which I can't
+explain by code changes?
+ <a class="sectionlink" href="#unexplainable-compile-errors"
+ title="Link to this section">¶</a>
+</h3>
+
+<p>There are a couple of frequent causes of this kind of problem:</p>
+
+<p>1. You could be linking about your own installed libraries.</p>
+<p>Workaround 1: Remove them.</p>
+<p>Workaround 2: <code>"./configure --prefix=/usr/vladivostock ## Doesn't exist"</code></p>
+
+<p>2. You may have run <code>"svn up"</code> so that your build system is now stale:</p>
+<p>Rerun <code>"./autogen.sh; make"</code> or <code>"./autogen.sh; ./configure; make"</code>.</p>
+</div>
+
+
<div class="h2" id="references">
<h2>References:
<a class="sectionlink" href="#references"
[[[
Add advice to developer questions category on how to deal with compile errors
which are not explained by code changes.
* publish/faq.html:
(table-of-contents): List question and add reference link to answer to
developer question section.
(developer-questions): Add matching answer referred to in table-of-contents.
Patch by: Gabriela Gibson <gabriela.gibson{_AT_}gmail.com>
]]]
