From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] About POSIX "sched_yield/1-1.c" buld failure
Date: Tue, 26 Oct 2010 10:45:53 +0900 [thread overview]
Message-ID: <000001cb74af$8658b390$930a1ab0$@co.jp> (raw)
Hi,
I reported that build failure of POSIX test set "conformance/interfaces/
sched_yield/1-1" was still left in RHEL4.8 system:
http://www.mail-archive.com/ltp-list@lists.sourceforge.net/msg10713.html
In addition, build of the following tests failed by the reason of
"undefined reference":
------------
conformance/interfaces/pthread_barrierattr_getpshared/1-1
conformance/interfaces/pthread_barrierattr_getpshared/2-1
conformance/interfaces/pthread_barrierattr_init/1-1
conformance/interfaces/pthread_barrierattr_setpshared/1-1
conformance/interfaces/pthread_cond_broadcast/1-2
conformance/interfaces/pthread_cond_broadcast/2-3
conformance/interfaces/pthread_cond_destroy/2-1
conformance/interfaces/pthread_cond_init/1-2
conformance/interfaces/pthread_cond_init/2-2
conformance/interfaces/pthread_cond_init/4-1
conformance/interfaces/pthread_cond_init/4-2
conformance/interfaces/pthread_cond_signal/1-2
conformance/interfaces/pthread_cond_timedwait/2-4
conformance/interfaces/pthread_cond_timedwait/2-5
conformance/interfaces/pthread_cond_timedwait/2-6
conformance/interfaces/pthread_cond_timedwait/2-7
conformance/interfaces/pthread_cond_timedwait/4-2
conformance/interfaces/pthread_cond_wait/2-2
conformance/interfaces/pthread_cond_wait/2-3
conformance/interfaces/pthread_condattr_getclock/1-1
conformance/interfaces/pthread_condattr_getclock/1-2
conformance/interfaces/pthread_condattr_setclock/1-1
conformance/interfaces/pthread_condattr_setclock/1-2
conformance/interfaces/pthread_condattr_setclock/1-3
conformance/interfaces/pthread_condattr_setclock/2-1
conformance/interfaces/pthread_getschedparam/1-3
conformance/interfaces/pthread_mutex_getprioceiling/1-1
conformance/interfaces/pthread_mutexattr_getprioceiling/1-1
conformance/interfaces/pthread_mutexattr_getprioceiling/1-2
conformance/interfaces/pthread_mutexattr_getprioceiling/3-1
conformance/interfaces/pthread_mutexattr_getprotocol/1-1
conformance/interfaces/pthread_mutexattr_getprotocol/1-2
conformance/interfaces/pthread_mutexattr_setprioceiling/1-1
conformance/interfaces/pthread_mutexattr_setprioceiling/3-1
conformance/interfaces/pthread_mutexattr_setprioceiling/3-2
conformance/interfaces/pthread_mutexattr_setprotocol/1-1
conformance/interfaces/pthread_mutexattr_setprotocol/3-1
conformance/interfaces/pthread_mutexattr_setprotocol/3-2
conformance/interfaces/pthread_setschedprio/1-1
conformance/interfaces/sched_yield/1-1
------------
The environment is as follows:
- RHEL4.8 --- (x86, x86_64, ia64)
- kernel --- kernel-2.6.9-89.EL
- glibc --- glibc-2.3.4-2.43
But I found out a method of avoidance of some of these failures.
And I succeeded to build "conformance/interfaces/sched_yield/1-1".
For example, the log of "conformance/interfaces/
pthread_barrierattr_getpshared/1-1" is as follows:
------------
conformance/interfaces/pthread_barrierattr_getpshared/1-1 compile FAILED;
SKIPPING
/tmp/cc8gB5Qj.o(.text+0x3e): In function `main':
: undefined reference to `pthread_barrierattr_getpshared'
collect2: ld returned 1 exit status
------------
I extracted insufficient functions from these logs:
------------
pthread_barrierattr_getpshared
pthread_condattr_getclock
pthread_condattr_setcloc
pthread_condattr_setclock
pthread_mutex_getprioceiling
pthread_mutexattr_getprioceiling
pthread_mutexattr_getprotocol
pthread_mutexattr_setprioceiling
pthread_mutexattr_setprotocol
pthread_setaffinity_np
pthread_setschedprio
------------
In RHEL3.x/RHEL4.x systems, some of these functions were included in
nptl-devel package.
I did the followings:
1. Installed nptl-devel package.
2. Exported LIBRARY_PATH:
export LIBRARY_PATH=/usr/lib/nptl
export LIBRARY_PATH=/usr/lib64/nptl ---(in x86_64)
3. Added "-lpthread" to "conformance/interfaces/lio_listio/LDLIBS" file.
Is the method mentioned above right?
---
postscript:
Now, build of the following tests failed even if I took the method
mentioned above:
------------
conformance/interfaces/pthread_mutex_getprioceiling/1-1
conformance/interfaces/pthread_mutexattr_getprioceiling/1-1
conformance/interfaces/pthread_mutexattr_getprioceiling/1-2
conformance/interfaces/pthread_mutexattr_getprioceiling/3-1
conformance/interfaces/pthread_mutexattr_getprotocol/1-1
conformance/interfaces/pthread_mutexattr_getprotocol/1-2
conformance/interfaces/pthread_mutexattr_setprioceiling/1-1
conformance/interfaces/pthread_mutexattr_setprioceiling/3-1
conformance/interfaces/pthread_mutexattr_setprioceiling/3-2
conformance/interfaces/pthread_mutexattr_setprotocol/1-1
conformance/interfaces/pthread_mutexattr_setprotocol/3-1
conformance/interfaces/pthread_mutexattr_setprotocol/3-2
------------
The insufficient functions are as follows:
------------
pthread_mutex_getprioceiling
pthread_mutexattr_getprotocol
pthread_mutexattr_getprioceiling
pthread_mutexattr_setprioceiling
------------
The man-page of these functions exist, but the definitions don't exist
in header files.
------------
[root@RHEL48-LTP-EM64T ~]# grep -r pthread_mutex_getprioceiling /usr/include
[root@RHEL48-LTP-EM64T ~]# grep -r pthread_mutexattr_getprotocol
/usr/include
[root@RHEL48-LTP-EM64T ~]# grep -r pthread_mutexattr_getprioceiling
/usr/include
[root@RHEL48-LTP-EM64T ~]# grep -r pthread_mutexattr_setprioceiling
/usr/include
[root@RHEL48-LTP-EM64T ~]#
------------
And there aren't these functions in libraries.
------------
[root@RHEL48-LTP-EM64T ~]# nm /usr/lib/*.a | grep pthread_mutex
nm: vsnprintf_nonpic.o: no symbols
nm: mt_support.o: no symbols
nm: snprintf.o: no symbols
[...]
nm: strtol.o: no symbols
nm: strtoul.o: no symbols
nm: cmu_compat.o: no symbols
[root@RHEL48-LTP-EM64T ~]# nm /usr/lib64/*.a | grep
pthread_mutexattr_getprotocol
nm: getopt.o: no symbols
nm: getopt1.o: no symbols
nm: aesopt.o: no symbols
[...]
nm: strtol.o: no symbols
nm: strtoul.o: no symbols
nm: cmu_compat.o: no symbols
[root@RHEL48-LTP-EM64T ~]# nm /usr/lib64/nptl/*.a | grep
pthread_mutex_getprioceiling
nm: old_atexit.o: no symbols
nm: strtoll.o: no symbols
nm: strtoull.o: no symbols
[...]
nm: ptw-pwrite64.o: no symbols
nm: pthread_kill_other_threads.o: no symbols
nm: shm_unlink.o: no symbols
------------
I think that I have to investigate about these a little more.
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-26 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 1:45 Mitani [this message]
2010-10-26 6:56 ` [LTP] About POSIX "sched_yield/1-1.c" buld failure Garrett Cooper
2010-10-28 2:44 ` Mitani
2010-11-02 6:42 ` Garrett Cooper
2010-11-05 12:56 ` Mitani
2010-11-08 21:27 ` Garrett Cooper
2010-11-09 10:54 ` 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='000001cb74af$8658b390$930a1ab0$@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