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

Matthew Seaman matthew at
Thu Feb 9 16:42:58 UTC 2017

On 2017/02/09 16:24, Franco Fichtner wrote:
>> On 9 Feb 2017, at 5:21 PM, Steve Wills <swills at> wrote:
>> We provide backwards compatibility, not forwards compatibility.

> But don't you see that users won't know this?

Forward compatibility has been the ABI stability guarantee basically
ever since there has been a FreeBSD project.   Anything you compile now
will continue to work on later OS versions.  However you cannot
guarantee it will work on earlier versions.

The fact that newer binaries frequently will still work on older
releases in no way invalidates this claim.  That's just a reflection of
the fact that the system ABIs do not change particularly frequently.

> This is a good theory, yet it is difficult in practice because it is
> not being enforced.

Why do you think it is not being enforced?  Forwards compatibility means
that during the lifetime of a major branch you can only *add* symbols to
the system shared libraries, not remove them nor modify any existing
symbols.  The project has held to that for many years -- not breaking
ABI forwards compatibility is a really big deal amongst developers.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 972 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the freebsd-ports mailing list