public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Hannu Heikkinen <ext-hannu.m.heikkinen@nokia.com>
To: ext Mitani <mitani@ryobi.co.jp>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] POSIX "sched_yield/1-1.c" build failed
Date: Wed, 15 Sep 2010 13:43:18 +0000	[thread overview]
Message-ID: <20100915134318.GD24784@hannu-debian.research.nokia.com> (raw)
In-Reply-To: <000401cb53c6$d7a16620$86e43260$@co.jp>

On 14/09/10 06:39 +0200, ext Mitani wrote:
> 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
> 

Hi,

could try this out?

--- include/posixtest.h	2010-09-14 14:05:21.000000000 +0000
+++ fixing/posixtest.h	2010-09-14 19:01:02.000000000 +0000
@@ -11,8 +11,16 @@
  */
 
 #if defined(_GNU_SOURCE)
+#if defined (PTS_GNU_SOURCE_WARNING)
+#warning "Contains GNU-isms that need fixing."
+#else
 #error "Contains GNU-isms that need fixing."
+#endif
+
 #elif defined(_BSD_SOURCE)
+#if defined (PTS_BSD_SOURCE_WARNING)
+#warning "Contains BSD-isms that need fixing."
+#else
 #error "Contains BSD-isms that need fixing."
 #endif


Add to yr source #define PTS_GNU_SOURCE_WARNING 1
and compile, or define in posixtest.h and include that hdr.

br,
Hannu

-- 
Hannu Heikkinen
http://www.nixu.com

------------------------------------------------------------------------------
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

  reply	other threads:[~2010-09-15 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14  4:39 [LTP] POSIX "sched_yield/1-1.c" build failed Mitani
2010-09-15 13:43 ` Hannu Heikkinen [this message]
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=20100915134318.GD24784@hannu-debian.research.nokia.com \
    --to=ext-hannu.m.heikkinen@nokia.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=mitani@ryobi.co.jp \
    /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