From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libiscsi: add optional dependency to cunit
Date: Thu, 6 Dec 2018 21:21:31 +0100 [thread overview]
Message-ID: <20181206212131.0e812735@windsurf> (raw)
In-Reply-To: <20181204102500.14168-1-yann.morin.1998@free.fr>
Hello,
On Tue, 4 Dec 2018 11:25:00 +0100, Yann E. MORIN wrote:
> libiscsi uses cunit for its test suite, and autodetexcts its presence.
>
> Usually, we just try to disable tests altogether, but there is no way to
> do so. So, ensure proper ordering.
>
> Note: there is an ac_cv_have_cunit variable, but it is not a true
> ac_cv* cache variable, and the value provided on the command line or
> environment is properly ignored.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
> ---
> Note: for the interesting parties, I've sent a bunch of enhacements to
> the configure script upstream:
> https://github.com/sahlberg/libiscsi/pull/283
> ---
> package/libiscsi/libiscsi.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-06 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 9:31 [Buildroot] [PATCH] package/libiscsi: fix build due to warnings Yann E. MORIN
2018-12-04 9:57 ` [Buildroot] [PATCH] package/libiscsi: do not built the manpages Yann E. MORIN
2018-12-04 10:25 ` [Buildroot] [PATCH] package/libiscsi: add optional dependency to cunit Yann E. MORIN
2018-12-06 20:21 ` Thomas Petazzoni [this message]
2018-12-06 20:21 ` [Buildroot] [PATCH] package/libiscsi: do not built the manpages Thomas Petazzoni
2018-12-16 14:54 ` Peter Korsgaard
2018-12-06 20:21 ` [Buildroot] [PATCH] package/libiscsi: fix build due to warnings Thomas Petazzoni
2018-12-16 14:51 ` Peter Korsgaard
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=20181206212131.0e812735@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.