From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] valgrind: bump to version 3.9.0
Date: Sat, 04 Jan 2014 23:40:48 +0100 [thread overview]
Message-ID: <87fvp374lr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1388680480-58533-1-git-send-email-jezz@sysmic.org> ("Jérôme Pouiller"'s message of "Thu, 2 Jan 2014 17:34:40 +0100")
>>>>> "J?r?me" == J?r?me Pouiller <jezz@sysmic.org> writes:
> Drop some patches:
> - glibc 2.17 and 2.18 are now supported by upstream
> - coregrind/link_tool_exe_linux.in has been reworked and should now
> support ccache
> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
> ---
> v2:
> Fix subject of patch
> Use -M option of git-send-email for better reviewing.
> +++ b/package/valgrind/valgrind.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
> -VALGRIND_VERSION = 3.8.1
> +VALGRIND_VERSION = 3.9.0
> VALGRIND_SITE = http://valgrind.org/downloads/
> VALGRIND_SOURCE = valgrind-$(VALGRIND_VERSION).tar.bz2
> VALGRIND_LICENSE = GPLv2 GFDLv1.2
We can also drop AUTORECONF as we're no longer patching configure.in.
Committed with that fixed, thanks.
> --
> 1.8.3.2
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-01-04 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 16:34 [Buildroot] [PATCH v2] valgrind: bump to version 3.9.0 Jérôme Pouiller
2014-01-04 22:40 ` Peter Korsgaard [this message]
2014-01-28 17:39 ` Thomas Petazzoni
2014-01-29 9:44 ` Markos Chandras
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=87fvp374lr.fsf@dell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.