About POSIX "sched_yield/1-1.c" buld failure

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/[email protected]/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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Some versions of gcc didn't function properly with -lpthread; try
-pthread instead at the top-level LDLIBS file and see whether or not it works for you.
HTH,
-Garrett

------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Hi,

I tried to use "-pthread" instead of "-lpthread".
But "sched_yield/1-1" failed in my all archtectures (RHEL4.8-x86, x86_64, ia64).
Other 27 tests, too.

Thanks--

-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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

What does `man pthread_barrierattr_getpshared' say? -Garrett

------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

"man pthread_barrierattr_getpshared" in my system "RHEL4.8-x86_64".

------------
[root@RHEL48-LTP-EM64T make]# man pthread_barrierattr_getpshared PTHREAD_BARRIERATTR_GETPSHARED(P) PTHREAD_BARRIERATTR_GETPSHARED(P)

NAME
pthread_barrierattr_getpshared, pthread_barrierattr_setpshared - get
and set the
process-shared attribute of the barrier attributes object
(ADVANCED REALTIME
THREADS)

SYNOPSIS

       #include <pthread.h>

       int pthread_barrierattr_getpshared(const pthread_barrierattr_t *
              restrict attr, int *restrict pshared);
       int pthread_barrierattr_setpshared(pthread_barrierattr_t *attr,
              int pshared);

DESCRIPTION
The pthread_barrierattr_getpshared() function shall obtain the value
of the pro-
cess-shared attribute from the attributes object referenced by
attr. The
pthread_barrierattr_setpshared() function shall set the
process-shared attribute
in an initialized attributes object referenced by attr.

The process-shared attribute is set to PTHREAD_PROCESS_SHARED to
permit a bar-
rier to be operated upon by any thread that has access to the
memory where the
barrier is allocated. If the process-shared attribute is
PTHREAD_PROCESS_PRI-
VATE, the barrier shall only be operated upon by threads created
within the same
process as the thread that initialized the barrier; if threads of
different pro-
cesses attempt to operate on such a barrier, the behavior is
undefined. The
default value of the attribute shall be PTHREAD_PROCESS_PRIVATE. Both
constants
PTHREAD_PROCESS_SHARED and PTHREAD_PROCESS_PRIVATE are defined in
<pthread.h>.

Additional attributes, their default values, and the names of the
associated
functions to get and set those attribute values are
implementation-defined.

RETURN VALUE
If successful, the pthread_barrierattr_getpshared() function shall
return zero
and store the value of the process-shared attribute of attr into the
object ref-
erenced by the pshared parameter. Otherwise, an error number shall
be returned
to indicate the error.

If successful, the pthread_barrierattr_setpshared() function shall
return zero;
otherwise, an error number shall be returned to indicate the error.

ERRORS
These functions may fail if:

EINVAL The value specified by attr is invalid.

The pthread_barrierattr_setpshared() function may fail if:

EINVAL The new value specified for the process-shared attribute is
not one of
the legal values PTHREAD_PROCESS_SHARED or
PTHREAD_PROCESS_PRIVATE.

These functions shall not return an error code of [EINTR].

The following sections are informative.

EXAMPLES
None.

APPLICATION USAGE
The pthread_barrierattr_getpshared() and
pthread_barrierattr_setpshared() func-
tions are part of the Barriers option and need not be provided on all
implemen-
tations.

RATIONALE
None.

FUTURE DIRECTIONS
None.

SEE ALSO
pthread_barrier_destroy() , pthread_barrierattr_destroy() ,
pthread_barrier-
attr_init() , the Base Definitions volume of IEEE Std 1003.1-2001,
<pthread.h>

COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form
from IEEE
Std 1003.1, 2003 Edition, Standard for Information Technology --
Portable Oper-
ating System Interface (POSIX), The Open Group Base Specifications
Issue 6,
Copyright (C) 2001-2003 by the Institute of Electrical and
Electronics Engi-
neers, Inc and The Open Group. In the event of any discrepancy
between this ver-
sion and the original IEEE and The Open Group Standard, the
original IEEE and
The Open Group Standard is the referee document. The original
Standard can be
obtained online at http://www.opengroup.org/unix/online.html .

POSIX 2003
PTHREAD_BARRIERATTR_GETPSHARED(P)
[root@RHEL48-LTP-EM64T make]#
------------

In the manual, it seems not to be mentioned the necessity of the "". Sorry, but I examine context and e-mail a few days later.

Regards--

-Tomonori Mitani

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

...

RHEL sucks for compiling stuff (I remember because it used to be a reference platform when I was doing the Makefile work). Try swapping around -lrt and -lpthread in the LDLIBS file and see whether or not things work. If not, then I'd talk to Redhat and figure out what it doesn't work.
-Garrett

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

I tried to build "sched_yield", and found that they succeeded to build in my system (all of RHEL4.8 - x86, x86_64, ia64).
I didn't notice that "-lpthread" added to "Makefile" of "sched_yield" from 2010/10/29 git.

It was October 27 that I tried "-pthread" last. After that, I merely revised "LDLIBS" automatically and did make with it. Sorry!

Thank you--

-Tomonori Mitani

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list