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: Sat, 10 Dec 2016 04:19:01 +0000 [thread overview]
Message-ID: <bug-8946-163-dTGd2UDJJY@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8946-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8946
Brandon Maier <brandon.maier@rockwellcollins.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |---
Status|RESOLVED |REOPENED
--- Comment #8 from Brandon Maier <brandon.maier@rockwellcollins.com> ---
We just ran into this same build error on one of our boards.
I was able to recreate the error on master
(f30eec41f95ed99909eb2c7590d83c12b9142df2) by building the beaglebone_defconfig
with BR2_TOOLCHAIN_BUILDROOT_USE_SSP=y and BR2_SSP_ALL=y. Then doing "make
valgrind".
The cause is Valgrind requires -fno-stack-protector to build correctly. I fixed
the error by appending -fno-stack-protector to the CFLAGS passed to Valgrind,
so that it overrides the ones in TARGET_CFLAGS.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-12-10 4:19 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
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 [this message]
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-dTGd2UDJJY@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 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.