Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/mtd: integck needs threads
Date: Mon, 14 Aug 2017 21:29:52 +0200	[thread overview]
Message-ID: <20170814212952.69e2033c@windsurf> (raw)
In-Reply-To: <20170814190123.6828-1-bernd.kuhls@t-online.de>

Hello,

On Mon, 14 Aug 2017 21:01:23 +0200, Bernd Kuhls wrote:
> The test programs depend on pthreads:
> http://git.infradead.org/mtd-utils.git/blob/1bfee8660131fca7a18f68e9548a18ca6b3378a0:/configure.ac#l43
> 
> Our option BR2_PACKAGE_MTD_INTEGCK is the only option which enables
> building the test programs so it needs to depend on threads because
> BR2_PACKAGE_MTD_TESTS as a hidden option cannot be selected.

I don't understand this explanation, and actually, I believe it is
wrong, and the thread dependency should be added to
BR2_PACKAGE_MTD_TESTS. Indeed, it's the fact of enabling
BR2_PACKAGE_MTD_TESTS that passes --enable-tests, which requires thread
support.

The thread dependency should be added to BR2_PACKAGE_MTD_TESTS, so that
is other people add more visible options to enable other tests in the
future, they will notice this dependency.

Of course, this thread dependency should then be propagated to all
existing reverse dependencies of BR2_PACKAGE_MTD_TESTS, which means
doing exactly your patch.

So basically, your patch + a "depends on BR2_TOOLCHAIN_HAS_THREADS" on
BR2_PACKAGE_MTD_TESTS and a reworked commit log would be good.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-08-14 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 19:01 [Buildroot] [PATCH v2 1/1] package/mtd: integck needs threads Bernd Kuhls
2017-08-14 19:29 ` Thomas Petazzoni [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=20170814212952.69e2033c@windsurf \
    --to=thomas.petazzoni@free-electrons.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