From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] gst1-plugins-bad: fix build against openjpeg 2.2
Date: Fri, 8 Sep 2017 15:31:18 +0200 [thread overview]
Message-ID: <20170908153118.19f46256@gmx.net> (raw)
In-Reply-To: <20170908085622.57eddaa9@windsurf.lan>
Hello Thomas,
On Fri, 8 Sep 2017 08:56:22 +0200, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Thu, 7 Sep 2017 23:16:28 +0200, Peter Seiderer wrote:
> > diff --git a/package/gstreamer1/gst1-plugins-bad/0002-Bump-gettext-version-to-0.19.patch b/package/gstreamer1/gst1-plugins-bad/0002-Bump-gettext-version-to-0.19.patch
> > new file mode 100644
> > index 0000000000..ccac1f1073
> > --- /dev/null
> > +++ b/package/gstreamer1/gst1-plugins-bad/0002-Bump-gettext-version-to-0.19.patch
> > @@ -0,0 +1,46 @@
> > +From 750da2a0dbaaefa4e702bf7ede16917b57b7efa8 Mon Sep 17 00:00:00 2001
> > +From: Peter Seiderer <ps.report@gmx.net>
> > +Date: Thu, 7 Sep 2017 23:01:44 +0200
> > +Subject: [PATCH] Bump gettext version to 0.19
> > +
> > +Fixes autoreconf failure:
> > +
> > + *** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.17 but the autoconf macros are from gettext version 0.19
> > +
> > +Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> I think the normal fix for this is to add <pkg>_GETTEXTIZE = YES in the
> package.
Thanks for the tip (did not know about it yet)...new patch version follows...
Regards,
Peter
>
> Thomas
prev parent reply other threads:[~2017-09-08 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 21:16 [Buildroot] [PATCH v2] gst1-plugins-bad: fix build against openjpeg 2.2 Peter Seiderer
2017-09-08 6:56 ` Thomas Petazzoni
2017-09-08 13:31 ` Peter Seiderer [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=20170908153118.19f46256@gmx.net \
--to=ps.report@gmx.net \
--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