From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Status of valgrind on powerpc
Date: Sat, 1 Oct 2011 11:39:02 +0200 [thread overview]
Message-ID: <20111001113902.2aeff98d@skate> (raw)
In-Reply-To: <CAAXf6LUKtv1Cs-gEfGj4Aq9wLe3N0tiKHDxniv39dW+RwoQOjw@mail.gmail.com>
Le Fri, 30 Sep 2011 23:12:52 +0200,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> An eglibc toolchain built with crosstool-ng, also works (both
> compilation as running on target).
Ok. It would be good to identify whether Valgrind can be built with
uClibc with additional configuration options, or if glibc/eglibc is
really needed. In the former case, additional documentation in the
Config.in help would be good. In the latter case, some additional
"depends on" to hide valgrind when uClibc is used would be nice.
> To run properly, though, valgrind needs an unstripped ld.so
> I worked around this by adding ld.so as an exception to the strip
> command in target-finalize (but am hoping for inclusion of Sven
> Neumann's 'exclude-from-strip' patch)
Ok.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-10-01 9:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 9:50 [Buildroot] Status of valgrind on powerpc Thomas De Schampheleire
2011-09-29 10:15 ` Thomas Petazzoni
2011-09-30 9:39 ` Thomas De Schampheleire
2011-09-30 19:41 ` Thomas Petazzoni
2011-09-30 21:12 ` Thomas De Schampheleire
2011-10-01 9:39 ` Thomas Petazzoni [this message]
2011-10-03 18:21 ` Thomas De Schampheleire
2011-11-03 9:27 ` Thomas De Schampheleire
2011-11-07 22:22 ` Peter Korsgaard
2011-11-08 8:33 ` Thomas De Schampheleire
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=20111001113902.2aeff98d@skate \
--to=thomas.petazzoni@free-electrons.com \
--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