From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15658] hifive_unleashed_defconfig: Linker errors in opensbi-0.9
Date: Sun, 25 Jun 2023 12:14:36 +0000 [thread overview]
Message-ID: <bug-15658-163-IwA6nfWSlB@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15658-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15658
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
CC| |yann.morin.1998@free.fr
Status|NEW |RESOLVED
--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Jan-Benedict, All,
You want to get the patch added by 2f7582538fa5 (boot/opensbi: unconditionally
disable SSP) and carry it locally in your global patch dir.
When we bumped opensbi from 0.9 to 1.2, that patch no longer applied to 1.2.
We can't indefinitely carry patches against older versions, so we dropped it.
It is your responsibility when using a custom version (c765ac9c02db is
2023.05-rc2, which already has opensbi 1.2), to provide any necessary patch,
or to use an already patched version.
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
next prev parent reply other threads:[~2023-06-25 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 16:32 [Buildroot] [Bug 15658] New: hifive_unleashed_defconfig: Linker errors in opensbi-0.9 bugzilla
2023-06-25 11:00 ` [Buildroot] [Bug 15658] " bugzilla
2023-06-25 12:14 ` bugzilla [this message]
2023-06-25 18:16 ` bugzilla
2023-06-25 19:19 ` bugzilla
2023-06-26 17:23 ` bugzilla
2023-06-26 19:03 ` bugzilla
2023-06-26 20:23 ` bugzilla
2023-07-05 19:07 ` bugzilla
2023-07-05 19:09 ` bugzilla
2023-07-16 9:09 ` 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-15658-163-IwA6nfWSlB@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