Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Jan 2017 14:53:57 +0000
From:      Matthew Seaman <matthew@FreeBSD.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: libpkg.so.3: Undefined symbol "utimensat"
Message-ID:  <18620574-6ea8-bbef-53b3-5ef5f9168df7@FreeBSD.org>
In-Reply-To: <20170113134432.GA52870@neutralgood.org>
References:  <587802c0.dc08620a.da847.b4d7@mx.google.com> <20170113134432.GA52870@neutralgood.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--thDGsCQIQpJjpXvgbOfvnnXX6Prmk9r7m
Content-Type: multipart/mixed; boundary="GsAAuJkS2JXcN0EXEP26FFXXbfe8FFh3J";
 protected-headers="v1"
From: Matthew Seaman <matthew@FreeBSD.org>
To: freebsd-questions@freebsd.org
Message-ID: <18620574-6ea8-bbef-53b3-5ef5f9168df7@FreeBSD.org>
Subject: Re: libpkg.so.3: Undefined symbol "utimensat"
References: <587802c0.dc08620a.da847.b4d7@mx.google.com>
 <20170113134432.GA52870@neutralgood.org>
In-Reply-To: <20170113134432.GA52870@neutralgood.org>

--GsAAuJkS2JXcN0EXEP26FFXXbfe8FFh3J
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 2017/01/13 13:44, Kevin P. Neal wrote:
>> I get the following error when I tried to do "pkg upgrade" on FreeBSD =
10.2
>> 64bit
>>
>> =20
>>
>> Proceed with this action? [y/N]: y
>>
>> [1/102] Upgrading xproto from 7.0.28 to 7.0.31...
>>
>> [1/102] Extracting xproto-7.0.31:   0%/usr/local/lib/libpkg.so.3: Unde=
fined
>> symbol "utimensat"

> I have no idea how this happened.

It's because utimensat(2) is a new syscall in 10.3-RELEASE and above,
and as pkg(8) is now being built on 10.3-RELEASE (as that's the lowest
supported 10.x RELEASE since the beginning of the month) it now tries to
use that syscall.

Means 10.1 and 10.2 users of the standard FreeBSD packages are going to
be unhappy until they can upgrade to 10.3.  A work around is to use
pkg-static, but that's not completely foolproof either as any other
packaged software could use utimensat(2) and suffer from the same problem=
=2E

	Cheers,

	Matthew



--GsAAuJkS2JXcN0EXEP26FFXXbfe8FFh3J--

--thDGsCQIQpJjpXvgbOfvnnXX6Prmk9r7m
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQJ8BAEBCgBmBQJYeOoNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw
MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnRiAP/isJQmEYELmZpX39FhT+GPdi
mwzAB++D4BSooQPocYHRz69RpiPE9XTxs2ch0aUDatMx7W8c9g2xapjS6AKq0dDx
8RGc6sNI5+qVWJ2QHyzy0WWrBY70S72i0qwarrZVhH0fWfHPwTMNiT+T31YkN149
aoLzZofbLeEqoDWLRFSH6W6AX99vPMlSmx2mx6mryIze1q7DoZRXMC4NANNefzpC
wYUw1V0oo57pKnkJtv2MsflIpwVZMd3V86sGR/Is1AoIvwfDS9CYRD3eJ72UTO94
/qgpQdimiEkQOqDcHkJTsg/3rAXoOnf6F1rimHOhsVAh/AGLYLR1hskYGBJ5sq9U
f8KuijArM1La9XF/W8Ip5ZG1sT7O0I72Lxx74owmfW7tMJQDWu4wvSJ81A5yAq39
m+7SSuqY7iZPKlxm8xTUQ2kBy4WFwbgKk/HHiYOdMs4gZfrFJHxItsq6xjfHBLrA
PTlTSz6xT2Eynl8fhdbprazpE2gKnTKCLPjbK0QRYpT8JgVsZkVP0zZOln8MyyDG
CrI5z27q9c9nTxYjXCKQ9ggv5wGSvPAUwdvm0GAoJKkgDkkCArIPa9qDXwUCsizN
OUe2Foet7yMyz7FzjjOFlukMa0OrKLfZ1Au1J7wJS7QHLY233INB4UO3/ubxsQm7
UpVN4cas+hIjyL5xKb+D
=1MYY
-----END PGP SIGNATURE-----

--thDGsCQIQpJjpXvgbOfvnnXX6Prmk9r7m--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18620574-6ea8-bbef-53b3-5ef5f9168df7>