Date: Thu, 7 Nov 2002 09:35:19 -0800 (PST) From: John Polstra <jdp@polstra.com> To: current@freebsd.org Cc: sgk@troutmask.apl.washington.edu Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <200211071735.gA7HZJvl065569@vashon.polstra.com> In-Reply-To: <20021107173023.GA41366@troutmask.apl.washington.edu> References: <200211070030.gA70UF05024508@troutmask.apl.washington.edu> <20021107171741.GA41290@troutmask.apl.washington.edu> <200211071721.gA7HLrRY065532@vashon.polstra.com> <20021107173023.GA41366@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20021107173023.GA41366@troutmask.apl.washington.edu>, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > On Thu, Nov 07, 2002 at 09:21:53AM -0800, John Polstra wrote: > > 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. That would surprise me, but I haven't tried it myself. Inspection of the ezm3 bootstrap shows that it has references to __sF. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa 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?200211071735.gA7HZJvl065569>