From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/testing: TestFileCapabilities: update kernel to 4.19.310
Date: Wed, 10 Apr 2024 23:46:48 +0200 [thread overview]
Message-ID: <20240410234648.70732fa4@windsurf> (raw)
In-Reply-To: <20240327162319.149021-1-romain.naour@smile.fr>
On Wed, 27 Mar 2024 17:23:19 +0100
Romain Naour <romain.naour@smile.fr> wrote:
> Since the toolchain Bootlin update to 2023.11-1 [1], the arm Linux
> kernel build is broken with binutils >= 2.41 with:
>
> arch/arm/mm/proc-v7.S: Assembler messages:
> arch/arm/mm/proc-v7.S:640: Error: junk at end of line, first unrecognized character is `#'
>
> A similar issue has already be fixed for qemu m68k [2].
>
> Bump to the latest kernel 4.19 that already include the backport
> of 790756c7e022 ("ARM: 8933/1: replace Sun/Solaris style flag on section directive")
>
> [1] 7e0e6e3b8618ab942f25b11ee72fbc5a4deefdf1
> [2] a1ce9474e40f731f327035d8c0962abb16f00ff7
>
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/6414160106 (TestFileCapabilities)
>
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> ---
> support/testing/tests/core/test_file_capabilities.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-10 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 16:23 [Buildroot] [PATCH] support/testing: TestFileCapabilities: update kernel to 4.19.310 Romain Naour
2024-04-10 21:46 ` Thomas Petazzoni via buildroot [this message]
2024-05-06 20:51 ` Peter Korsgaard
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=20240410234648.70732fa4@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox