From: Mattia Narducci <mattianarducci1@gmail.com>
To: Kilian Zinnecker <kilian.zinnecker@mail.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [Help] Using an external toolchain
Date: Sat, 11 Jan 2025 23:41:23 +0100 [thread overview]
Message-ID: <2975060.e9J7NaK4W3@localhost> (raw)
In-Reply-To: <6118780.lOV4Wx5bFT@kilian-laptop>
On Sat, 11 Jan 2025 14:32:05 +0100 Kilian Zinnecker wrote:
> Hello,
>
> I'd like to use an external toolchain, to speedup building my images.
> Buildroot supports this and also has a subsection (6.1.2) about this in the
> manual [1]. However, I was not able to straight forward set up using an
> external bootlin toolchain from the manual. I.e., I wanted to set up the
> easiest way, i.e., to use a predefined external toolchain profile. Hence, I
> set:
>
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_LP64D_GLIBC_STABLE=y
>
> However, with only these settings, I get errors, e.g., that the headers are
> not correct (2.6 in opposite to 5.4). Therefore, step by step, I add more
> options:
Hello Kilian,
I just tried building qemu_riscv64_virt_defconfig with the same
toolchain you selected:
diff --git a/configs/qemu_riscv64_virt_defconfig b/configs/qemu_riscv64_virt_defconfig
index d9f715198a..aa7eb55091 100644
--- a/configs/qemu_riscv64_virt_defconfig
+++ b/configs/qemu_riscv64_virt_defconfig
@@ -1,5 +1,6 @@
BR2_riscv=y
-BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_6=y
+BR2_TOOLCHAIN_EXTERNAL=y
+BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_LP64D_GLIBC_STABLE=y
BR2_GLOBAL_PATCH_DIR="board/qemu/patches"
BR2_DOWNLOAD_FORCE_CHECK_HASHES=y
BR2_SYSTEM_DHCP="eth0"
and I can't see any problem.
Maybe you missed BR2_riscv=y, the target architecture for your board,
which the bootlin toolchain for RISCV64 depends on?
Best regards,
Mattia
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-11 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 13:32 [Buildroot] [Help] Using an external toolchain Kilian Zinnecker via buildroot
2025-01-11 22:41 ` Mattia Narducci [this message]
2025-01-11 22:49 ` Kilian Zinnecker via buildroot
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=2975060.e9J7NaK4W3@localhost \
--to=mattianarducci1@gmail.com \
--cc=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
/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