From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help]
Date: Tue, 15 Jun 2010 09:37:36 +0200 [thread overview]
Message-ID: <20100615093736.1872e8e7@surf> (raw)
In-Reply-To: <4C1726CE.8080009@terawatt.fr>
Hello Damien,
On Tue, 15 Jun 2010 09:07:58 +0200
Damien Borie <dbe@terawatt.fr> wrote:
> So, I tried to compile Valgrind version 3.5.0. I only change the version
> number in Config.in file (in package/valgrind/). 'make source' cause the
> package download without problems. Then 'make' doesn't cause error but
> it try to apply a patch ('valgrind-largefile patch'). This patch modify
> a file 'coregrind/m_ume.c' and ask me to type a path to a file to patch,
> with no others precisions.
It means that the file the patch is modifying doesn't exist anymore in
newer versions of Valgrind. So you need to see whether the patch is
still needed or not. From a quick look, it looks like it does.
Attached is a updated version of the patch for Valgrind 3.5.0. I haven't
tested it *at all*, I haven't even built Valgrind with this patch. But
at least, it applies on Valgrind 3.5.0.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: valgrind-3.5.0-largefile.patch
Type: text/x-patch
Size: 2435 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100615/aa15e560/attachment.bin>
next prev parent reply other threads:[~2010-06-15 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 7:07 [Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help] Damien Borie
2010-06-15 7:37 ` Thomas Petazzoni [this message]
2010-06-15 9:58 ` Damien Borie
2010-06-15 11:15 ` Damien Borie
2010-06-15 12:26 ` Damien Borie
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=20100615093736.1872e8e7@surf \
--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