From: Petr Vorel <petr.vorel@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/1] lapi: Add sysinfo.h to fix build with MUSL libc
Date: Tue, 27 Oct 2020 20:18:23 +0100 [thread overview]
Message-ID: <20201027191823.GB25803@dell5510> (raw)
In-Reply-To: <20201015190620.GA9408@dell5510>
Hi Cyril,
...
> I've added this patch already to buildroot, but if kernel patch get accepted,
> it'd be kept only temporarily (I think they don't have patches for musl based
> toolchains, otherwise they'd take Alpine's patch by now. But they instead drop
> support for these toolchains in packages which don't upstream the solution.
> > Apart from that it looks like the kernel patch has been ignored. I guess
> > that you should try to push it a bit more before we give up and apply
> > workarounds...
> Tried next version, let's see.
> https://lore.kernel.org/linux-api/20201015190013.8901-1-petr.vorel@gmail.com/
Patch has been included into next tree [1]. If not reverted, it would fix the
problem for newer kernel headers. Distros using MUSL (Buildroot and OpenEmbedded)
will have to keep this patch for older headers and update it as we might add
more <sys/sysinfo.h> in the future, but that's not that difficult.
Kind regards,
Petr
[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20201027&id=92a5a1734a34380444dd9cace835525c5f51a9ed
next prev parent reply other threads:[~2020-10-27 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 23:12 [LTP] [RFC PATCH 1/1] lapi: Add sysinfo.h to fix build with MUSL libc Petr Vorel
2020-10-01 23:21 ` Petr Vorel
2020-10-14 14:33 ` Cyril Hrubis
2020-10-15 19:06 ` Petr Vorel
2020-10-27 19:18 ` Petr Vorel [this message]
2023-04-27 18:54 ` Petr Vorel
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=20201027191823.GB25803@dell5510 \
--to=petr.vorel@gmail.com \
--cc=ltp@lists.linux.it \
/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