[Buildroot] [PATCH v2 2/2] configs/qemu_riscv32_virt: Update to 5.1 kernel

[Alistair Francis]

On Sat, Aug 17, 2019 at 9:12 AM Bin Meng <bmeng.cn at gmail.com> wrote:
>
> Hi,
>
> On Fri, Jun 21, 2019 at 4:03 AM Alistair Francis <alistair23 at gmail.com> wrote:
> >
> > On Thu, Jun 20, 2019 at 12:02 PM Thomas Petazzoni
> > <thomas.petazzoni at bootlin.com> wrote:
> > >
> > > On Thu, 20 Jun 2019 11:26:06 -0700
> > > Alistair Francis <alistair23 at gmail.com> 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:
> >
> > Yep, there is no 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.
> >
> > It hasn't been updated, we are using the latest. This is why we need
> > the kernel patch.
> >
>
> The riscv32 glibc build is still failing with current buildroot master
> HEAD. Is there any plan to address this?

I thought I tried this the other day and it worked.

The RV32 glibc submission is ongoing. When it's in a better state I'll
update it here.

Alistair

>
> Regards,
> Bin