From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Toolchain issues on multiple architectures
Date: Thu, 24 Sep 2020 20:47:07 +0200 [thread overview]
Message-ID: <20200924204707.58010cfc@windsurf> (raw)
In-Reply-To: <CAKmqyKMuzcbZ0ZhMdmgYxRnxkLT0z9+-3Vb==sdc2miHKvF7YA@mail.gmail.com>
Hello,
On Thu, 24 Sep 2020 11:20:18 -0700
Alistair Francis <alistair23@gmail.com> wrote:
> > Sorry for the slow feedback. I retested the above defconfig, and it
> > fails to build here. Did you try on the 2020.08 tag, with no change ?
> > Perhaps you tried on master and something fixed this on master after
> > 2020.08 ?
>
> Yep, that doesn't work.
>
> That branch is missing the patches to use upstream glibc:
>
> * acc1330d4a configs/qemu_riscv32_virt: use Linux 5.4 kernel (by
> Alistair Francis 3 weeks ago)
> * a4889545aa package/glibc: use upstream glibc for RISC-V 32-bit (by
> Alistair Francis 3 weeks ago)
>
> Because of that the kernel headers need to be patched to add support
> for a 32-bit time_t.
>
> This change in the defconfig should fix that:
>
> BR2_GLOBAL_PATCH_DIR="board/qemu/riscv32-virt/patches/"
>
> Although it looks like the kernel build is also required to get the
> patches to take effect:
>
> # Kernel
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.1.12"
> BR2_LINUX_KERNEL_DEFCONFIG="rv32"
> BR2_LINUX_KERNEL_IMAGE=y
>
> Although applying the two commits mentioned above would be a much better option.
Thanks a lot for the feedback, it makes sense. To me, it illustrates
very well that the solution of having patches for the kernel headers
that only apply to a specific defconfig doesn't work: whenever someone
builds a system from scratch without using a defconfig, such patches
are not applied.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-24 18:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 10:05 [Buildroot] Toolchain issues on multiple architectures Thomas Petazzoni
2020-09-10 14:43 ` Matthew Weber
2020-09-10 15:43 ` Thomas Petazzoni
2020-09-10 15:43 ` Matthew Weber
2020-09-10 16:55 ` Matthew Weber
2020-09-11 12:43 ` Matthew Weber
2020-09-10 16:39 ` [Buildroot] [arc-buildroot] " Alexey Brodkin
2020-09-11 8:28 ` Thomas Petazzoni
2020-09-11 9:59 ` Alexey Brodkin
2020-09-10 23:17 ` [Buildroot] " Alistair Francis
2020-09-11 7:30 ` Thomas Petazzoni
2020-09-11 16:03 ` Alistair Francis
2020-09-24 9:42 ` Thomas Petazzoni
2020-09-24 18:20 ` Alistair Francis
2020-09-24 18:47 ` Thomas Petazzoni [this message]
2020-09-24 18:47 ` Alistair Francis
2020-09-24 18:28 ` Bernd Kuhls
2020-09-25 9:30 ` 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=20200924204707.58010cfc@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