Libthr stable enough for testing

[Mike Makonnen]

> and then, should it just replace libc_r.co.5? Or do I need to recompile 
> everything that has threads with -lthr instead of -lc_r?

I'm moving this to -current since I have already had to answer it once. I've
included my reply to a another person's similar question.

You shouldn't have to recompile any applications linked with libc_r. libthr is a
drop-in replacement. On my machine I just backup libc_r* and symlink it to
libthr*:

May/26 mtm at kokeb ~% ll /usr/lib/libc_r*
lrwxr-xr-x  1 root  wheel   8 May 26 21:06 /usr/lib/libc_r.a@ -> libthr.a
lrwxr-xr-x  1 root  wheel  11 May 20 17:23 /usr/lib/libc_r.so@ -> libc_r.so.5
lrwxr-xr-x  1 root  wheel  11 May 26 21:06 /usr/lib/libc_r.so.5@ -> libthr.so.1
lrwxr-xr-x  1 root  wheel  10 May 26 21:06 /usr/lib/libc_r_p.a@ -> libthr_p.a

However, I think mdodd@ has a patch so you can create
an /etc/libmap.conf to make different applications use different libraries.
Search the freebsd-threads archive for "/etc/libmap.conf".

> What kind of information are you looking for with the bug reports? Is
> there any debugging code that could be enabled?

The debugging code is enabled by default. Ideally, what I would like is for
people to post detailed descriptions and hopefully a backtrace of any crashes.
Having said that, while you may have some problems with specific
applications, I think the majority of threaded applications should work just
fine.

Cheers.
-- 
Mike Makonnen  | GPG-KEY: http://www.identd.net/~mtm/mtm.asc
mtm at identd.net | D228 1A6F C64E 120A A1C9  A3AA DAE1 E2AF DBCC 68B9
mtm at FreeBSD.Org| FreeBSD - The Power To Serve