From owner-freebsd-questions Sat Dec 7 5:39:16 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6836F37B401 for ; Sat, 7 Dec 2002 05:39:15 -0800 (PST) Received: from otter.mills-atl.com (dsl-64-192-140-77.telocity.com [64.192.140.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB8FE43EA9 for ; Sat, 7 Dec 2002 05:39:14 -0800 (PST) (envelope-from jmmills@telocity.com) Received: from localhost (jmills@localhost) by otter.mills-atl.com (8.9.3/8.9.3) with ESMTP id IAA02273; Sat, 7 Dec 2002 08:40:07 -0500 X-Authentication-Warning: otter.mills-atl.com: jmills owned process doing -bs Date: Sat, 7 Dec 2002 08:40:07 -0500 (EST) From: John Mills X-Sender: jmills@otter.mills-atl.com Reply-To: John Mills To: Kent Stewart Cc: freebsd-questions Subject: Re: buildworld fail In-Reply-To: <200212061411.26848.kstewart@owt.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kent, all - On Fri, 6 Dec 2002, Kent Stewart wrote: > Just remember that a signal 11 in a compile is usually your hardware > telling you something is wrong. If it dies at the same spot, it can > be options or whatever. If you use strange options, you have to try > them first but still remember a signal 11is normally related to > memory or heating problems. Yes, but when several users with different systems in different parts of the world report the same message in the same spot, I rather suspect a configuration or tool issue. For example, tripling the RAM didn't change it. I may well have a bad set of configuration options for these newer releases. I am very new to FreeBSD. I followed the Handbook configuration instructions to reflect my hardware and didn't knowingly set compiler options at all. Your note was the first to remark on compiler options in connection with this error message so it certainly warrants my attention. I build RELENG_4_5 seamlessly with the same configuration file (in a RELENG_4_5 installation, however), so an environmental or generational issue is likely here. I _have_ also hit heating problems and swap overruns, but these showed different 'footprints'. The partition size issue is my real stimulus to reconfigure the setup before I am more invested and dependent on it: "A house built on sand ..." etc. Thanks for your comments. I need to dig out my error messages and compare the compilation options with the other poster's. Regards. - John Mills To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message