Library minor versions conflicting with PLIST with no minor
Conrad J. Sabatier
conrads at cox.net
Fri Feb 16 23:40:19 UTC 2007
On Thu, 15 Feb 2007 01:40:06 -0500
Kris Kennaway <kris at obsecurity.org> wrote:
> On Wed, Feb 14, 2007 at 11:32:51PM -0600, Conrad J. Sabatier wrote:
> > 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?
> See the heads up I sent the other week.
Could you be a little more specific? Which list did you send it to?
Did it have "Heads Up" in the Subject line?
Conrad J. Sabatier <conrads at cox.net>
More information about the freebsd-ports