Date: Thu, 7 Nov 2002 09:30:23 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021107173023.GA41366@troutmask.apl.washington.edu> In-Reply-To: <200211071721.gA7HLrRY065532@vashon.polstra.com> References: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> <20021106.231940.123343134.imp@bsdimp.com> <200211071640.gA7GeWJk065460@vashon.polstra.com> <20021107171741.GA41290@troutmask.apl.washington.edu> <200211071721.gA7HLrRY065532@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 07, 2002 at 09:21:53AM -0800, John Polstra wrote: > In article <20021107171741.GA41290@troutmask.apl.washington.edu>, > Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > > > I rebuilt cvsup from net/cvsup yesterday on a new world, and > > it appears to be working fine. What problems should I expect? > > It's possible that if you already have a working installation of pm3 > or ezm3, you'll be able to build CVSup on -current. But if you try to > build pm3 or ezm3 from scratch, you'll find that the build fails. > I removed all ports because of the __sF symbol problem. I simply did "cd /usr/ports/net/cvsup ; make install" and this automatically installed ezm3. pkg_info doesn't show pm3 installed on system. Perhaps, only pm3 is the port that will have the problem. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021107173023.GA41366>