From owner-freebsd-ports@freebsd.org Wed Feb 8 11:46:20 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A09B9CD6E1D for ; Wed, 8 Feb 2017 11:46:20 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (unknown [IPv6:2a01:4f8:a0:51d6::108:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 61383137A for ; Wed, 8 Feb 2017 11:46:20 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (dslb-092-078-013-237.092.078.pools.vodafone-ip.de [92.78.13.237]) by host64.shmhost.net (Postfix) with ESMTPSA id 33FCC84924; Wed, 8 Feb 2017 12:46:10 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?! From: Franco Fichtner In-Reply-To: Date: Wed, 8 Feb 2017 12:46:09 +0100 Cc: freebsd-ports Content-Transfer-Encoding: quoted-printable Message-Id: References: To: scratch65535@att.net X-Mailer: Apple Mail (2.3259) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 11:46:20 -0000 > On 8 Feb 2017, at 12:29 PM, = wrote: >=20 > I just tried to install the fuse-nfts pkg under 10.2 on my > server-of-all-work. But after requiring me to "upgrade" pkg, the > fuse-ntfs install failed, apparently because there's an undefined > symbol ("utimenstat") in pkg itself! >=20 > How do I extricate myself? The latest supported release is FreeBSD 10.3 and packages are therefore build against it. It creates this soft breakage inside the fixed ABI, which quite a few people run into. There are two solutions: (a) Build the packages yourself on a FreeBSD 10.2. (b) Upgrade to FreeBSD 10.3 and do a "pkg upgrade -f" run. And for the wicked: (c) Let's please address this issue within FreeBSD so users don't run = into it. ;) Cheers, Franco=