From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] POSIX "sched_yield/1-1.c" build failed
Date: Tue, 14 Sep 2010 13:39:39 +0900 [thread overview]
Message-ID: <000401cb53c6$d7a16620$86e43260$@co.jp> (raw)
Hi,
POSIX "open_posix_testsuite/conformance/interfaces/sched_yield/1-1.c"
build failed in RHEL4.8 (x86, x86_64, ia64):
------------
conformance/interfaces/sched_yield/1-1 compile FAILED; SKIPPING In file
included from ../../../conformance/interfaces/sched_yield/1-1.c:35:
../../../include/posixtest.h:14:2: #error "Contains GNU-isms that need
fixing."
../../../conformance/interfaces/sched_yield/1-1.c: In function
`set_thread_affinity':
../../../conformance/interfaces/sched_yield/1-1.c:91: warning: implicit
declaration of function `pthread_setaffinity_np'
------------
This testset seems to test "sched_yield()", and uses "sched_setafinity()"
for CPU fixing.
I tried to remove "_GNU_SOURCE" definition from "sched_yield/1-1.c".
But "sched_setafinity()" needs "_GNU_SOURCE".
"sched_setafinity()" is necessary for this testset, and I considered the
substitution for "sched_setafinity()".
But I don't have any ideas. There is no function to be substitute for
"sched_setafinity()" by POSIX conformity, I think.
Regards--
-Tomonori Mitani
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-09-14 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 4:39 Mitani [this message]
2010-09-15 13:43 ` [LTP] POSIX "sched_yield/1-1.c" build failed Hannu Heikkinen
2010-09-15 16:18 ` Garrett Cooper
2010-09-15 18:20 ` Hannu Heikkinen
2010-09-15 19:01 ` Garrett Cooper
2010-09-16 19:00 ` Hannu Heikkinen
2010-09-16 19:12 ` Garrett Cooper
2010-09-17 16:47 ` Hannu Heikkinen
2010-09-21 4:39 ` Mitani
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='000401cb53c6$d7a16620$86e43260$@co.jp' \
--to=mitani@ryobi.co.jp \
--cc=ltp-list@lists.sourceforge.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