Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15793] beaglev_defconfig: Cross binutils/gcc configuration problem?
Date: Sun, 24 Sep 2023 18:17:00 +0000	[thread overview]
Message-ID: <bug-15793-163-NMnOLaf5na@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15793-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15793

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yann.morin.1998@free.fr

--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Jan-Benedict, All,

That second build log is eactly the original one; check the timestamps... :-/

The BeagleV defconfig uses an old opensbi: check if you can update it,
of maybe try to backport upstream 5d53b55aa77ffeefd4012445dfa6ad3535e1ff2c.

Also, it looks like all your reports are from an automated build farm, that
just builds all the defconfigs. We already do that once a week on our
gitlab.com repository. So, your reports are most probably duplicates of
the results we get once a week, e.g.:

   
https://lore.kernel.org/buildroot/20230909062958.AE75B40A50@smtp2.osuosl.org/

If you look toward the end, you'll see the list of defconfigs that indeed
do not build.

Regards,
Yann E. MORIN.

-- 
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:[~2023-09-24 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 22:36 [Buildroot] [Bug 15793] New: beaglev_defconfig: Cross binutils/gcc configuration problem? bugzilla
2023-09-24 18:00 ` [Buildroot] [Bug 15793] " bugzilla
2023-09-24 18:17 ` bugzilla [this message]
2024-06-15 15:12 ` 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-15793-163-NMnOLaf5na@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