Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] valgrind: bump to 3.7.0 and fix build with ccache
Date: Mon, 02 Jan 2012 15:09:07 +0100	[thread overview]
Message-ID: <87d3b22o3g.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <6d753f5cb4dcbda5715d538bf956f72ec82bbcf5.1325340331.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sat, 31 Dec 2011 15:07:08 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> After bumping to 3.7.0, the
 Thomas> valgrind-3.6.1-configure-support-linux-3.patch is no longer
 Thomas> necessary since it was added upstream. The
 Thomas> valgrind-3.7.0-compiler-check.patch patch is added to fix a
 Thomas> compiler version check issue (patch taken from the upstream
 Thomas> Subversion repository). The
 Thomas> valgrind-3.7.0-fix-ccache-support.patch is added to fix the
 Thomas> build process when ccache is used.

Committed, thanks.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2012-01-02 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 14:07 [Buildroot] [pull request v3] Pull request for branch for-2012.02/valgrind-bump Thomas Petazzoni
2011-12-31 14:07 ` [Buildroot] [PATCH 1/1] valgrind: bump to 3.7.0 and fix build with ccache Thomas Petazzoni
2012-01-01 13:35   ` Thomas Petazzoni
2012-01-02 14:09   ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-29 21:29 [Buildroot] [pull request v2] Pull request for branch for-2012.02/valgrind-bump Thomas Petazzoni
2011-12-29 21:29 ` [Buildroot] [PATCH 1/1] valgrind: bump to 3.7.0 and fix build with ccache Thomas Petazzoni

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=87d3b22o3g.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