Re: Status of revivesa

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

BTW, libpthread major wasn't bumped on SA to 1:1 migration.

This means libpthread APIs have not been changed
while SA syscalls have been removed.

Is there any reason why "thousand binaries" have to be recompiled
even if libc.so and libpthread.so will also be updated with
the new post SA kernel?

Or, does the "compatibility problem" only affect chroot environments
where any base libraries must not be updated?

For example, "make test" on perl binary compiled on 4.0 shows:
---
On 4.0:
Failed 4 test scripts out of 966, 99.59% okay.
(four thread tests fail)

On 4.99.72 HEAD kernel with 4.0 libc and libpthread
Failed 27 test scripts out of 966, 97.20% okay.
(most thread tests fail)

On 4.99.72 HEAD kernel with 4.99.72 libc and libpthread
Failed 1 test script out of 966, 99.90% okay.
(only one locale test fails, due to version mismatched dl modules?)
---

named(8) binary from stock 4.0 distribution seems working
on 4.99.72 HEAD kernel with 4.99.72 libc and libpthread.
(all other binaries are stock 4.0)

firefox3 binary installed by pkg_add(1) from 4.0-2008Q2 seems
working on 4.99.72 HEAD kernel with 4.99.72 libc and libpthread.

Thread tests by sysbench packages binary from 4.0-2008Q2 also
works on 4.99.72 HEAD kernel with 4.99.72 libc and libpthread.

What's expected not even with new base binaries?
---
Izumi Tsutsui