From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Romain Naour <romain.naour@gmail.com>
Cc: Guo Ren <ren_guo@c-sky.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/5] configs: remove qemu_csky defconfigs
Date: Sun, 3 Oct 2021 16:22:37 +0200 [thread overview]
Message-ID: <20211003162237.7949d437@windsurf> (raw)
In-Reply-To: <20211003124027.343390-1-romain.naour@gmail.com>
Hello Romain,
On Sun, 3 Oct 2021 14:40:23 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> We are going to remove the gcc fork for csky since it doesn't build
> with the latest compilers (gcc 8, 10, 11 tested) [1].
>
> Removing theses defconfigs and the csky gcc fork has become unavoidable
> since the Buildroot Docker image used by the gitlab CI will switch soon
> to Debian bullseye soon [2].
>
> The cksy gcc fork based on gcc 6 has not been updated since it has been
> added to Buildroot [3]. Since then, csky has been added to binutils and
> gcc but using the latest upstream version (binutils 2.37 and gcc 11) is
> not yet possible due to build issue with glibc 2.34 [4].
>
> Moreover, qemu_csky defconfigs was to be used with the csky qemu fork
> (based on Qemu 3.x) added by commit [5] and removed by commit [6].
> Since then it's not possible to do a runtime test with theses
> defconfigs.
>
> Theses defconfigs can be added back later if the csky toolchain support
> is fixed and csky supported by upstream Qemu.
>
> [1] http://lists.busybox.net/pipermail/buildroot/2021-August/621504.html
> [2] 71b83227128be62c169313e85bb8f339f977ad67
> [3] 7873a5bd5ebbeb1674293dae6b06b50f0a1f2184
> [4] http://lists.busybox.net/pipermail/buildroot/2021-October/624596.html
> [5] f816e5b276f1ef15840bec6667f1e8219717ab7d
> [6] 58af9a70cc0f195116dedb3fd0e2ca5b4fec9e70
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Guo Ren <ren_guo@c-sky.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
I agree with the patch series. What I propose is to wait maybe 4-5 days
to see if there is a reaction or some feedback from Guo Ren. And if
there's no feedback, we apply in 4-5 days.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-03 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 12:40 [Buildroot] [PATCH 1/5] configs: remove qemu_csky defconfigs Romain Naour
2021-10-03 12:40 ` [Buildroot] [PATCH 2/5] arch/Config.in: disable internal toolchain backend for csky Romain Naour
2021-10-03 12:40 ` [Buildroot] [PATCH 3/5] package/glibc: remove glibc csky fork Romain Naour
2021-10-03 12:40 ` [Buildroot] [PATCH 4/5] package/gcc: remove csky version Romain Naour
2021-10-03 12:40 ` [Buildroot] [PATCH 5/5] package/binutils: " Romain Naour
2021-10-03 14:22 ` Thomas Petazzoni [this message]
2021-10-15 19:51 ` [Buildroot] [PATCH 1/5] configs: remove qemu_csky defconfigs Romain Naour
2021-10-17 17:02 ` Yann E. MORIN
[not found] <20211003123932.343326-1-romain.naour@gmail.com>
[not found] ` <7402CD01-65B9-42B3-B6BF-95F3434B843F@c-sky.com>
2021-10-04 21:40 ` Romain Naour
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=20211003162237.7949d437@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=ren_guo@c-sky.com \
--cc=romain.naour@gmail.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