From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] support/libtool: add patch for newer versions
Date: Sun, 21 Dec 2014 16:12:18 +0100 [thread overview]
Message-ID: <20141221161218.017f5f7e@free-electrons.com> (raw)
In-Reply-To: <1418738900-16150-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Tue, 16 Dec 2014 11:08:15 -0300, Gustavo Zacarias wrote:
> Add patch to support newer (>2.4.2) versions.
> Adjust patch logic to check for patchlevel greater than 2 (apply new patch) or
> not (apply current patch).
> Some people/distributions used unreleased versions, with the string being
> 2.4.2.x, this packages are AUTORECONFed and have to be kept like this since
> the up-to-2.4.2 patch doesn't work, neither does the from-2.4.3 version patch.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/pkg-autotools.mk | 8 ++-
> support/libtool/buildroot-libtool-v2.4.4.patch | 95 ++++++++++++++++++++++++++
> 2 files changed, 102 insertions(+), 1 deletion(-)
> create mode 100644 support/libtool/buildroot-libtool-v2.4.4.patch
Entire series applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-12-21 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 14:08 [Buildroot] [PATCH 1/6] support/libtool: add patch for newer versions Gustavo Zacarias
2014-12-16 14:08 ` [Buildroot] [PATCH 2/6] libtool: bump to version 2.4.4 Gustavo Zacarias
2014-12-16 14:08 ` [Buildroot] [PATCH 3/6] subversion: security bump to version 1.7.19 Gustavo Zacarias
2014-12-16 14:08 ` [Buildroot] [PATCH 4/6] lzo: adjust libtool comment Gustavo Zacarias
2014-12-16 14:08 ` [Buildroot] [PATCH 5/6] libfribidi: " Gustavo Zacarias
2014-12-16 14:08 ` [Buildroot] [PATCH 6/6] sudo: " Gustavo Zacarias
2014-12-21 15:12 ` Thomas Petazzoni [this message]
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=20141221161218.017f5f7e@free-electrons.com \
--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