Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] libv4l: add elfutils optional dependency
Date: Sat, 3 Nov 2018 14:18:24 +0100	[thread overview]
Message-ID: <20181103141824.6e47adbc@windsurf> (raw)
In-Reply-To: <20181103122758.10578-3-fontaine.fabrice@gmail.com>

Hello,

On Sat,  3 Nov 2018 13:27:57 +0100, Fabrice Fontaine wrote:
> Bump to version 1.61.1 added an optional dependency to elfutils:
> https://git.linuxtv.org/v4l-utils.git/commit/?id=d6025b0e8c7f57b0f9390f987acc5eed57360d80
> 
> host-clang is also needed to build PBF protocols, see:

PBF -> BPF

> https://git.linuxtv.org/v4l-utils.git/commit/?id=91b37c0d9cb71fc2d5f78cc96aa2ef9f3bba145b

I'm not sure to understand: there are two separate commits upstream,
one that adds the elfutils dependency, one that adds the clang
dependency. Are they both needed to have BPF protocols ? If so, why
were those two dependencies introduced in separate commits upstream ?

> +ifeq ($(BR2_PACKAGE_ELFUTILS),y)
> +# host-clang is needed to build BPF protocols
> +LIBV4L_DEPENDENCIES += elfutils host-clang
> +endif

I think an explicit sub-option would make sense in this case, because
it's not trivial at all to know that you need elfutils. So I would
prefer to have

config BR2_PACKAGE_LIBV4L_KEYTABLE_BPF_PROTOCOLS
	bool "keytable BPF protocols"
	select BR2_PACKAGE_ELFUTILS
        depends on BR2_USE_WCHAR # elfutils
        depends on !BR2_STATIC_LIBS # elfutils
        depends on BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_GLIBC # elfutils

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-11-03 13:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 12:27 [Buildroot] [PATCH 1/4] llvm: fix build of host-llvm Fabrice Fontaine
2018-11-03 12:27 ` [Buildroot] [PATCH 2/4] llvm: enable bpf Fabrice Fontaine
2018-11-03 13:14   ` Thomas Petazzoni
2018-11-03 14:14     ` Fabrice Fontaine
2018-11-03 14:24       ` Valentin Korenblit
2018-11-03 14:45         ` Fabrice Fontaine
2018-11-03 12:27 ` [Buildroot] [PATCH 3/4] libv4l: add elfutils optional dependency Fabrice Fontaine
2018-11-03 13:18   ` Thomas Petazzoni [this message]
2018-11-03 14:06     ` Fabrice Fontaine
2018-11-03 12:27 ` [Buildroot] [PATCH 4/4] scripts/check-bin-arch: fix failure with bpf Fabrice Fontaine
2018-11-03 13:20   ` Thomas Petazzoni
2018-11-03 13:53     ` Fabrice Fontaine
2018-11-03 14:00       ` Thomas Petazzoni
2018-11-03 14:15 ` [Buildroot] [PATCH 1/4] llvm: fix build of host-llvm Romain Naour
2018-11-03 14:35   ` Thomas Petazzoni
2018-11-03 15:11     ` Fabrice Fontaine

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=20181103141824.6e47adbc@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