From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 20 Jun 2019 21:02:15 +0200 Subject: [Buildroot] [PATCH v2 2/2] configs/qemu_riscv32_virt: Update to 5.1 kernel In-Reply-To: References: <20190619165406.19615-1-alistair.francis@wdc.com> <20190619165406.19615-2-alistair.francis@wdc.com> <20190620155715.23c40f26@windsurf> <58cf6eb8-6e90-1a36-1339-ba5a12c51cad@embecosm.com> <20190620202630.133c7d35@windsurf> Message-ID: <20190620210215.08baafe7@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Thu, 20 Jun 2019 11:26:06 -0700 Alistair Francis wrote: > Yep, the problem is that the glibc port isn't upstream so it isn't > stable. The kernel has progressed ahead of the latest glibc upstrem > submission (what we are using in buildroot). To fix this we are > reverting the patch from the kernel. Hopefully in the future we can > update glibc and then remove the patch. For riscv32 we are *not* using upstream glibc: else ifeq ($(BR2_RISCV_32),y) GLIBC_VERSION = 06983fe52cfe8e4779035c27e8cc5d2caab31531 GLIBC_SITE = $(call github,riscv,riscv-glibc,$(GLIBC_VERSION)) so if this glibc fork has been updated to cope with the recent kernel change, I think we should update glibc instead of reverting the patch from the kernel. This would also address my comment that building a riscv32 configuration doesn't work out of the box. Of course, we would have to disallow selecting kernel headers < 5.1 on riscv32, but that's perfectly possible. Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com