From owner-freebsd-ports@FreeBSD.ORG Fri Jan 16 00:59:27 2015 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87514DBD for ; Fri, 16 Jan 2015 00:59:27 +0000 (UTC) Received: from gw.catspoiler.org (cl-1657.chi-02.us.sixxs.net [IPv6:2001:4978:f:678::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 26CDCB68 for ; Fri, 16 Jan 2015 00:59:27 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id t0G0xHob019723; Thu, 15 Jan 2015 16:59:21 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <201501160059.t0G0xHob019723@gw.catspoiler.org> Date: Thu, 15 Jan 2015 16:59:17 -0800 (PST) From: Don Lewis Subject: Re: Fwd: [package - 84amd64-default][graphics/libspiro] Failed for libspiro-0.2.20131203, 1 in build To: cyberbotx@cyberbotx.com In-Reply-To: <54B7E239.2080704@cyberbotx.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 00:59:27 -0000 On 15 Jan, Naram Qashat wrote: > I'm looking to see if someone who is more knowledgeable about perl or libtool or > whatever to help me solve the below problem. > > Basically, libspiro's internal version number is 0.2.20130930. Under FreeBSD 9.X > and up, config.log shows LIBSPIRO_VERSION as being 0:2:0 and libtool completes > as expected. However, under 8.X, LIBSPIRO_VERSION instead becomes $0:2:0, and > libtool gets :2:0 instead of 0:2:0, and thus fails to build, as shown below. > > I'd tried manually having autoreconf and automake run (as libspiro's README.md > explains), but that didn't help at all. > > I'm not familiar enough with the build process of applications that utilize > libtool to know why this is the case. If anyone has any insights into this, I'd > really appreciate it. See It looks like upstream has already fixed this in their repo after the last release.