ports/devel/icu: PTHREAD_LIBS clean
Mikhail Teterin
mi+kde at aldan.algebra.com
Mon Nov 27 08:19:38 PST 2006
On Monday 27 November 2006 10:59, Norikatsu Shigemura wrote:
= 1. PTHREAD_LIBS=-lthr
= So I removed libpthread.*, I'm testing.
=
= 2. WITHOUT_LIBPTHREAD=yes >> /etc/src.conf and make world
= ru@ committed this way. So I can do it.
= But we can only use on 7-current. If you'll try to get
= libthr environment, you can only select 1.
=
= 3. libpthread.so.2 -> libthr.so.2 in /etc/libmap.conf IS TOO BAD
= I don't think this approch is good, believe that I'll get
= unstable environment.
It will be just as unstable, as one achieved by 1. or 2. Just much easier and
without world-rebuilds.
= > ICU developers think, threads ought to be enabled, but there really is no
= > software at the moment, which calls into ICU from multiple threads at the
= > same time, AFAIK...
=
= I don't think trying to use multiple threads at the same time.
= But if applications use libthr, libraries must use libthr, too.
You are right about the dangers of mixing different thread implementations,
but library may also be not using threads _at all_. -lm, for example, is
happily used by many threaded programs without itself being thread-aware.
(If anything, a library, even a thread-aware one, should, arguably, not be
explicitly linking with any thread implementation -- this way, it will use,
whatever implementation the application is using. But that's a different
topic...)
-mi
More information about the freebsd-ports
mailing list