From owner-freebsd-sparc64@FreeBSD.ORG Mon Jan 26 22:55:48 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 11B3A16A4CE for ; Mon, 26 Jan 2004 22:55:48 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-67-119-53-122.dsl.lsan03.pacbell.net [67.119.53.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D3B843D2D for ; Mon, 26 Jan 2004 22:55:31 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 29F4566C78; Mon, 26 Jan 2004 22:55:09 -0800 (PST) Date: Mon, 26 Jan 2004 22:55:09 -0800 From: Kris Kennaway To: Pat Lashley Message-ID: <20040127065508.GA55455@xor.obsecurity.org> References: <40156661.4070708@njmc.com> <4273990816.1075146026@mccaffrey.phoenix.volant.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <4273990816.1075146026@mccaffrey.phoenix.volant.org> User-Agent: Mutt/1.4.1i cc: freebsd-sparc64@freebsd.org 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: Tue, 27 Jan 2004 06:55:48 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 26, 2004 at 11:40:26AM -0800, Pat Lashley wrote: > --On Monday, January 26, 2004 14:11:29 -0500 John LeMay = =20 > wrote: >=20 > >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. >=20 > Same as for anything else - send-pr(1). Sounds like you've > got enough experience that the form should be self-explanitory. >=20 > 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.) Also check http://bento.freebsd.org for errors discovered during the automated package builds. Kris --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAFgtMWry0BWjoQKURAvp2AJ9kniWhXYhZXXXEqdceanU4gKypdwCgozgE 7e3oNd1zC8AvQg47GFYAxKI= =u1H4 -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--