Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Status of valgrind on powerpc
Date: Mon, 07 Nov 2011 23:22:28 +0100	[thread overview]
Message-ID: <87y5vrd13v.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LVTAU73avFA3BJXEvcbVoQj6er1PFg-ntjLo9F3tc6hOA@mail.gmail.com> (Thomas De Schampheleire's message of "Thu, 3 Nov 2011 10:27:58 +0100")

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> writes:

Hi,

 Thomas> Possible solutions?
 Thomas> 1. Modify uClibc so that it does not depend on the linux a.out.h file,
 Thomas> but rather provides its own definitions as eglibc does.
 Thomas> 2. Modify the kernel so that powerpc also provides a.out.h

I looked into this a few years ago, and option 2 is not an option as the
aout stuff is old and shouldn't be used:

https://lkml.org/lkml/2008/6/15/126

 Thomas> 3. Modify buildroot to state that valgrind can not be build with uClibc.

4. Fix valgrind to not include a.out.h

It's not really used for much - Have you seen this thread?

http://old.nabble.com/How-to-disable-the-a.out-support-of-valgrind-td29226733.html

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-11-07 22:22 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
2011-10-03 18:21         ` Thomas De Schampheleire
2011-11-03  9:27           ` Thomas De Schampheleire
2011-11-07 22:22             ` Peter Korsgaard [this message]
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=87y5vrd13v.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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