Do the builders have newer kernels now? If so the testsuite in apr may
now pass and the workaround could be dropped.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apr in Ubuntu.
https://bugs.launchpad.net/bugs/604753
Title:
[eglibc
Reverted:
apr (1.4.2-7ubuntu2) natty; urgency=low
* Revert previous change. I forgot the build servers have an older
kernel on which the testsuite fails to pass. Reopens LP: #604753
-- Jani Monoses Mon, 21 Mar 2011 10:14:43 +0200
Need to reapply once buildds' kernels are upgraded
** C
** Changed in: linaro-toolchain-misc
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apr in ubuntu.
https://bugs.launchpad.net/bugs/604753
Title:
[eglibc] process shared mutex's fail on armel
This bug was fixed in the package apr - 1.4.2-7ubuntu1
---
apr (1.4.2-7ubuntu1) natty; urgency=low
* debian/rules: Reenable robust pthread mutexes on armel, now that eglibc
process shared mutexes were fixed to use gcc atomic sync builtins.
(LP: #604753)
-- Jani MonosesF
apr without workaround applied passes tests on current natty so glibc is fixed.
We still need to revert the workaround in apr (that is part of Debian packaging
now as well)
** Changed in: eglibc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
I think this the issue has been fixed by #643171. I do not see this
testcase failing using a recent (e)glibc and GCC. Could anyone of the
original reporters check if it works for them? Please make sure that you
use at least glibc 2.12.1-0ubuntu11 and GCC 4.5.
--
You received this bug notification
I ran the apr testsuite (svn revision 1071306) several times and I
notice that the testlock:test_timeoutcond test fails sometimes because
the timer returned to late. Not sure sure if this is related.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is su
I ran the testprocmutex test on a panda board using ubuntu natty alpha 2 and it
passed:
$ ./testall testprocmutex
testprocmutex : SUCCESS
All tests passed.
$ apt-cache show libc6 gcc|grep Version
Version: 4:4.5.1-1ubuntu3
Version: 2.12.1-0ubuntu16
--
You received this bug notification bec
I had a quick look into the apr sources. Their locks/unix/proc_mutex.c can map
the proc_mutex functionality to various methods:
1) Posix sem implemenation (see mutex_posixsem_methods)
2) SysV sem implementation (see mutex_sysv_methods)
3) pthread implementation (see mutex_proc_pthread_methods)
** Tags added: arm-porting-queue
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apr in ubuntu.
https://bugs.launchpad.net/bugs/604753
Title:
[eglibc] process shared mutex's fail on armel v7 (thumb)
--
Ubuntu-server-bugs mailing li
Given that the APR task is just for our own development usage, I'm
setting the status to Confirmed, and the Importance to Wishlist. When
eglibc is fixed, the changes should be reverted, but at the very least,
this bug can change to status Triaged at that point.
** Changed in: apr (Ubuntu)
S
11 matches
Mail list logo
