From owner-freebsd-ports Sun Mar 12 10: 4:38 2000 Delivered-To: freebsd-ports@freebsd.org Received: from argon.blackdawn.com (13-039.008.popsite.net [209.69.13.39]) by hub.freebsd.org (Postfix) with ESMTP id EC6CC37BBDF for ; Sun, 12 Mar 2000 10:04:35 -0800 (PST) (envelope-from will@argon.blackdawn.com) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 0E6C319B8; Sun, 12 Mar 2000 13:04:17 -0500 (EST) Date: Sun, 12 Mar 2000 13:04:17 -0500 From: Will Andrews To: Dag-Erling Smorgrav Cc: freebsd-ports@FreeBSD.ORG Subject: Re: ports/17340: Ports that need Xaw3d won't build Message-ID: <20000312130416.F7461@argon.blackdawn.com> References: <200003121440.GAA86842@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003121440.GAA86842@freefall.freebsd.org>; from des@flood.ping.uio.no on Sun, Mar 12, 2000 at 06:40:03AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Mar 12, 2000 at 06:40:03AM -0800, Dag-Erling Smorgrav wrote: > > Ports that depend on Xaw3d won't build because the Xaw3d's library version > > number is now 7 instead of 6. What's more, the PLIST for the Xaw3d port > > incorrectly lists lib/libXaw3d.so.6.1 instead of lib/libXaw3d.so.7. > > Update: it only seems to happen when running XFree86 4.0, so it may > not be as bad as I originally thought. Yeah.. the reason is because only the Xaw3d shlib version numbers are updated in XFree86 4.0, as opposed to 3.3.6. The Xaw3d port is not at fault here. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message