Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Jan 2004 11:40:26 -0800
From:      Pat Lashley <patl+freebsd@volant.org>
To:        John LeMay <jlemay@njmc.com>, freebsd-sparc64@freebsd.org
Subject:   Re: Problem with compiling ports
Message-ID:  <4273990816.1075146026@mccaffrey.phoenix.volant.org>
In-Reply-To: <40156661.4070708@njmc.com>
References:  <40156661.4070708@njmc.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--On Monday, January 26, 2004 14:11:29 -0500 John LeMay <jlemay@njmc.com> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4273990816.1075146026>