linux-kernel - Re: [RFC PATCH] samples: mei: Fix building on musl libc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <6iseanlkrqoci3fgylsnzf4lxrvtf6o32tfvpoux4axyugiv6a@dnx76o5t2l2j>
Date: Tue, 1 Jul 2025 20:08:34 +0530
From: Brahmajit Das <listout@...tout.xyz>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, alexander.usyskin@...el.com, 
	tomas.winkler@...el.com
Subject: Re: [RFC PATCH] samples: mei: Fix building on musl libc

On 01.07.2025 07:13, Greg KH wrote:
> 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

Did some testing and it seems like we can remove the bits/wordsize.h. It
does not affect build on either glibc or musl.
I'll send a patch.

-- 
Regards,
listout