From owner-freebsd-sparc64@FreeBSD.ORG Mon Jan 26 11:41:05 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C78916A4CE for ; Mon, 26 Jan 2004 11:41:05 -0800 (PST) Received: from smtp.volant.org (gate.volant.org [207.111.218.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id A830E43D39 for ; Mon, 26 Jan 2004 11:41:02 -0800 (PST) (envelope-from patl+freebsd@volant.org) Received: from 64-144-229-193.client.dsl.net ([64.144.229.193] helo=[192.168.0.13]) by smtp.volant.org with asmtp (TLSv1:AES256-SHA:256) (Exim 4.22) id 1AlCay-0006Zt-4b; Mon, 26 Jan 2004 11:40:28 -0800 Date: Mon, 26 Jan 2004 11:40:26 -0800 From: Pat Lashley To: John LeMay , freebsd-sparc64@freebsd.org Message-ID: <4273990816.1075146026@mccaffrey.phoenix.volant.org> In-Reply-To: <40156661.4070708@njmc.com> References: <40156661.4070708@njmc.com> X-Mailer: Mulberry/3.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Scan-Signature: 0e97991d4d276b8697c19f6612959bfa973867fd X-Spam-Score: -4.5 (----) X-Spam-Score-Int: -45 X-Spam-Report: -4.5/5.0 This mail has matched the spam-filter tests listed below. See http://spamassassin.org/tag/ for details about the specific tests reported. In general, the higher the number of total points, the more likely that it actually is spam. (The 'required' number of points listed below is the arbitrary number above which the message is normally considered spam.) Content analysis details: (-4.50 points total, 5 required)header IN_REP_TO (-0.4 points) Has a In-Reply-To header probability is 1 to 10% [score: 0.0905]quoted email text REPLY_WITH_QUOTES (0.0 points) Reply with quoted text AWL (1.7 points) AWL: Auto-whitelist adjustment Subject: Re: Problem with compiling ports X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2004 19:41:05 -0000 --On Monday, January 26, 2004 14:11:29 -0500 John LeMay wrote: > Hi, list newbie here (freebsd newbie as well, but one with > several years experience with Linux, Solaris, and some AIX). > Just wondering what the process is for reporting an issue > when compiling something in the ports tree. Same as for anything else - send-pr(1). Sounds like you've got enough experience that the form should be self-explanitory. It's a good idea to check the FreeBSD.org website first to see if the problem has already been reported. And, depending on the problem, you may want to send a message to this group first, to help determine whether it is a real problem or pilot error. (Monitoring this group on an on-going basis is also a good idea for any FreeBSD sysadmin.) You didn't say whether you were using the ports tree from the release; or if you had CVSup'd it first. If you were using the release, check the Updating section of the Handbook on how to use CVSup to keep your ports tree up to date; then update the tree and try the build again. You may also want to install portupgrade and use that instead of direct makes. -Pat