From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] valgrind issues on 2014.11-git buildroot
Date: Thu, 4 Dec 2014 16:56:03 +0100 [thread overview]
Message-ID: <20141204165603.0129b7b3@free-electrons.com> (raw)
In-Reply-To: <CANPyyuOxMHdc_ivhhQecBbJUzpJi5gqtAj_CJVhKWNLh0akwZw@mail.gmail.com>
Dear Mike Williams,
On Thu, 4 Dec 2014 10:40:45 -0500, Mike Williams wrote:
> I would say yes. I'm not certain of it in this case, but I usually
> make clean when changing options like this. See:
> http://buildroot.uclibc.org/downloads/manual/manual.html#full-rebuild
I can confirm you need to do a make clean. Basically, once Buildroot
has stripped binaries in output/target, the only sane way to get back to
unstripped binaries is to do a full clean build.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-12-04 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 6:57 [Buildroot] valgrind issues on 2014.11-git buildroot Rohit Kumar
2014-12-04 13:50 ` Mike Williams
2014-12-04 15:26 ` Rohit Kumar
2014-12-04 15:40 ` Mike Williams
2014-12-04 15:56 ` Thomas Petazzoni [this message]
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=20141204165603.0129b7b3@free-electrons.com \
--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