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] package/iozone: Build non-threads version if !BR2_PTHREADS_NATIVE
Date: Fri, 12 Jul 2013 10:04:29 +0200	[thread overview]
Message-ID: <20130712100429.7950ace7@skate> (raw)
In-Reply-To: <1373615072-5258-1-git-send-email-mjonker@synopsys.com>

Dear Mischa Jonker,

On Fri, 12 Jul 2013 09:44:32 +0200, Mischa Jonker wrote:

>  # No threading target is non-AIO as well
> -ifeq ($(BR2_TOOLCHAIN_HAS_THREADS),)
> +ifeq ($(BR2_PTHREADS_NATIVE),)
>  IOZONE_TARGET = linux-noth
>  # AIO support not available on uClibc, use the linux (non-aio) target.
>  else ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y)

BR2_PTHREADS_NATIVE is a Config.in option that only makes sense in the
context of the internal toolchain backend. So any usage of it in
package/ is going to not be suitable for external toolchain usage. So
your change, as is, would disable thread support in IOZone for any
external toolchain.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-07-12  8:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  7:44 [Buildroot] [PATCH] package/iozone: Build non-threads version if !BR2_PTHREADS_NATIVE Mischa Jonker
2013-07-12  8:04 ` Thomas Petazzoni [this message]
2013-07-12  8:06   ` Mischa Jonker
2013-07-12  8:14     ` Thomas Petazzoni
2013-07-12  8:27       ` Mischa Jonker
  -- strict thread matches above, loose matches on Subject: below --
2013-07-12  7:42 Mischa Jonker
2013-07-12  7:49 ` Mischa Jonker

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=20130712100429.7950ace7@skate \
    --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