From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] About "realtime" build failure
Date: Fri, 29 Oct 2010 16:35:05 +0900 [thread overview]
Message-ID: <000001cb773b$ce4f9950$6aeecbf0$@co.jp> (raw)
Hi,
I applied patches which are the effort of various people.
And I could overcome configuration error and keyctl01's build error.
(Thanks!!)
After that, librttest.c build failed:
------------
make[3]: Leaving directory
`/home/LTP/ltp-dev-20101028/testcases/network/xinetd'
make[2]: Leaving directory `/home/LTP/ltp-dev-20101028/testcases/network'
make[2]: Entering directory `/home/LTP/ltp-dev-20101028/testcases/realtime'
make -C lib -f "/home/LTP/ltp-dev-20101028/testcases/realtime/lib/Makefile"
all
make[3]: Entering directory
`/home/LTP/ltp-dev-20101028/testcases/realtime/lib'
gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -D_GNU_SOURCE
-I/home/LTP/ltp-dev-20101028/testcases/realtime/lib/../include
-I../../../include -I../../../include -c -o librttest.o librttest.c
librttest.c: In function `init_pi_mutex':
librttest.c:569: warning: implicit declaration of function
`pthread_mutexattr_setprotocol'
librttest.c:569: error: `PTHREAD_PRIO_INHERIT' undeclared (first use in this
function)
librttest.c:569: error: (Each undeclared identifier is reported only once
librttest.c:569: error: for each function it appears in.)
librttest.c:572: warning: implicit declaration of function
`pthread_mutexattr_getprotocol'
make[3]: *** [librttest.o] Error 1
make[3]: Leaving directory
`/home/LTP/ltp-dev-20101028/testcases/realtime/lib'
make[2]: *** [lib/librealtime.a] Error 2
make[2]: Leaving directory `/home/LTP/ltp-dev-20101028/testcases/realtime'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/LTP/ltp-dev-20101028/testcases'
make: *** [testcases-all] Error 2
------------
"realtime" became to be build by the patch of Makefile:
------------
--- a/testcases/Makefile
+++ b/testcases/Makefile
@@ -38,7 +38,12 @@ FILTER_OUT_DIRS := ballista kdump mce-test
open% pounder21
# XXX (garrcoop): kdump was in this list.
# XXX (garrcoop): open_hpi_testsuite was in this list.
ifeq ($(UCLINUX),1)
-FILTER_OUT_DIRS += DOTS realtime
+FILTER_OUT_DIRS += realtime
+endif
+
+# DOTS requires javac
+ifeq ($(strip $(JAVAC)),)
+FILTER_OUT_DIRS += DOTS
endif
#
------------
"realtime" added to build.
Perhaps this revision caused this failure, I think.
Regards--
-Tomonori Mitani
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-10-29 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Act3O838preomyfuTIOsmPN0ITLHHQ==>
2010-10-29 7:35 ` Mitani [this message]
2010-11-08 21:51 ` [LTP] About "realtime" build failure Garrett Cooper
2010-11-09 1:41 ` Mitani
2010-11-11 6:58 Mitani
2010-11-11 7:57 ` Subrata Modak
2010-11-11 8:42 ` Garrett Cooper
[not found] <4D0672E6.9000100@ams.org>
2010-12-13 19:42 ` [LTP] About \"realtime\" " Garrett Cooper
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='000001cb773b$ce4f9950$6aeecbf0$@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