From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] iozone: depends on threads
Date: Mon, 11 Nov 2013 11:44:28 +0100 [thread overview]
Message-ID: <20131111114428.27ab2ac0@skate> (raw)
In-Reply-To: <1384165234-18705-1-git-send-email-spdawson@gmail.com>
Dear spdawson at gmail.com,
On Mon, 11 Nov 2013 10:20:34 +0000, spdawson at gmail.com wrote:
> From: Simon Dawson <spdawson@gmail.com>
>
> Signed-off-by: Simon Dawson <spdawson@gmail.com>
> ---
> package/iozone/Config.in | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/package/iozone/Config.in b/package/iozone/Config.in
> index 33e12ca..6638b7c 100644
> --- a/package/iozone/Config.in
> +++ b/package/iozone/Config.in
> @@ -2,8 +2,14 @@ config BR2_PACKAGE_IOZONE
> bool "iozone"
> depends on BR2_USE_MMU # fork()
> depends on !BR2_UCLIBC_VERSION_0_9_31 # no pthread_setaffinity_np
> + depends on BR2_PTHREADS_NATIVE || BR2_TOOLCHAIN_BUILDROOT_EGLIBC || BR2_TOOLCHAIN_BUILDROOT_GLIBC
> help
> IOzone is a filesystem benchmark tool.
> The benchmark generates and measures a variety of file operations
>
> http://www.iozone.org/
> +
> +comment "iozone needs a toolchain w/ threads"
> + depends on BR2_USE_MMU
> + depends on !BR2_UCLIBC_VERSION_0_9_31
> + depends on !(BR2_PTHREADS_NATIVE || BR2_TOOLCHAIN_BUILDROOT_EGLIBC || BR2_TOOLCHAIN_BUILDROOT_GLIBC)
No, this will make iozone invisible when building with external
toolchains. See my other reply to the e-mail suggesting to add
BR2_THREADS_NATIVE as a dependency.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-11 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 10:20 [Buildroot] [PATCH] iozone: depends on threads spdawson at gmail.com
2013-11-11 10:44 ` Thomas Petazzoni [this message]
2013-11-11 10:50 ` Simon Dawson
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=20131111114428.27ab2ac0@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 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.