From: Maxim Kochetkov via buildroot <buildroot@busybox.net>
To: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH v2] package/gcc: fix libsanitizer in gcc 11.1, 10.3 for linux 5.13
Date: Tue, 27 Jul 2021 10:05:51 +0300 [thread overview]
Message-ID: <ea0533dc-e2fc-aa00-cc0d-ddaec8da89e9@inbox.ru> (raw)
In-Reply-To: <20210705125139.1516789-1-fido_max@inbox.ru>
05.07.2021 15:51, Maxim Kochetkov via buildroot wrote:
> Starting from 5.13 Cyclades async mux support is dropped from linux kernel:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f76edd8f7ce06cdff2fe5b6b39a49644c684a161
>
> But gcc's libsanitizer uses <linux/cyclades.h> header.
> This issue is fixed by:
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=745dae5923aba02982563481d75a21595df22ff8
>
> Right now just gcc 9.4.0 has this commit and 8.4.0 is proposed to be deleted.
> So we need to add this patch for 10.3 and 11.1 to fix build with linux kernel 5.13.
>
> Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru>
Fixes:
http://autobuild.buildroot.net/results/3ab15a8e16a929dfb2b99b371fa9838d4e137bf1/
Fixes:
http://autobuild.buildroot.net/results/e78a68cfe68461a78a50ee41a0ed5f0923611b00/
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-07-27 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 12:51 [Buildroot] [PATCH v2] package/gcc: fix libsanitizer in gcc 11.1, 10.3 for linux 5.13 Maxim Kochetkov
2021-07-20 20:08 ` James Hilliard
2021-07-23 8:02 ` Michael Walle
2021-07-26 6:01 ` Maxim Kochetkov via buildroot
2021-07-27 7:05 ` Maxim Kochetkov via buildroot [this message]
2021-07-31 10:06 ` Thomas Petazzoni
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=ea0533dc-e2fc-aa00-cc0d-ddaec8da89e9@inbox.ru \
--to=buildroot@busybox.net \
--cc=fido_max@inbox.ru \
/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.