From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Toolchain issues on multiple architectures
Date: Thu, 24 Sep 2020 11:42:04 +0200 [thread overview]
Message-ID: <20200924114204.7713bdfe@windsurf> (raw)
In-Reply-To: <CAKmqyKN4Ge5YWUtbU-XwBD2JbrJ-jMhSVMZVbE6wOsz+CUM1jA@mail.gmail.com>
Hello Alistair,
On Fri, 11 Sep 2020 09:03:23 -0700
Alistair Francis <alistair23@gmail.com> wrote:
> > BR2_riscv=y
> > BR2_RISCV_32=y
> > BR2_KERNEL_HEADERS_5_4=y
> > BR2_BINUTILS_VERSION_2_34_X=y
> > BR2_GCC_VERSION_10_X=y
> > BR2_TOOLCHAIN_BUILDROOT_CXX=y
> > BR2_TOOLCHAIN_BUILDROOT_FORTRAN=y
> > BR2_INIT_NONE=y
> > BR2_SYSTEM_BIN_SH_NONE=y
> > # BR2_PACKAGE_BUSYBOX is not set
> > BR2_PACKAGE_GDB=y
> > # BR2_TARGET_ROOTFS_TAR is not set
>
> I don't see any errors using this config with buildroot. Do I need to
> do anything else?
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 ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-09-24 9:42 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 [this message]
2020-09-24 18:20 ` Alistair Francis
2020-09-24 18:47 ` Thomas Petazzoni
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=20200924114204.7713bdfe@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.