Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Borie <dbe@terawatt.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [Re:  Valgrind compilation, with patch 3.5.0, need help]
Date: Tue, 15 Jun 2010 09:07:58 +0200	[thread overview]
Message-ID: <4C1726CE.8080009@terawatt.fr> (raw)

My architecture is x86.

It's not me that say that Valgrind depends on glibc version, it's the
log...I have only added valgrind in my configuration and launch 'make
source' and 'make'. The package is downloaded without problem but during
compilation, there is a test on glibc version number. I can see it in
'configure.in' file. And it say me that Valgrind need glibc version 2.2
to 2.5. I use 2.9.

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.
So I don't know how to type here. And if I ignore, the compilation end
with an error (saying that I must apply the patch).

Any idea?

Damien Borie

TERAWATT / AENERGIA S.A.S.
ZA DUBOSCOA
64990 Villefranque
FRANCE

tel : +33 (0)5 59 44 26 08
fax : +33 (0)5 59 31 15 11



Thomas Petazzoni a ?crit :
 > On Mon, 14 Jun 2010 17:10:41 +0200
 > Damien Borie <dbe@terawatt.fr> wrote:
 >
 >
 >> I Have to add Valgrind to my distribution to debug my programs. The
 >> version in buildroot doesn't compile because it needs glibc 2.2 -2.5,
 >> and I have 2.9. So I tried with the patch to bump to Valgrind 3.5.0.
 >> But it ask me fro a file to patch, and I don't understand what I must
 >> type to apply correctly the patch and compile Valgrind. In the match
 >> itself, I cannot see indications about this file to choose.
 >>
 >
 > What is your target architecture ? Remember that Valgrind only works on
 > x86, x86_64 and PowerPC 32/64.
 >
 > Moreover, I don't really see how Valgrind in Buildroot would depend on
 > a particular version of glibc. Can you be more specific about what
 > you're doing and the exact result of the commands you're using ?
 >
 > Thomas
 >


-- 
Damien Borie

TERAWATT / AENERGIA S.A.S.
ZA DUBOSCOA
64990 Villefranque
FRANCE 

tel : +33 (0)5 59 44 26 08
fax : +33 (0)5 59 31 15 11 

             reply	other threads:[~2010-06-15  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15  7:07 Damien Borie [this message]
2010-06-15  7:37 ` [Buildroot] [Re: Valgrind compilation, with patch 3.5.0, need help] Thomas Petazzoni
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=4C1726CE.8080009@terawatt.fr \
    --to=dbe@terawatt.fr \
    --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