From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] problem with ccache during valgrind compiling
Date: Sat, 31 Dec 2011 15:04:22 +0100 [thread overview]
Message-ID: <20111231150422.08bc29b7@skate> (raw)
In-Reply-To: <CAAfyv37svSYUTu4bE7236jmyG0=XLA=8Ty-eBrPJ02xqZt9=6g@mail.gmail.com>
Le Sat, 31 Dec 2011 13:12:34 +0100,
Belisko Marek <marek.belisko@gmail.com> a ?crit :
> I apply patch you sent and there is another problem:
Ah, yes, that's a mistake on my side. The patch
valgrind-3.7.0-readstab-fix.patch shouldn't have been part of the
commit. Can you just remove it and retry?
I will send a new updated version soon.
Thanks a lot for your testing!
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-12-31 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 19:09 [Buildroot] problem with ccache during valgrind compiling Belisko Marek
2011-12-22 9:37 ` Diego Iastrubni
2011-12-22 11:31 ` Thomas Petazzoni
2011-12-30 8:06 ` Thomas Petazzoni
2011-12-31 12:12 ` Belisko Marek
2011-12-31 14:04 ` Thomas Petazzoni [this message]
2012-01-01 13:08 ` Belisko Marek
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=20111231150422.08bc29b7@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