Date: Mon, 26 Jan 2004 22:55:09 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Pat Lashley <patl+freebsd@volant.org> Cc: freebsd-sparc64@freebsd.org Subject: Re: Problem with compiling ports Message-ID: <20040127065508.GA55455@xor.obsecurity.org> In-Reply-To: <4273990816.1075146026@mccaffrey.phoenix.volant.org> References: <40156661.4070708@njmc.com> <4273990816.1075146026@mccaffrey.phoenix.volant.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <jlemay@njmc.com>= =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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040127065508.GA55455>