From owner-freebsd-questions@FreeBSD.ORG Wed May 4 02:18:36 2005 Return-Path: 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 287D516A4CE for ; Wed, 4 May 2005 02:18:36 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0454443D62 for ; Wed, 4 May 2005 02:18:36 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin01-en2 [10.13.10.146]) id j442IYu9007306; Tue, 3 May 2005 19:18:34 -0700 (PDT) Received: from [192.168.1.6] (pool-68-161-53-96.ny325.east.verizon.net [68.161.53.96]) (authenticated bits=0)j442IWVD017484; Tue, 3 May 2005 19:18:34 -0700 (PDT) In-Reply-To: <11cc9565287c535926609e4364673849@cox-internet.com> References: <11cc9565287c535926609e4364673849@cox-internet.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <80ef6c10844212e134edc18b3dc06f05@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Tue, 3 May 2005 22:18:32 -0400 To: "Christopher M.Hobbs" X-Mailer: Apple Mail (2.622) cc: freebsd-questions@freebsd.org Subject: Re: gcc issue in 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 02:18:36 -0000 On May 3, 2005, at 10:09 PM, Christopher M.Hobbs wrote: > I'm running a fresh install of 5.3-RELEASE. Every time I attempt to > install anything from the ports tree, gcc fails. Nine times out of > ten it states that there has been an internal error, and that I should > submit a bug report. Try building the port again; if it fails in a different place and you're seeing signal 11's (SIGSEGV), it's almost certainly hardware problems like poor cooling or bad memory, not a bug with GCC. Try running memtest.org's checker overnight and see whether that shows any problems. Otherwise, please provide more information including *which* port, and the exact error messages (give about 10 lines of context)... -- -Chuck