summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorrillig <rillig>2006-07-02 23:34:03 +0000
committerrillig <rillig>2006-07-02 23:34:03 +0000
commit9e0a574d1fe488b5c9bfc6cfa3e87ef9fd560278 (patch)
tree593f846c3da375c07b70558099a99f7b98241a50
parentbf482b7c274fbb870a3cbe99d521c3cca2ddb07c (diff)
downloadpkgsrc-9e0a574d1fe488b5c9bfc6cfa3e87ef9fd560278.tar.gz
Added "A package does not build. What shall I do?" to the FAQ.
-rw-r--r--doc/guide/files/faq.xml29
1 files changed, 28 insertions, 1 deletions
diff --git a/doc/guide/files/faq.xml b/doc/guide/files/faq.xml
index bdc49acaa63..c376a2b31c2 100644
--- a/doc/guide/files/faq.xml
+++ b/doc/guide/files/faq.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: faq.xml,v 1.26 2006/07/02 12:42:07 rillig Exp $ -->
+<!-- $NetBSD: faq.xml,v 1.27 2006/07/02 23:34:03 rillig Exp $ -->
<chapter id="faq"> <?dbhtml filename="faq.html"?>
<title>Frequently Asked Questions</title>
@@ -581,4 +581,31 @@ a security check before building any package. See
</sect1>
+<sect1 id="ufaq-fail">
+<title>A package does not build. What shall I do?</title>
+
+ <procedure>
+
+ <step><para>Make sure that your copy of pkgsrc is consistent. A
+ case that occurs often is that people only update pkgsrc in
+ parts, because of performance reasons. Since pkgsrc is one large
+ system, not a collection of many small systems, there are
+ sometimes changes that only work when the whole pkgsrc tree is
+ updated.</para></step>
+
+ <step><para>Make sure that you don't have any CVS conflicts.
+ Search for <quote>&lt;&lt;&lt;&lt;&lt;&lt;</quote> or
+ <quote>&gt;&gt;&gt;&gt;&gt;&gt;</quote> in all your pkgsrc
+ files.</para></step>
+
+ <step><para>Make sure that you don't have old copies of the packages
+ extracted. Run <command>make clean clean-depends</command> to
+ verify this.</para></step>
+
+ <step><para>If the problem still exists, write a mail to the
+ <literal>pkgsrc-users</literal> mailing list.</para></step>
+
+ </procedure>
+
+</sect1>
</chapter>