Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15676] New: OpenSBI additional build variables doesn't work.
Date: Mon, 03 Jul 2023 06:14:57 +0000	[thread overview]
Message-ID: <bug-15676-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 15676
           Summary: OpenSBI additional build variables doesn't work.
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: 1151727370@qq.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

When I build the firmware of OpenSBI's generic platform, I need to specify
OpenSBI's custom FW_TEXT_START, so I specified the custom value of
FW_TEXT_START in Buildroot's BR2_TARGET_OPENSBI_ADDITIONAL_VARIABLES
configuration. Unfortunately, it didn't work, and the generated firmware still
used the default FW_TEXT_START value. I guess this may have something to do
with OPENSBI_MAKE_ENV being placed before the Make command, I hope someone can
check and fix this problem, thanks.

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

             reply	other threads:[~2023-07-03  6:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  6:14 bugzilla [this message]
2024-04-25 20:44 ` [Buildroot] [Bug 15676] OpenSBI additional build variables doesn't work bugzilla
2024-04-25 21:16 ` bugzilla
2024-06-15 15:11 ` 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-15676-163@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