Gabriela Gibson wrote on Thu, Jan 10, 2013 at 00:15:29 +0000: > I thought that the solutions to this question might be useful to have in > the faq.html.
> +<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> It would be useful to quote the error message. Is this section applicable to tarball builds (which don't use autogen.sh) too? How does this compare to the HACKING (docs/community-guide/) section containing Karl's "voice of experience" email? Should they crossreference each other? > +<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> It would be useful to explain why this happens or what needs to be run when. IIRC the permutations are: if Makefile.in changed, re-run configure to regenerate Makefile; if configure.ac or build/ac-macros/ changed, rerun autogen.sh to regenerate configure (then run configure); if build.conf or build/gen-make/ changed, run ./gen-make.py (which is normally invoked by autogen.sh) to regenerate build-outputs.mk. > +</div> > + > + > <div class="h2" id="references"> > <h2>References: > <a class="sectionlink" href="#references"
