From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] iozone: disable for uClibc 0.9.31
Date: Mon, 11 Nov 2013 12:01:50 +0200 [thread overview]
Message-ID: <20131111100150.GN4581@tarshish> (raw)
In-Reply-To: <87siv36z7u.fsf@dell.be.48ers.dk>
Hi Peter, Simon,
On Mon, Nov 11, 2013 at 10:53:57AM +0100, Peter Korsgaard wrote:
> >>>>> "spdawson" == spdawson <spdawson@gmail.com> writes:
>
> > From: Simon Dawson <spdawson@gmail.com>
> > uClibc 0.9.31.x does not include the pthread_setaffinity_np GNU extension.
>
> > Fixes build failures such as the following.
>
> > http://autobuild.buildroot.net/results/e21526c0c18733310d3fb322d79d5fff3a71af51/
>
> > Signed-off-by: Simon Dawson <spdawson@gmail.com>
> > ---
> > package/iozone/Config.in | 1 +
> > 1 file changed, 1 insertion(+)
>
> > diff --git a/package/iozone/Config.in b/package/iozone/Config.in
> > index 26d4daa..33e12ca 100644
> > --- a/package/iozone/Config.in
> > +++ b/package/iozone/Config.in
> > @@ -1,6 +1,7 @@
> > config BR2_PACKAGE_IOZONE
> > bool "iozone"
> > depends on BR2_USE_MMU # fork()
> > + depends on !BR2_UCLIBC_VERSION_0_9_31 # no pthread_setaffinity_np
>
> Committed, thanks. It sounds like it also needs to depend on
> BR2_TOOLCHAIN_HAS_THREADS. Care to send a patch adding that dependency
> and a comment line?
It also depends on BR2_PTHREADS_NATIVE. linuxthreads doesn't have
pthread_setaffinity_np.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2013-11-11 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 9:49 [Buildroot] [PATCH] iozone: disable for uClibc 0.9.31 spdawson at gmail.com
2013-11-11 9:53 ` Peter Korsgaard
2013-11-11 9:55 ` Simon Dawson
2013-11-11 10:01 ` Baruch Siach [this message]
2013-11-11 10:06 ` Simon Dawson
2013-11-11 10:23 ` Thomas Petazzoni
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=20131111100150.GN4581@tarshish \
--to=baruch@tkos.co.il \
--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