From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RESEND PATCH v3 1/1] package/iputils: add configs to select which binaries are built
Date: Sun, 15 Sep 2019 14:23:13 +0200 [thread overview]
Message-ID: <20190915142313.7abf39df@windsurf.home> (raw)
In-Reply-To: <4e8f64ec-1797-a418-79d7-701380a767db@gmail.com>
Hello Alejandro,
On Sun, 15 Sep 2019 12:05:46 +0200
Alejandro Gonz?lez <alejandro.gonzalez.correo@gmail.com> wrote:
> +config BR2_PACKAGE_IPUTILS_NINFOD
> + bool "ninfod"
> + depends on BR2_TOOLCHAIN_HAS_THREADS # ninfod requires <pthread.h>
> + depends on BR2_PACKAGE_NETTLE || BR2_PACKAGE_LIBGCRYPT || BR2_PACKAGE_OPENSSL || BR2_PACKAGE_LINUX_HEADERS
Do we really want to handle this with depends on ? This is indeed what
is the closest to what the current package does, but when we have
sub-options, we generally use "select" to enable the appropriate
dependencies. In this case, it's not easy to know if there is a
preferred crypto provider though, so perhaps what you did is the best.
However, reviewing your commit, I realized we already have this
dependency on BR2_PACKAGE_LINUX_HEADERS, and this is completely bogus.
BR2_PACKAGE_LINUX_HEADERS is only valid when an internal toolchain is
used. When an external toolchain is used, BR2_PACKAGE_LINUX_HEADERS is
always disabled. So it shouldn't be used in packages. This is something
that should be fixed in iputils. In fact, kernel headers are always
available, as they are provided by the toolchain. So this dependency
doesn't make sense.
Could you investigate how USE_CRYPTO=kernel is working, i.e which
APIs/headers it requires ?
Besides this particular problem, the rest of the patch looks good to me.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-15 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 19:17 [Buildroot] [PATCH v3 1/1] package/iputils: add configs to select which binaries are built Alejandro González
2019-09-15 10:05 ` [Buildroot] [RESEND PATCH " Alejandro González
2019-09-15 12:23 ` Thomas Petazzoni [this message]
2020-09-03 19:49 ` Thomas Petazzoni
2020-09-08 13:33 ` Alejandro
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=20190915142313.7abf39df@windsurf.home \
--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