Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Franco Fichtner franco at
Thu Feb 9 15:30:24 UTC 2017

Hi Steve,

> On 9 Feb 2017, at 4:09 PM, Steve Wills <swills at> wrote:
> Ports and packages are maintained on the assumption that the user is
> using a supported version of the OS. We didn't decide when to end
> support for 10.1 or 10.2. How long after the end of life for 10.1 would
> you have ports maintain support?

The issue is quite simple and cause of multiple issues:

FreeBSD package management makes an ABI promise in the form of
"FreeBSD:10:amd64", but not even pkg code itself adheres to this,
and thus we have had subtle and yet fatal breakage in 10.2 and 10.3.

And since pkg acts according to the imposed paradigm of a unified
ABI, this will continue to be a source of problems for users who
cannot know what's going on, lest even know how to fix it.

They simply run:

# pkg upgrade

And then their systems are unusable *and* not fixable with pkg.

What are they supposed to do?  They come here.  They want to make
everyone aware that this is a serious issue that shouldn't repeat
in FreeBSD 11.  It's not to late to do that by pinning the pkg ABI
to 11.0 by forcing the proper feature macros.


More information about the freebsd-ports mailing list