Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Hisam Mehboob <hisamshar@gmail.com>
To: David Matlack <dmatlack@google.com>
Cc: Sean Christopherson <seanjc@google.com>,
	kvm@vger.kernel.org, pbonzini@redhat.com, shuah@kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] KVM: selftests: Replace ulong with unsigned long
Date: Fri, 21 Aug 2026 17:45:34 +0500	[thread overview]
Message-ID: <94e1dbf0-de6e-44da-9bc2-772fd6654250@gmail.com> (raw)
In-Reply-To: <CALzav=fs4bqMM7BXNPXqhtbqGzA+LW5fgx2-1Q5=sTN5+krYhw@mail.gmail.com>

On 8/20/26 21:13, David Matlack wrote:
> libuuid is required to build libvfio, which VFIO and KVM selftests
> both depend on.
> 
> How is this problem solved for other libraries, like -lpthread? 

musl does not need a separate pthread library. pthread support is part 
of libc, and libpthread.so is provided as a compatibility stub, so 
-lpthread works without an extra package.

libuuid is an external library from util-linux. On Alpine, installing 
util-linux-dev provides the musl-built libuuid and uuid/uuid.h, and the 
selftests build succeeds. I confirmed this on a fresh Alpine install.

I sent the basename fix as a separate patch:
https://lore.kernel.org/kvm/20260821122110.902382-2-hisamshar@gmail.com/


      reply	other threads:[~2026-08-21 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 17:08 [PATCH v2] KVM: selftests: Replace ulong with unsigned long Hisam Mehboob
2026-08-17 22:04 ` Hisam Mehboob
2026-08-17 22:24   ` Sean Christopherson
2026-08-17 22:42     ` Hisam Mehboob
2026-08-18 16:27       ` Sean Christopherson
2026-08-18 18:19         ` Hisam Mehboob
2026-08-18 19:28           ` Sean Christopherson
2026-08-18 21:03             ` Hisam Mehboob
2026-08-20 16:13               ` David Matlack
2026-08-21 12:45                 ` Hisam Mehboob [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=94e1dbf0-de6e-44da-9bc2-772fd6654250@gmail.com \
    --to=hisamshar@gmail.com \
    --cc=dmatlack@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=shuah@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox