From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] exiv2: add patch to fix build error with some toolchains
Date: Sat, 6 Dec 2014 13:47:59 +0100 [thread overview]
Message-ID: <20141206134759.1aae7a50@free-electrons.com> (raw)
In-Reply-To: <1417688294-3397-1-git-send-email-nicolas.serafini@sensefly.com>
Dear Nicolas Serafini,
On Thu, 4 Dec 2014 11:18:14 +0100, Nicolas Serafini wrote:
> This patch remove a header inclusion that is not required an can create
> build error with some toolchains.
> The patch is pushed on the upstream for the next release.
> http://dev.exiv2.org/issues/1007
>
> Fixes:
> http://autobuild.buildroot.net/results/09d/09d9b525eeee458247e10a7948070c00bbabb964/
>
> Signed-off-by: Nicolas Serafini <nicolas.serafini@sensefly.com>
> ---
> package/exiv2/exiv2-0001-remove-useless-header.patch | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 package/exiv2/exiv2-0001-remove-useless-header.patch
Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
I tested that it indeed fixes the Blackfin build failure mentioned in
the commit log. The only minor detail is that the patch is not named
correctly, it should be named 0001-remove-useless-header.patch, and not
exiv2-0001-remove-useless-header.patch, but this can be fixed when
applying Nicolas patch.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-06 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 10:18 [Buildroot] [PATCH] exiv2: add patch to fix build error with some toolchains Nicolas Serafini
2014-12-06 12:47 ` Thomas Petazzoni [this message]
2014-12-07 21:10 ` 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=20141206134759.1aae7a50@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