From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8946] New: Valgrind fails to build with stack protection turned on
Date: Wed, 18 May 2016 23:55:04 +0000 [thread overview]
Message-ID: <bug-8946-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8946
Bug ID: 8946
Host: ARM
Target: IMX6
Build: Ubuntu 16.04
Summary: Valgrind fails to build with stack protection turned
on
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: nnabavian at sonendo.com
CC: buildroot at uclibc.org
Target Milestone: ---
arm-none-linux-gnueabi-gcc -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -Os -fstack-protector -o memcheck-arm-linux -O2 -g
-std=gnu99 -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith
-Wstrict-prototypes -Wmissing-declarations -Wcast-qual -Wwrite-strings
-Wempty-body -Wformat -Wformat-security -Wignored-qualifiers
-Wmissing-parameter-type -Wold-style-declaration -fno-stack-protector
-fno-strict-aliasing -fno-builtin -marm -mcpu=cortex-a8 -O2 -static
-nodefaultlibs -nostartfiles -u _start memcheck_arm_linux-mc_leakcheck.o
memcheck_arm_linux-mc_malloc_wrappers.o memcheck_arm_linux-mc_main.o
memcheck_arm_linux-mc_translate.o memcheck_arm_linux-mc_machine.o
memcheck_arm_linux-mc_errors.o ../coregrind/libcoregrind-arm-linux.a
../VEX/libvex-arm-linux.a -lgcc
mkdir -p ../.in_place; \
for f in ; do \
rm -f ../.in_place/$f.dSYM; \
ln -f -s ../memcheck/$f.dSYM ../.in_place; \
done
memcheck_arm_linux-mc_main.o: In function `mc_post_reg_write':
/projects/nitrogen6x/buildroot-2016.05-rc1/output/build/valgrind-3.11.0/memcheck/mc_main.c:4165:
undefined reference to `__stack_chk_fail'
and many more of the same
/projects/nitrogen6x/buildroot-2016.05-rc1/output/build/valgrind-3.11.0/VEX/priv/main_util.c:493:
undefined reference to `__stack_chk_guard'
collect2: error: ld returned 1 exit status
Makefile:1014: recipe for target 'memcheck-arm-linux' failed
make[5]: *** [memcheck-arm-linux] Error 1
Makefile:1290: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
Makefile:825: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
Makefile:694: recipe for target 'all' failed
make[2]: *** [all] Error 2
package/pkg-generic.mk:195: recipe for target
'/projects/nitrogen6x/buildroot-2016.05-rc1/output/build/valgrind-3.11.0/.stamp_built'
failed
make[1]: ***
[/projects/nitrogen6x/buildroot-2016.05-rc1/output/build/valgrind-3.11.0/.stamp_built]
Error 2
Makefile:36: recipe for target '_all' failed
make: *** [_all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-05-18 23:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 23:55 bugzilla at busybox.net [this message]
2016-05-19 8:06 ` [Buildroot] [Bug 8946] Valgrind fails to build with stack protection turned on 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
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@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.