Date: Sun, 14 Jan 2001 02:26:36 -0800 (PST) From: dima@unixfreak.org To: FreeBSD-gnats-submit@freebsd.org Subject: docs/24322: [PATCH] New FAQ entry about kernel build failures Message-ID: <200101141026.f0EAQaa63076@spike.unixfreak.org>
index | next in thread | raw e-mail
>Number: 24322
>Category: docs
>Synopsis: [PATCH] New FAQ entry about kernel build failures
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Sun Jan 14 02:30:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Dima Dorfman
>Release: FreeBSD 5.0-20010101-CURRENT i386
>Organization:
Private
>Environment:
System: FreeBSD spike.unixfreak.org 5.0-20010101-CURRENT FreeBSD 5.0-20010101-CURRENT #6: Tue Jan 2 03:14:04 PST 2001 dima@spike.unixfreak.org:/usr/home/dima/w/f/src/sys/compile/SPIKE i386
>Description:
It's enough that the kernel build process isn't fool-proof (not that I
think it necessarily should be; it's easy enough, and at some point
one must stop trying to take care of those afraid of a little
thinking), but many users get even more frustrated when the build of
the GENERIC kernel fails. This entry attempts to explain some of the
common causes for GENERIC failing to build. It was inspired by the
occasional bursts of complains about GENERIC failing to build
following changes to gcc or other build tools.
>How-To-Repeat:
Read freebsd-(questions|stable) for a while. Look for threads about
kernels failing to build even though the originator "tried everything"
(except for buildworld before buildkernel, that is!)
>Fix:
Apply the following patch to doc/en_US.ISO_8859-1/books/faq/book.sgml.
Index: book.sgml
===================================================================
RCS file: /st/src/FreeBSD/doc/en_US.ISO_8859-1/books/faq/book.sgml,v
retrieving revision 1.137
diff -u -r1.137 book.sgml
--- book.sgml 2001/01/11 00:16:46 1.137
+++ book.sgml 2001/01/14 03:26:06
@@ -4833,6 +4833,56 @@
</answer>
</qandaentry>
+
+ <qandaentry>
+ <question id="generic-kernel-build-failure">
+ <para>Every kernel I try to build fails to compile; even
+ GENERIC.</para>
+ </question>
+
+ <answer>
+ <para>There are a number of possible causes for this problem.
+ They are, in no particular order:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>You are not using the new <command>make
+ buildkernel</command> and <command>make
+ installkernel</command> targets, and your source tree is
+ different from the one used to build the currently running
+ system (e.g., you're compiling 4.2-RELEASE on a 4.0-RELEASE
+ system). If you're attempting an upgrade, please read the
+ <filename>/usr/src/UPDATING</filename> file, paying
+ particular attention to the <quote>COMMON ITEMS</quote>
+ section at the end.</para>
+ </listitem>
+
+ <listitem>
+ <para>You are using the new <command>make
+ buildkernel</command> and <command>make
+ installkernel</command> targets, but you failed to assert
+ the completion of the <command>make buildworld</command>
+ target. The <command>make buildkernel</command> target
+ relies on files generated by the <command>make
+ buildworld</command> target to complete its job
+ correctly.</para>
+ </listitem>
+
+ <listitem>
+ <para>Even if you are trying to build <link
+ linkend="stable">FreeBSD-STABLE</link>, it is possible that
+ you fetched the source tree at a time when it was either
+ being modified, or broken for other reasons; only releases
+ are absolutly guaranteed to be buildable, although <link
+ linkend="stable">FreeBSD-STABLE</link> builds fine the
+ majority of the time. If you have not already done so, try
+ re-fetching the source tree and see if the problem goes
+ away. Try using a different server in case the one you're
+ using is having problems.</para>
+ </listitem>
+ </itemizedlist>
+ </answer>
+ </qandaentry>
</qandaset>
</chapter>
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101141026.f0EAQaa63076>