svn commit: r368005 - in head: lib/libprocstat share/man/man4 sys/opencrypto sys/sys tools/tools/crypto usr.bin/procstat

John Baldwin jhb at FreeBSD.org
Mon Dec 7 20:36:34 UTC 2020


On 12/7/20 11:11 AM, Kyle Evans wrote:
> On Mon, Dec 7, 2020 at 12:58 PM John Baldwin <jhb at freebsd.org> wrote:
>>
>> On 12/6/20 8:51 PM, Steve Wills wrote:
>>> Hi,
>>>
>>> On 11/24/20 7:10 PM, John Baldwin wrote:
>>>> Author: jhb
>>>> Date: Wed Nov 25 00:10:54 2020
>>>> New Revision: 368005
>>>> URL: https://svnweb.freebsd.org/changeset/base/368005
>>>>
>>>> Log:
>>>>    Remove the cloned file descriptors for /dev/crypto.
>>>>
>>>
>>> Would this change warrant a bump of __FreeBSD_version? I only noticed
>>> because PR 251470 (radare2 not building due to KF_TYPE_CRYPTO).
>>
>> Hmm, perhaps so, though ports could also use #ifdef KF_TYPE_CRYPTO (and
>> that is probably preferred for anything using C).  Looks like we haven't
>> yet had another bump of __FreeBSD_version so I can do that.
>>
> 
> There's surely a better way, but this version bump would've actually
> been really handy for detecting the resulting qemu-user-static
> fallout. The build was broken for about ~9 days, neither the official
> builder or my local builder felt compelled to rebuild it absent the
> bump because I had just built it a couple revisions prior. =-(
> 
> I'm kind of leaning towards trying to shoehorn a qemu-user-static
> build into ci.f.o somewhere, though, since it's used as a part of
> producing some of the weekly snapshot images and digs pretty deeply in
> other areas. I've got a Cirrus config for qemu-user-static and Cirrus
> builds it regularly for me, but that's not so helpful when the image
> it builds against is also tied to the weekly snapshot process.

qemu-user uses this flag?  What on earth can it be using it for?

-- 
John Baldwin


More information about the svn-src-head mailing list