public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12836] New: libunwind: package does not show up in menuconfig for aarch64 target
Date: Sat, 02 May 2020 17:58:47 +0000	[thread overview]
Message-ID: <bug-12836-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 12836
           Summary: libunwind: package does not show up in menuconfig for
                    aarch64 target
           Product: buildroot
           Version: 2020.02.1
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: seems.deviant at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

The libunwind won't show up in menuconfig for aarch64 target because of an
unmet BR2_PACKAGE_LIBUNWIND_ARCH_SUPPORTS dependency.

This is strange, because:

  - the official https://github.com/libunwind/libunwind claims that aarch64
linux is fully supported
  - the minimal handcrafted config featuring libunwind works fine. 

The minimal config that I've tested was:

BR2_aarch64=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_PACKAGE_LIBUNWIND=y


This occurs on "e30eaeb10e package/qemu: disable curl for the host variant"

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-05-02 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 17:58 bugzilla at busybox.net [this message]
2020-05-02 21:40 ` [Buildroot] [Bug 12836] libunwind: package does not show up in menuconfig for aarch64 target bugzilla at busybox.net
2020-05-16 13:43 ` bugzilla at busybox.net

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-12836-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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