All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] configs/qemu_riscv32_virt: Update to 5.1 kernel
Date: Thu, 20 Jun 2019 21:02:15 +0200	[thread overview]
Message-ID: <20190620210215.08baafe7@windsurf> (raw)
In-Reply-To: <CAKmqyKPecJMDpJu+R8cZ7jEc_UbOeMvJszViZ=siVJV_HVUY+A@mail.gmail.com>

On Thu, 20 Jun 2019 11:26:06 -0700
Alistair Francis <alistair23@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:

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

  reply	other threads:[~2019-06-20 19:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 16:54 [Buildroot] [PATCH v2 1/2] configs/qemu_riscv64_virt: Update to 5.1 kernel Alistair Francis
2019-06-19 16:54 ` [Buildroot] [PATCH v2 2/2] configs/qemu_riscv32_virt: " Alistair Francis
2019-06-20 13:57   ` Thomas Petazzoni
2019-06-20 17:01     ` Alistair Francis
2019-06-20 17:13       ` Mark Corbin
2019-06-20 17:40         ` Alistair Francis
2019-06-20 17:54           ` Alistair Francis
2019-06-20 18:26             ` Thomas Petazzoni
2019-06-20 18:26               ` Alistair Francis
2019-06-20 19:02                 ` Thomas Petazzoni [this message]
2019-06-20 20:00                   ` Alistair Francis
2019-08-17 16:12                     ` Bin Meng
2019-08-19 20:24                       ` Alistair Francis
2019-06-20 13:50 ` [Buildroot] [PATCH v2 1/2] configs/qemu_riscv64_virt: " 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=20190620210215.08baafe7@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.