Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Jun 1999 16:33:24 -0400
From:      "Alok K. Dhir" <adhir@forumone.com>
To:        "Ilya Obshadko" <ilya@zhurnal.ru>
Cc:        "Juriy Goloveshkin" <j@avias.com>, <freebsd-stable@freebsd.org>
Subject:   RE: Re[2]: mysql problems after upgrading to 3.2-stable
Message-ID:  <000f01beb900$a5d830a0$5438b5d8@forumone.com>
In-Reply-To: <Pine.BSF.4.05.9906172003230.6041-100000@xfire.polit.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

The mysql322 port builds fine on 3.x using mit-pthreads.  I think the port
patches the mit-pthreads library to build correctly on 3.x to allow it to work.

It seems to work pretty good over here, so I am trying to decide if I should
switch to the patched uthread libaray version...

Thanks

> -----Original Message-----
> From: Ilya Obshadko [mailto:ilya@zhurnal.ru]
> Sent: Thursday, June 17, 1999 12:06 PM
> To: Alok K. Dhir
> Cc: Juriy Goloveshkin; freebsd-stable@freebsd.org
> Subject: RE: Re[2]: mysql problems after upgrading to 3.2-stable
>
>
> On Thu, 17 Jun 1999, Alok K. Dhir wrote:
>
> > Can you send these patches through?
>
> Available at
>
>  ftp://ftp.pcnet.com/users/eischen/FreeBSD/uthread.tgz
>  ftp://ftp.pcnet.com/users/eischen/FreeBSD/uthread_diffs.gz
>
> (BIG THANKS to author).
>
> > Also - on a related topic, what is the benefit of building mysql
> with the system
> > thread library in libc_r versus using mit-pthreads?
>
> I could not build mysql with mit-pthreads on FreeBSD 3.x. On the other
> hand, I suppose that built-in system threads are faster than third-party
> ones.
>
> #-- Ilya Obshadko [IDO-RIPN] -------------------------------#
> #-- email: ilya@zhurnal.ru, ilya24@chat.ru -----------------#
> #-- ICQ UIN: 10704338 --------------------------------------#
>
>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000f01beb900$a5d830a0$5438b5d8>