From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8946] Valgrind fails to build with stack protection turned on
Date: Thu, 19 May 2016 09:22:48 +0000 [thread overview]
Message-ID: <bug-8946-163-EDg41YClmM@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8946-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8946
--- Comment #4 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Jiri, are you sure your last comment is related to this bug? I don't think it
is.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-05-19 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 23:55 [Buildroot] [Bug 8946] New: Valgrind fails to build with stack protection turned on bugzilla at busybox.net
2016-05-19 8:06 ` [Buildroot] [Bug 8946] " bugzilla at busybox.net
2016-05-19 8:23 ` bugzilla at busybox.net
2016-05-19 8:26 ` bugzilla at busybox.net
2016-05-19 9:22 ` bugzilla at busybox.net [this message]
2016-05-19 9:44 ` bugzilla at busybox.net
2016-05-19 17:03 ` bugzilla at busybox.net
2016-09-12 20:20 ` bugzilla at busybox.net
2016-12-10 4:19 ` bugzilla at busybox.net
2017-02-11 14:39 ` 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-8946-163-EDg41YClmM@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