Date: Tue, 21 Dec 2004 05:36:38 -0600 From: "Conrad J. Sabatier" <conrads@cox.net> To: obrien@freebsd.org Cc: freebsd-amd64@freebsd.org Subject: Re: 5.3R cvsup failure, libm.so.2. COMPAT files missing? Message-ID: <20041221053638.33947b3a@dolphin.local.net> In-Reply-To: <20041221021702.GB83892@dragon.nuxi.com> References: <20041213152257.A3882@rc.tex-an.net> <20041219100920.GB7942@dragon.nuxi.com> <20041220192745.0e941442@dolphin.local.net> <20041221021702.GB83892@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 20 Dec 2004 18:17:02 -0800, "David O'Brien" <obrien@freebsd.org> wrote: > On Mon, Dec 20, 2004 at 07:27:45PM -0600, Conrad J. Sabatier wrote: > > On Sun, 19 Dec 2004 02:09:20 -0800, "David O'Brien" > > <obrien@freebsd.org> wrote: > > If you do the same command without the grep: > > > > $ ldd /usr/local/bin/cvsup > > /usr/local/bin/cvsup: > > libz.so.2 => /lib/libz.so.2 (0x8006dd000) > > libm.so.3 => /lib/libm.so.3 (0x8007f0000) > > libc.so.5 => /lib/libc.so.5 (0x80090d000) > > > > Whereas CURRENT, of course, is up to libc.so.6 now. Fortunately, I > > was careful not to delete the older libc when the version bump > > occurred. Of course, /etc/libmap.conf can always be used as a > > workaround, but I try to avoid that as much as possible. > > > > MD5 (/usr/ports/distfiles/cvsup-without-gui.amd64.tar.bz2) = > > 5e83e6b68696058ebcc4e8666e8442a9 > > > > Perhaps it's time to update the cvsup port for amd64? > > An update would render it unusable on 5.3. Right now one can use the > compat5x port (once made). What about perhaps having a separate distfile for CURRENT, with a little .if __FreeBSD_version == ... magic in the port's Makefile? I would venture to say that the majority of amd64 users are, in fact, running CURRENT. -- Conrad J. Sabatier <conrads@cox.net> -- "In Unix veritas"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041221053638.33947b3a>