Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15291] New: BR2_PACKAGE_GNU_EFI_ARCH_SUPPORTS without location
Date: Thu, 26 Jan 2023 05:40:24 +0000	[thread overview]
Message-ID: <bug-15291-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 15291
             Build: Ubuntu 22 X86_64
           Summary: BR2_PACKAGE_GNU_EFI_ARCH_SUPPORTS without location
           Product: buildroot
           Version: 2022.11
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: glscene2010@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Created attachment 9496
  --> https://bugs.busybox.net/attachment.cgi?id=9496&action=edit
try to find BR2_PACKAGE_GNU_EFI_ARCH_SUPPORTS in buildroot

In my example pc_x86_bios_defconfig
https://bugs.busybox.net/show_bug.cgi?id=15246#c5 I have option
BR2_PACKAGE_GNU_EFI_ARCH_SUPPORTS=y

I try to find Location of this option, but nothing. 
But for all others options (such as BR2_PACKAGE_GNU_EFI) I can find Location.
Is it a bug?

-- 
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-01-26  5:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26  5:40 bugzilla [this message]
2023-01-28 20:31 ` [Buildroot] [Bug 15291] BR2_PACKAGE_GNU_EFI_ARCH_SUPPORTS without location 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-15291-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