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 20:26:30 +0200 [thread overview]
Message-ID: <20190620202630.133c7d35@windsurf> (raw)
In-Reply-To: <CAKmqyKOA1JxWX0EZ1aBa5AGYBbTpDPXPusUthfR-Y3QXyg4ZzQ@mail.gmail.com>
Hello,
On Thu, 20 Jun 2019 10:54:27 -0700
Alistair Francis <alistair23@gmail.com> wrote:
> > Yep, it's not working for me now either. I think the Linux patch is
> > somehow not being applied. I'll investigate.
>
> The conversion to the BR2_GLOBAL_PATCH_DIR mechanism broke the build.
> I'll send a patch now that fixes it.
Argh, sorry about that :-/
However, if the patch is needed to be able to build the toolchain, then
there is a larger problem: it shouldn't be just this defconfig that has
the patch.
In fact, now that I think of it, I remember doing a rebuild of
toolchains recently, and riscv32 was indeed failing with:
In file included from ../sysdeps/unix/sysv/linux/lowlevellock-futex.h:23:0,
from ../sysdeps/nptl/lowlevellock.h:23,
from ../sysdeps/nptl/libc-lockP.h:33,
from ../sysdeps/nptl/libc-lock.h:184,
from gconv_db.c:26:
gconv_db.c: In function '__gconv_find_transform':
../sysdeps/unix/sysv/linux/riscv/sysdep.h:120:31: error: '__NR_futex' undeclared (first use in this function); did you mean '__futex'?
#define SYS_ify(syscall_name) __NR_##syscall_name
^
../sysdeps/unix/sysv/linux/riscv/sysdep.h:232:38: note: in definition of macro 'internal_syscall4'
register long int __a7 asm ("a7") = number; \
^~~~~~
../sysdeps/unix/sysv/linux/riscv/sysdep.h:151:24: note: in expansion of macro 'SYS_ify'
internal_syscall##nr (SYS_ify (name), err, args)
^~~~~~~
And this should be fixed somehow.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-20 18:26 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 [this message]
2019-06-20 18:26 ` Alistair Francis
2019-06-20 19:02 ` Thomas Petazzoni
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=20190620202630.133c7d35@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox