From owner-freebsd-questions@FreeBSD.ORG Thu Oct 6 12:13:20 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 78D4116A41F for ; Thu, 6 Oct 2005 12:13:20 +0000 (GMT) (envelope-from toomas.aas@raad.tartu.ee) Received: from lv.raad.tartu.ee (lv.raad.tartu.ee [194.126.106.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9929443D45 for ; Thu, 6 Oct 2005 12:13:18 +0000 (GMT) (envelope-from toomas.aas@raad.tartu.ee) Received: Message by Barricade lv.raad.tartu.ee with ESMTP id j96CD4nG007888; Thu, 6 Oct 2005 15:13:04 +0300 Received: from INFO/SpoolDir by raad.tartu.ee (Mercury 1.48); 6 Oct 05 15:13:05 +0300 Received: from SpoolDir by INFO (Mercury 1.48); 6 Oct 05 15:12:46 +0300 Received: from [192.168.1.2] (192.168.1.2) by raad.tartu.ee (Mercury 1.48) with ESMTP; 6 Oct 05 15:12:39 +0300 Message-ID: <434514B8.4070806@raad.tartu.ee> Date: Thu, 06 Oct 2005 15:12:40 +0300 From: Toomas Aas User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Reinhard Weismann References: <20051004101732.170bfcfc@jadzia.intern.creative.co.at> In-Reply-To: <20051004101732.170bfcfc@jadzia.intern.creative.co.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:13:20 -0000 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