From owner-freebsd-questions Wed Nov 18 15:37:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00323 for freebsd-questions-outgoing; Wed, 18 Nov 1998 15:37:20 -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 PAA00317 for ; Wed, 18 Nov 1998 15:37:16 -0800 (PST) (envelope-from stormy@futuresouth.com) Received: (from stormy@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id RAA22919; Wed, 18 Nov 1998 17:36:46 -0600 (CST) Message-ID: <19981118173646.51238@futuresouth.com> Date: Wed, 18 Nov 1998 17:36:46 -0600 From: Stormy Henderson To: freebsd-questions@FreeBSD.ORG Subject: GCC Signal 11 update (it isn't hardware) References: <19981118141420.04580@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19981118141420.04580@futuresouth.com>; from Stormy Henderson on Wed, Nov 18, 1998 at 02:14:20PM -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some new information...I mounted my old 2.2.7 hard drive, chrooted to it, and tried compiling, and it worked fine. So the problem is definitely software. Both releases are using GCC 2.7.2.1. Perhaps this info will be useful to someone in guessing the cause of the problem. -- Stormy Henderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message