From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
buildroot@buildroot.org,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Petr Vorel <pevik@seznam.cz>
Subject: Re: [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump version to 20230127
Date: Sat, 15 Apr 2023 10:40:56 +0200 [thread overview]
Message-ID: <20230415084056.GD2819@scaer> (raw)
In-Reply-To: <20230415080547.GC2819@scaer>
Petr, All,
On 2023-04-15 10:05 +0200, Yann E. MORIN spake thusly:
> On 2023-04-14 22:54 +0200, Petr Vorel spake thusly:
> > On Fri, 14 Apr 2023 at 21:01, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> [--SNIP--]
> > > Unless the upstream ltp has provision for supporting both kind of
> > > headers, with or without the fix, then yes, I think this should be
> > > rebased and kept. And re-submit upstream to explain it will support
> > > older, existing toolchains.
> > I'll verify again support/config-fragments/autobuild/toolchain-configs.csv, if
> > there are tests which will fail. Or are these toolchains elsewhere? I'm asking
> > to give some proof to upstream that there are toolchains with older kernel
> > headers. Because upstream expects that old distros are being tested with old
> > version and if people want new software they are able to update their
> > toolchain. They will see a real example than just claiming "it's needed".
> > Also have a way to check in the future that workaround can be removed.
>
> I looked at toolchain/toolchain-external/toolchain-external-arm-aarch64/
> which is the first external toolchain in the list of toolchain Buildroot
> knows of.
So, that's a glibc toolchain, right, so it is not impacted by the bug.
Still, the reasonging stands: in the wilde, there are toolchains that
have been built before that fix existed, and people are not updating
their toolchains for various reasons, the most prominent one being "it
is suplied by the chipco, so we use it".
It is not just about the toolchains we know of in Buildroot. by the way.
Now, we could also very well decide that ltp-testsuite depends on kernel
headers >= 5.11 for musl toolchains, which would probably be the actual
solution, if upstream really does not want to fix that situation.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-04-15 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 20:14 [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump version to 20230127 Petr Vorel
2023-04-05 20:14 ` [Buildroot] [PATCH 2/2] package/ltp-testsuite: Backport fix for buildroot toolchain Petr Vorel
2023-04-05 20:27 ` [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump version to 20230127 Petr Vorel
2023-04-10 17:24 ` Yann E. MORIN
2023-04-12 18:12 ` Petr Vorel
2023-04-14 19:01 ` Yann E. MORIN
2023-04-14 20:54 ` Petr Vorel
2023-04-15 8:05 ` Yann E. MORIN
2023-04-15 8:40 ` Yann E. MORIN [this message]
2023-04-15 23:21 ` Petr Vorel
2023-04-16 7:45 ` Yann E. MORIN
2023-04-16 15:08 ` 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=20230415084056.GD2819@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=petr.vorel@gmail.com \
--cc=pevik@seznam.cz \
--cc=thomas.petazzoni@free-electrons.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