Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	Petr Vorel <pevik@seznam.cz>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump version to 20230127
Date: Sat, 15 Apr 2023 10:05:47 +0200	[thread overview]
Message-ID: <20230415080547.GC2819@scaer> (raw)
In-Reply-To: <CAB1t1CwsMzTgYyAY_AFftyUh+OdXADpKBXTw0Ot1reibt=fWgg@mail.gmail.com>

Petr, All,

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.

That one is using kernel headers 4.20.13:

    https://developer.arm.com/downloads/-/gnu-a
    https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu-a/10.3-2021.07/srcrel/gcc-arm-src-snapshot-10.3-2021.07-manifest.txt

    Excerpt:
        [linux]
        type=git
        url=git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
        version=v4.20.13

It's the last toolchain from ARM that is not impacted by:
    https://bugs.linaro.org/show_bug.cgi?id=5825#c34

Even the release from 2020-12 still has kernel headers 4.20.13:
    https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads
    https://armkeil.blob.core.windows.net/developer/Files/downloads/gnu/12.2.rel1/srcrel/arm-gnu-toolchain-src-snapshot-12.2.rel1-manifest.txt

    Excerpt:
        [linux]
        type=git
        url=git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
        version=v4.20.13

So, whether impacted or not by the abovementioned bug, people using
official tolchains from ARM use kernel headers 4.20.13, which I
understand do not have that fix.

And that's only by looking at one of the few toolchains Buildroot knows
of. There are countless such toolchains that have been built over the
years, and that they can't update (e.g. because they are using the
official toolchain provided by their chipco vendor, or because the
kernel they are using for their board is a fork by some vendor and does
not have that fix, and so on...).

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

  reply	other threads:[~2023-04-15  8:06 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 [this message]
2023-04-15  8:40           ` Yann E. MORIN
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=20230415080547.GC2819@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