From owner-freebsd-ports@FreeBSD.ORG Thu Feb 15 06:09:51 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2380416A402 for ; Thu, 15 Feb 2007 06:09:51 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmmtao03.cox.net (eastrmmtao03.cox.net [68.230.240.36]) by mx1.freebsd.org (Postfix) with ESMTP id 5F5F213C441 for ; Thu, 15 Feb 2007 06:09:50 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmmtao03.cox.net (InterMail vM.6.01.06.03 201-2131-130-104-20060516) with ESMTP id <20070215053252.GUQK28701.eastrmmtao03.cox.net@eastrmimpo01.cox.net> for ; Thu, 15 Feb 2007 00:32:52 -0500 Received: from serene.no-ip.org ([72.200.30.62]) by eastrmimpo01.cox.net with bizsmtp id PhYr1W00K1LR1K40000000; Thu, 15 Feb 2007 00:32:51 -0500 Received: from serene.no-ip.org (localhost [127.0.0.1]) by serene.no-ip.org (8.13.8/8.13.8) with ESMTP id l1F5Wp8o020384 for ; Wed, 14 Feb 2007 23:32:51 -0600 (CST) (envelope-from conrads@cox.net) Message-Id: <200702150532.l1F5Wp8o020384@serene.no-ip.org> Date: Wed, 14 Feb 2007 23:32:51 -0600 From: "Conrad J. Sabatier" To: freebsd-ports@freebsd.org X-Mailer: Claws Mail 2.7.2 (GTK+ 2.10.9; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Library minor versions conflicting with PLIST with no minor versions X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 06:09:51 -0000 I know I've seen a few other reports of this problem in the lists recently, and am just wondering if anyone has anything further to report. I've been seeing the odd port here and there building libraries with minor version numbers included in the filenames, whereas the PLIST specifies only the major version numbers, or vice versa. This is causing other ports to fail to link properly, in some cases where the dependent port is expecting the library with the minor number included, and others where the dependent port is expecting the library without the minor number. Very odd behavior, and it's only cropped up within the last week or two. I can't figure out what the heck's going on here. This is under 7.0-CURRENT on the amd64 arch, by the way. Anyone? -- Conrad J. Sabatier