From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: Thomas Petazzoni via buildroot <buildroot@buildroot.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 2/3] support/scripts/gen-bootlin-toolchains: drop tweak for Microblaze bleeding-edge toolchains
Date: Sun, 10 Aug 2025 21:57:50 +0200 [thread overview]
Message-ID: <871ppjosox.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <28185e62-aff8-4cad-ac61-a466c85e05a0@smile.fr> (Romain Naour's message of "Sun, 10 Aug 2025 21:08:00 +0200")
>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:
> Hello Peter, Thomas, All,
> Le 10/08/2025 à 20:40, Peter Korsgaard a écrit :
>>>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
>>
>> > On Sun, 10 Aug 2025 16:11:09 +0200
>> > Romain Naour <romain.naour@smile.fr> wrote:
>>
>> >> I guess you are referring to the pending patch from Neal Frager [1].
>> >>
>> >> [1]
>> >> https://patchwork.ozlabs.org/project/buildroot/patch/20250728045145.132333-1-neal.frager@amd.com/
>>
>> > Correct. This patch is pending for Buildroot master, but I did
>> > integrate it into my toolchain build.
>>
>> I wanted to apply this and get 2025.08-rc1 out - But if I read the
>> discussion correctly, gcc 15.x is broken on Microblaze even with that
>> patch, so what do we do?
>>
> Yes, we need another patch [1] to be able to test the rootfs with Qemu.
> Obviously this patch [1] is still unsure (except if you let me patch gcc code :p)
> [1]
> https://github.com/bootlin/buildroot-toolchains/commit/83947c7bb6158072bc2f52b58e90891cd3dc04a2
Ahh. so the issue is (most likely) solved in the bootlin toolchains?
Good, then lets add them.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-10 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 12:48 [Buildroot] [PATCH 1/3] package/gcc: 2024.12 ARC gcc is in fact based on GCC 14.x Thomas Petazzoni via buildroot
2025-08-10 12:48 ` [Buildroot] [PATCH 2/3] support/scripts/gen-bootlin-toolchains: drop tweak for Microblaze bleeding-edge toolchains Thomas Petazzoni via buildroot
2025-08-10 14:11 ` Romain Naour via buildroot
2025-08-10 15:52 ` Thomas Petazzoni via buildroot
2025-08-10 18:40 ` Peter Korsgaard
2025-08-10 19:08 ` Romain Naour via buildroot
2025-08-10 19:57 ` Peter Korsgaard [this message]
2025-08-10 20:16 ` Thomas Petazzoni via buildroot
2025-08-10 20:40 ` Romain Naour via buildroot
2025-08-10 19:59 ` Peter Korsgaard
2025-08-10 12:48 ` [Buildroot] [PATCH 3/3] toolchain/toolchain-external/toolchain-external-bootlin: update to Bootlin toolchains 2025.08-1 Thomas Petazzoni via buildroot
2025-08-10 20:04 ` Peter Korsgaard
2025-08-10 14:05 ` [Buildroot] [PATCH 1/3] package/gcc: 2024.12 ARC gcc is in fact based on GCC 14.x 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=871ppjosox.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=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