From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11391] New: Valgind availability on ARM
Date: Thu, 11 Oct 2018 09:55:44 +0000 [thread overview]
Message-ID: <bug-11391-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11391
Bug ID: 11391
Summary: Valgind availability on ARM
Product: buildroot
Version: 2018.02.4
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: jpcartal at free.fr
CC: buildroot at uclibc.org
Target Milestone: ---
Hello,
Valgrind package is not selectable for ARMv8 platform in version 2018.02.4,
which seems normal since the packaged Valgrind version is 3.12.0.
However, in version 2018.05.x the valgrind version has been updated to 3.13.0
and Config.in was modified to add BR2_aarch64, however my understanding is that
Valgrind does also support ARMv8 in 32 bits mode (see
https://bugs.kde.org/show_bug.cgi?id=372185), and in this case it can not be
selected.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-10-11 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 9:55 bugzilla at busybox.net [this message]
2018-10-11 10:00 ` [Buildroot] [Bug 11391] Valgind availability on ARM 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-11391-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