From: Greg KH <gregkh@linuxfoundation.org>
To: Brahmajit Das <listout@listout.xyz>
Cc: linux-kernel@vger.kernel.org, alexander.usyskin@intel.com,
tomas.winkler@intel.com
Subject: Re: [RFC PATCH] samples: mei: Fix building on musl libc
Date: Tue, 1 Jul 2025 07:13:15 +0200 [thread overview]
Message-ID: <2025070153-deputy-these-7ca3@gregkh> (raw)
In-Reply-To: <20250630204430.10968-1-listout@listout.xyz>
On Tue, Jul 01, 2025 at 02:14:30AM +0530, Brahmajit Das wrote:
> The header bits/wordsize.h is glibc specific and on building on musl
> with allyesconfig results in
>
> samples/mei/mei-amt-version.c:77:10: fatal error: bits/wordsize.h: No such file or directory
> 77 | #include <bits/wordsize.h>
> | ^~~~~~~~~~~~~~~~~
>
> mei-amt-version.c build file without bits/wordsize.h on musl. I'm not
> sure we can remove the header completely or how it's used under glibc.
Can you look into that instead of just adding a #ifdef that might not
actually be needed?
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-01 5:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 20:44 Brahmajit Das
2025-07-01 5:13 ` Greg KH [this message]
2025-07-01 14:38 ` Brahmajit Das
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=2025070153-deputy-these-7ca3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=listout@listout.xyz \
--cc=tomas.winkler@intel.com \
/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
all inboxes | Powered by JetHome®