All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16009] New: 'select' does not work with 'choice'
Date: Wed, 27 Mar 2024 15:55:30 +0000	[thread overview]
Message-ID: <bug-16009-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 16009
           Summary: 'select' does not work with 'choice'
           Product: buildroot
           Version: 2024.02.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: achpile@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

If we have something like this in Config.in

choice
        prompt "TEST"
        config BR2_TEST_1
                bool "1"
        config BR2_TEST_2
                bool "2"
endchoice

config BR2_TEST_BOOL_D1
        bool "Depends on 1"
        depends on BR2_TEST_1

config BR2_TEST_BOOL_S1
        bool "Selects 1"
        select BR2_TEST_1

config BR2_TEST_BOOL_D2
        bool "Depends on 2"
        depends on BR2_TEST_2

config BR2_TEST_BOOL_S2
        bool "Selects 2"
        select BR2_TEST_2


Then selecting BR2_TEST_BOOL_S1 or BR2_TEST_BOOL_S2 does not select BR2_TEST_1
or BR2_TEST_2. I am not sure if it is expected behavior but seems like a bug to
me.

-- 
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:[~2024-03-27 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 15:55 bugzilla [this message]
2024-03-27 21:04 ` [Buildroot] [Bug 16009] 'select' does not work with 'choice' bugzilla
2024-03-28  7:50 ` 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-16009-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.