Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14146] Cannot build for beaglebone black. Build fails with errors
Date: Tue, 15 Mar 2022 19:15:37 +0000	[thread overview]
Message-ID: <bug-14146-163-8zB962RBgM@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 #3 from Andrei Gherghescu <andrei.gherghescu@protonmail.com> ---
Dear Afua,

You should check your GCC version. I get the same error with GCC 10.

It looks that this is due to the kernel version and GCC 10 combination as
reported here: https://lkml.org/lkml/2020/4/1/1206

This was fixed in release 2021.08.1 with the upgrade to 5.10.30-ti-r3 as Adam
Duskett also mentioned. 

You should switch to that release. 

If you need to stick with 4.19 kernel for whatever reason, then you can use
4.19.94-ti-r72, as listed here https://github.com/beagleboard/linux/tags

4.19.94-ti-r72 kernel builds fine with GCC 10. Change to the following line in
your config.

BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call
github,beagleboard,linux,4.19.94-ti-r72)/linux-4.19.94-ti-r72.tar.gz"


Regards,
Andrei

-- 
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

  parent reply	other threads:[~2022-03-15 19:15 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 ` [Buildroot] [Bug 14146] " bugzilla
2022-03-15 19:15 ` bugzilla [this message]
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-8zB962RBgM@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox