On Wed, 29 Nov 2006 10:52:22 -0500
Mikhail Teterin <[EMAIL PROTECTED]> wrote:
> I know. And the ICU developers think, threads should be enabled by default.
> The reason they aren't right now -- in the FreeBSD port -- is because of
> certain bugs in thread implementation(s) on FreeBSD/ia64, which
Mikhail Teterin <[EMAIL PROTECTED]> writes:
> On Wednesday 29 November 2006 10:45, Lowell Gilbert wrote:
> = ICU is different in that not only can it be called from multiple
> = threads, but those threads can (in theory -- as far as I know, you're
> = right that nobody uses this capability right n
On Wednesday 29 November 2006 23:52, Mikhail Teterin wrote:
> Since nothing is using ICU in a multi-threaded fashion _right now_, the
> current version of the port builds without threads by default. Norikatsu
> confirms, he is not calling into ICU from multiple threads either, hence my
> suggestio
On Wednesday 29 November 2006 10:45, Lowell Gilbert wrote:
= ICU is different in that not only can it be called from multiple
= threads, but those threads can (in theory -- as far as I know, you're
= right that nobody uses this capability right now) be interacting.
=
= > You are (slightly) pessim
Mikhail Teterin <[EMAIL PROTECTED]> writes:
> On Wednesday 29 November 2006 09:06, Norikatsu Shigemura wrote:
> = > 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.
> =
> = I understan
On Wednesday 29 November 2006 09:06, Norikatsu Shigemura wrote:
= > 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.
=
= I understand your ideal, think so too. However, in fact, it is
=
On Mon, 27 Nov 2006 11:14:41 -0500
Mikhail Teterin <[EMAIL PROTECTED]> wrote:
> = 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 implement
Norikatsu Shigemura wrote:
> 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.
I've been using that for over a month, and haven't had a single
problem. I've made no other mod
On Mon, 27 Nov 2006 10:32:17 -0500
Mikhail Teterin <[EMAIL PROTECTED]> wrote:
> On Monday 27 November 2006 08:27, Norikatsu Shigemura wrote:
> = Hi mi!
> = I found a problem that icu don't reflect PTHREAD_LIBS=ANY(like -lthr).
> = Please check following patch.
> Thanks, I'll try it... Do yo
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
On Monday 27 November 2006 08:27, Norikatsu Shigemura wrote:
= Hi mi!
=
= I found a problem that icu don't reflect PTHREAD_LIBS=ANY(like -lthr).
= Please check following patch.
Thanks, I'll try it... Do you need it to be thread-aware though? It is built
by default without threads at
Hi mi!
I found a problem that icu don't reflect PTHREAD_LIBS=ANY(like -lthr).
Please check following patch.
Index: Makefile
===
RCS file: /home/ncvs/ports/devel/icu/Makefile,v
retrieving revision 1.24
diff -u -r1.24 M
12 matches
Mail list logo
