Archived
This forum has been archived. Please start a new discussion on GitHub.
make test error on pthread_condattr_setclock
Hi,erveryone
I have a problem when install the ICE3.3
My platform is Redhat 4 update 4. X86_64, GCC 3.4.6
I installed the mcpp by following the instrunction.
I built the cpp directory. I open "LP64 ?= yes" and change db_cxx to db_cxx-4.2 in Make.rules
Then make. No error.
When I make test, 2/63 does not pass
Is there anyone could help me ? many thanks
I have used ICE2.1 for about 3 years
*** running tests 2/63 in /mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/test/IceUtil/thread
*** configuration: Default
*** test started: 04/30/09 16:05:38
starting client... ok
running mutex test... /mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/test/IceUtil/thread/client: symbol lookup error: /mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/lib/libIceUtil.so.33: undefined symbol: pthread_condattr_setclock
unexpected exit status: expected: 0, got 127
Traceback (most recent call last):
File "/mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/test/IceUtil/thread/run.py", line 25, in ?
TestUtil.simpleTest(client, os.getcwd())
File "/mnt/raid1/user/osstone/stone/Ice-3.3.1/scripts/TestUtil.py", line 957, in simpleTest
client.waitTestSuccess()
File "/mnt/raid1/user/osstone/stone/Ice-3.3.1/scripts/Expect.py", line 537, in waitTestSuccess
test(self.exitstatus, exitstatus)
File "/mnt/raid1/user/osstone/stone/Ice-3.3.1/scripts/Expect.py", line 522, in test
assert False
AssertionError
('test in /mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/test/IceUtil/thread failed with exit status', 256)
I have a problem when install the ICE3.3
My platform is Redhat 4 update 4. X86_64, GCC 3.4.6
I installed the mcpp by following the instrunction.
I built the cpp directory. I open "LP64 ?= yes" and change db_cxx to db_cxx-4.2 in Make.rules
Then make. No error.
When I make test, 2/63 does not pass
Is there anyone could help me ? many thanks
I have used ICE2.1 for about 3 years
*** running tests 2/63 in /mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/test/IceUtil/thread
*** configuration: Default
*** test started: 04/30/09 16:05:38
starting client... ok
running mutex test... /mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/test/IceUtil/thread/client: symbol lookup error: /mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/lib/libIceUtil.so.33: undefined symbol: pthread_condattr_setclock
unexpected exit status: expected: 0, got 127
Traceback (most recent call last):
File "/mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/test/IceUtil/thread/run.py", line 25, in ?
TestUtil.simpleTest(client, os.getcwd())
File "/mnt/raid1/user/osstone/stone/Ice-3.3.1/scripts/TestUtil.py", line 957, in simpleTest
client.waitTestSuccess()
File "/mnt/raid1/user/osstone/stone/Ice-3.3.1/scripts/Expect.py", line 537, in waitTestSuccess
test(self.exitstatus, exitstatus)
File "/mnt/raid1/user/osstone/stone/Ice-3.3.1/scripts/Expect.py", line 522, in test
assert False
AssertionError
('test in /mnt/raid1/user/osstone/stone/Ice-3.3.1/cpp/test/IceUtil/thread failed with exit status', 256)
0
Comments
-
pthread_condattr_setclock
Only the Cond.cpp use pthread_condattr_setclock.#if !defined(__hpux) && !defined(__APPLE__)
rc = pthread_condattr_setclock(&attr, CLOCK_MONOTONIC);
if(rc != 0)
{
throw ThreadSyscallException(__FILE__, __LINE__, rc);
}
#endif
Bernard suggested that ifdef this out, because RH9 do not support monotonic clock.
But the "pthread_condattr_setclock" is supported in RH AS4. Why not defined?0 -
Hi,
Did you install the nptl-devel RPM package? It's required for the pthread_condattr_setclock function on RHEL 4.
Cheers,
Benoit.0