Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Mar 2017 15:16:32 +0100
From:      Jan Bramkamp <crest@rlwinm.de>
To:        freebsd-ports@freebsd.org
Subject:   Re: Chicken/egg problem with pkg
Message-ID:  <4ce7ad6f-afa8-4523-9fe3-97ba18cbf03b@rlwinm.de>
In-Reply-To: <20170310140815.GJ16105@kib.kiev.ua>
References:  <a2528a17-bae9-ef23-e2cd-bc4b1c813db7@xs4all.nl> <f21ccbab-2bf9-ccff-3d8a-942cbed4ecf0@rlwinm.de> <20170310140815.GJ16105@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/03/2017 15:08, Konstantin Belousov wrote:
> On Fri, Mar 10, 2017 at 02:55:13PM +0100, Jan Bramkamp wrote:
>> Among other
>> things FreeBSD 10.3 added a bunch of new *at() system calls like openat.
>> These *at() system calls are useful inside (capsicum) sandboxes. Your
>> old 10.1 kernel lacks those systems calls and your old 10.1 libc lacks
>> the stubs to call them anyways. It is this missing stub that causes the
>> new libpkg.so to fail to link.
>
> Although (removed) rest of your mail is mostly accurate, the cited part
> is explicitely false. The openat(2) syscall and friends exist even in
> FreeBSD 8.x.  What has changed in 10.2->10.3 is that the version for
> openat symbol in libc has to be bumped due to some issue with libthr. As
> result, newer binaries require a symbol version which does not exist in
> older libc.

Thanks for the correction.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ce7ad6f-afa8-4523-9fe3-97ba18cbf03b>