From: Andreas Ziegler <br025@umbiko.net>
To: Rustam <rustamabd@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/1] toolchain/toolchain-external: introduce BR2_TOOLCHAIN_EXTERNAL_UPDATE_LINUX_HEADERS
Date: Sat, 14 Mar 2026 07:27:00 +0000 [thread overview]
Message-ID: <132cf3552a756277ea2fa7c1e7e5b4ae@umbiko.net> (raw)
In-Reply-To: <CAPzS6u_1RaVGk3gaD0jk1pP0e_azWxPFSX42G_ejqR-sWAOJKA@mail.gmail.com>
Hi ALL,
On 2025-12-28 16:10, Rustam wrote:
> On Sat, 27 Dec 2025 at 23:24, Thomas Petazzoni
> <thomas.petazzoni@bootlin.com>
> wrote:
>
>> Hello Rustam,
>>
> Hi Thomas,
>
[...]
>> Currently restricted to glibc-based toolchains as glibc is backward-
>> and
>> > forward-compatible with different kernel versions while uClibc and musl
>> > are not.
>>
>> Not sure why this matters here though. Could you clarify?
>>
> This is just a safeguard to prevent issues. From personal experience,
> uClibc and musl sometimes run into issues unless they are compiled for
> the
> specific linux version on which they run.
> So this feature is only usable in combination with glibc.
>
Actually this suggestion came from me. I have Buildroot build my
toolchains, using uClibc and musl. I occasionally had problems when
switching kernel versions and forgetting to rebuild everything. This
might be a dependency issue, not directly related to the toolchain, but
since Rustam only tested this using glibc, the restriction seems
appropriate.
>
>> Thanks!
>>
>> Thomas
>> --
>> Thomas Petazzoni, co-owner and CEO, Bootlin
>> Embedded Linux and Kernel engineering and training
>> https://bootlin.com
>
> Hope this clarifies,
> Regards,
> Rustam
Kind regards,
Andreas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-14 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 21:14 [Buildroot] [PATCH v2 1/1] toolchain/toolchain-external: introduce BR2_TOOLCHAIN_EXTERNAL_UPDATE_LINUX_HEADERS Rustam Abdullaev
2025-12-27 22:24 ` Thomas Petazzoni via buildroot
2025-12-28 16:10 ` Rustam
2026-03-14 7:27 ` Andreas Ziegler [this message]
2026-02-02 13:41 ` John Ernberg via buildroot
2026-03-13 23:03 ` Romain Naour via buildroot
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=132cf3552a756277ea2fa7c1e7e5b4ae@umbiko.net \
--to=br025@umbiko.net \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=rustamabd@gmail.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.