From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14146] Cannot build for beaglebone black. Build fails with errors
Date: Tue, 02 Nov 2021 20:32:11 +0000 [thread overview]
Message-ID: <bug-14146-163-A97fszQ23K@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14146-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14146
--- Comment #2 from Adam Duskett <aduskett@gmail.com> ---
Hello;
The kernel version defined for the beaglebone in buildroot 2021.05.1 is quite
old (4.19.79.) I suggest using the latest beaglebone defconfig from 2021.05.1,
or using the following in your config:
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call
github,beagleboard,linux,5.10.30-ti-r3)/linux-5.10.30-ti-r3.tar.gz"
BR2_LINUX_KERNEL_DEFCONFIG="omap2plus"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="am335x-evm am335x-bone am335x-boneblack
am335x-bonegreen am335x-evmsk am335x-boneblue"
BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-02 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 20:25 [Buildroot] [Bug 14146] New: Cannot build for beaglebone black. Build fails with errors bugzilla
2021-11-02 20:32 ` bugzilla [this message]
2022-03-15 19:15 ` [Buildroot] [Bug 14146] " bugzilla
2024-06-15 14:59 ` bugzilla
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=bug-14146-163-A97fszQ23K@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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.