From owner-freebsd-ports@FreeBSD.ORG Thu Feb 26 09:03:16 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 075A416A4CE for ; Thu, 26 Feb 2004 09:03:16 -0800 (PST) Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id B22AE43D2F for ; Thu, 26 Feb 2004 09:03:15 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com ([68.161.120.219]) by out005.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040226170315.UNYT2677.out005.verizon.net@mac.com>; Thu, 26 Feb 2004 11:03:15 -0600 Message-ID: <403E26CB.4070701@mac.com> Date: Thu, 26 Feb 2004 12:03:07 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Noah References: <20040226153007.M64716@enabled.com> <403E226A.3050202@mac.com> <20040226164721.M5540@enabled.com> In-Reply-To: <20040226164721.M5540@enabled.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [68.161.120.219] at Thu, 26 Feb 2004 11:03:14 -0600 cc: freebsd-ports@freebsd.org Subject: Re: python-2.3.3 build failing X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2004 17:03:16 -0000 Noah wrote: > On Thu, 26 Feb 2004 11:44:26 -0500, Chuck Swiger wrote >> For what it's worth, python-2.3.3 built just fine for me under 4.9. >> Is the problem reproducable, or maybe your hardware was flaky? > > Yeah I dont have a problem building it on other 4.9 machines either. > seems rather strange. > > what hardware should I check? what could be broken? > this happens everytime I build python on this machine. You should look at the config.log to see exactly what was going on when the segfault happened. Maybe you have something wrong with one of the GNU autoconf tools? Otherwise, try running sysutils/memtest for a day or so and see whether it provokes your hardware into crashing, in which case you should do the usual-- check cooling, swap memory and other components, etc... -- -Chuck