From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] zbar: bump version to 0.22
Date: Sat, 9 Mar 2019 14:24:12 +0100 [thread overview]
Message-ID: <20190309142412.19af2ef5@windsurf> (raw)
In-Reply-To: <20190308221947.18548-1-ps.report@gmx.net>
Hello Peter,
On Fri, 8 Mar 2019 23:19:47 +0100
Peter Seiderer <ps.report@gmx.net> wrote:
> - change from git download to official release and
> download site (drop need for autoreconf)
>
> - drop dependency on kernel headers >= 3.17 (should be fixed with
> commit 'v4l2: make ZBar build and run on Kernels < 3.16' (see [1]),
> propagate removal to gst-plugins-bad
>
> [1] https://git.linuxtv.org/zbar.git/commit/?id=fa5c48127ec1e3670e28540c2e6a03431ebac5b8
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
I didn't pay attention, but in fact this is still not correct.
zbar selects libv4l, and libv4l has a dependency on headers >= 3.0. So
zbar should keep a dependency on >= 3.0, and so should the
gst-plugins-bad zbar option. Otherwise, you can enable zbar on < 3.0
headers, but libv4l is not selectable, violating the kconfig
correctness of the configuration.
Conclusion: we need a headers >= 3.0 dependency on zbar and the
gst-plugins-bad zbar option.
Could you fix this and resend ?
Thanks a lot!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-09 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 22:19 [Buildroot] [PATCH v3] zbar: bump version to 0.22 Peter Seiderer
2019-03-09 13:24 ` Thomas Petazzoni [this message]
2019-03-09 20:38 ` Peter Seiderer
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=20190309142412.19af2ef5@windsurf \
--to=thomas.petazzoni@bootlin.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