Date: Thu, 6 Sep 2001 10:39:37 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: bugs@freebsd.org Cc: marc@enginet.com Subject: Re: 4.4-RC cvsup-bin now missing, cvsup port broken? Message-ID: <200109061739.f86Hdb600410@vashon.polstra.com> In-Reply-To: <200109061721.KAA10939@enginet.com> References: <200109061721.KAA10939@enginet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <200109061721.KAA10939@enginet.com>, Marc Frajola <marc@enginet.com> wrote: > In <200109061702.f86H2SD10362@vashon.polstra.com>, John Polstra wrote: > > > > That's "packages" -- not "ports". The packages are specially built > > to be statically linked. > > Doh! Thanks for the quick response. You're welcome. FWIW, this same thing has confused several people. > When installing the package from the stable snapshot server, I > noticed there were two packages, cvsup-16.1_1.tgz (dated 6/22) > and cvsup-16.1c.tgz (dated 8/13). I installed the cvsup-16.1c.tgz > package because of the later date, if this is not the correct one, > please let me know.. That's the one I recommend. It is from the cvsup-devel port, which is the latest CVSup snapshot. The other one (16.1_1) is the older 16.1 release plus one patch. The snapshot has quite a few additional bug fixes. It's really only a snapshot (instead of a release) because I haven't gotten around to updating some documentation and finishing a couple of half-baked new features. > > > m3ship: quake error: unable to open "/usr/ports/lang/pm3-base/work/pm3-1.1.15/network/tcplibs/tcp/FreeBSD4//FreeBSD4" for reading > > > > One other person reported this problem, on one and only one of his > > systems. Unfortunately, I can't reproduce it and I don't have a clue > > what would cause it to happen. > > I'd be happy to help reproduce/debug this, send me email directly > with any suggestions about stuff I can do/try that would help partition > the problem.. Thanks. I spend a lot of time with the other guy who had the problem, but we never could figure out what was going on. It failed on one of his systems but worked fine on several others. We never could find any significant differences between the systems that would explain this. If there is anything at all unusual about your setup, please let me know. Things to look for would be: - make.conf settings - environment variables (PATH, LD_LIBRARY_PATH, etc.) - unusual mount configurations and symbolic links - moldy old installations of modula-3 already on the system > FWIW, I use cvsup _all_ the time, and have very much appreciated > your efforts over the years both in authoring the utility and > maintaining it. Thanks!! Thanks, that's nice to hear! John -- John Polstra jdp@polstra.com 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-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109061739.f86Hdb600410>