From owner-freebsd-questions Thu Nov 19 09:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24463 for freebsd-questions-outgoing; Thu, 19 Nov 1998 09:30:30 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24454 for ; Thu, 19 Nov 1998 09:30:26 -0800 (PST) (envelope-from stormy@futuresouth.com) Received: (from stormy@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id LAA06454; Thu, 19 Nov 1998 11:29:49 -0600 (CST) Message-ID: <19981119112949.37554@futuresouth.com> Date: Thu, 19 Nov 1998 11:29:49 -0600 From: Stormy Henderson To: freebsd-questions@FreeBSD.ORG Subject: Re: GCC Signal 11 fixed! References: <19981118141420.04580@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Doug White on Thu, Nov 19, 1998 at 09:23:39AM -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Installing the 11/18 3.0-SNAP fixed the GCC problems. Now I just need to get SMP to quit panicking the kernel at bootup when calling boot() on cpu #0. (c: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message