From owner-freebsd-doc Sun Jan 14 2:30:20 2001 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4D66437B402 for ; Sun, 14 Jan 2001 02:30:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f0EAU1q39201; Sun, 14 Jan 2001 02:30:01 -0800 (PST) (envelope-from gnats) Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 64D0F37B698 for ; Sun, 14 Jan 2001 02:26:37 -0800 (PST) Received: from spike.unixfreak.org (spike [192.168.2.4]) by bazooka.unixfreak.org (Postfix) with ESMTP id F1C3B3E02 for ; Sun, 14 Jan 2001 02:26:36 -0800 (PST) Received: (from dima@localhost) by spike.unixfreak.org (8.11.1/8.11.1) id f0EAQaa63076; Sun, 14 Jan 2001 02:26:36 -0800 (PST) (envelope-from dima) Message-Id: <200101141026.f0EAQaa63076@spike.unixfreak.org> Date: Sun, 14 Jan 2001 02:26:36 -0800 (PST) From: dima@unixfreak.org Reply-To: dima@unixfreak.org To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/24322: [PATCH] New FAQ entry about kernel build failures Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >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 @@ + + + + Every kernel I try to build fails to compile; even + GENERIC. + + + + There are a number of possible causes for this problem. + They are, in no particular order: + + + + You are not using the new make + buildkernel and make + installkernel 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 + /usr/src/UPDATING file, paying + particular attention to the COMMON ITEMS + section at the end. + + + + You are using the new make + buildkernel and make + installkernel targets, but you failed to assert + the completion of the make buildworld + target. The make buildkernel target + relies on files generated by the make + buildworld target to complete its job + correctly. + + + + Even if you are trying to build FreeBSD-STABLE, 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 FreeBSD-STABLE 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. + + + + >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message