From owner-freebsd-questions@FreeBSD.ORG Thu Oct 6 12:43:41 2005 Return-Path: X-Original-To: questions@freebsd.org 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 ABC0816A420 for ; Thu, 6 Oct 2005 12:43:41 +0000 (GMT) (envelope-from reinhard.weismann@callooh.com) Received: from fw2.creative.co.at (fw2.creative.co.at [193.81.98.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD57243D45 for ; Thu, 6 Oct 2005 12:43:40 +0000 (GMT) (envelope-from reinhard.weismann@callooh.com) Received: from blaster3.intern.creative.co.at (blaster2.intern.creative.co.at [192.168.10.8]) by fw2.creative.co.at (8.13.4/8.13.4/Debian-3) with ESMTP id j96ChcJP025359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Oct 2005 14:43:38 +0200 Received: from jadzia.intern.creative.co.at (jadzia.intern.creative.co.at [192.168.10.23]) by blaster3.intern.creative.co.at (8.13.4/8.13.4/Debian-3) with ESMTP id j96ChLxf020454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Oct 2005 14:43:26 +0200 Received: from jadzia.intern.creative.co.at (localhost [127.0.0.1]) by jadzia.intern.creative.co.at (8.13.5/8.13.4) with ESMTP id j96ChGow095866; Thu, 6 Oct 2005 14:43:21 +0200 (CEST) (envelope-from reinhard.weismann@callooh.com) Date: Thu, 6 Oct 2005 14:43:16 +0200 From: Reinhard Weismann To: Toomas Aas Message-ID: <20051006144316.5d18009d@jadzia.intern.creative.co.at> In-Reply-To: <434514B8.4070806@raad.tartu.ee> References: <20051004101732.170bfcfc@jadzia.intern.creative.co.at> <434514B8.4070806@raad.tartu.ee> X-Mailer: Sylpheed-Claws 1.9.15 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1116/Thu Oct 6 11:34:58 2005 on blaster3.intern.creative.co.at X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,BAYES_50 autolearn=ham version=3.0.3 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on blaster3.intern.creative.co.at Cc: questions@freebsd.org Subject: Re: broken ports X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2005 12:43:41 -0000 Thank you very much for the info's in the meanwhile, the problem got solved, after upgrading p5-Mail-DomainKeys-0.23 to 0.80 yesterday, p5-Mail-SpamAssassin upgrade also worked. > The reason I'm asking is that segmentation faults are often caused by > failing hardware (faulty memory chip, overheating CPU etc). In your > case, hardware fault is even more likely since you noticed yourself > that the port builds successfully on another machine. i don't think so, this problem appeared on two of my machines, both installed with 5.4, but not on another machine with 5.3 regards, reinhard On Thu, 06 Oct 2005 15:12:40 +0300 Toomas Aas wrote: > Reinhard Weismann wrote: > > > does anybody know where to report broken ports, or, where to get > > information if/why a port currently is broken. > > From your description I am not at all sure that the port is broken > in this case. But since you asked... > > If you are sure that the port really is broken, you should first see > whether somebody has already noted this, by going to > http://www.freebsd.org/support/bugreports.html and searching for > existing reports on a particular port. You can also look at the > archive of freebsd-ports mailing list by going to > http://www.freebsd.org/search/search.html#mailinglists > > FreeBSD has a large and active user community, so real port breakage > is usually found very fast and by the time you notice it, it's very > likely that the problem has already been found and even fixed. > Cvsupping your ports tree and trying to build the port again is often > a quick fix to port build problems. > > If you dont see any existing reports on your problem AND YOU ARE > STILL SURE THAT IT IS ACTUALLY A PROBLEM WITH THE PORT then it's time > to submit a bug report at > http://www.freebsd.org/support/bugreports.html > > > in this case on my 5.4-RELEASE-p6 (i386) installations, the port > > mail/p5-Mail-SpamAssassin (p5-Mail-SpamAssassin-3.1.0) does not > > compile, i.e. i get > > [..] > > Segmentation fault (core dumped) > > *** Error code 139 > > [..] > > Does this happen only to this port? Can you build other ports > successfully? Can you successfully run 'make buildworld'? > > The reason I'm asking is that segmentation faults are often caused by > failing hardware (faulty memory chip, overheating CPU etc). In your > case, hardware fault is even more likely since you noticed yourself > that the port builds successfully on another machine. > > -- > Toomas Aas -- If you give Congress a chance to vote on both sides of an issue, it will always do it. -- Les Aspin, D., Wisconsin