From owner-freebsd-stable Wed Jun 17 12:27:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17710 for freebsd-stable-outgoing; Wed, 17 Jun 1998 12:27:50 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA17705 for ; Wed, 17 Jun 1998 12:27:48 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0ymNrn-0007Kx-00; Wed, 17 Jun 1998 12:27:31 -0700 Date: Wed, 17 Jun 1998 12:27:29 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: John Birrell cc: "Andrew N. Edmond" , stable@FreeBSD.ORG, monty@tcx.se Subject: Re: is libc_r broken in 980520-SNAP (and stable?)? In-Reply-To: <199806170244.MAA10102@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Jun 1998, John Birrell wrote: > Andrew N. Edmond wrote: > > I've been working with Monty at www.tcx.se (makers of MySQL - the best > > free SQL database, ever :), and we've been having a very difficult time > > with the libc_r in 980520-SNAP (clean install). > > There are a few unwelcome features that should be fixed now in -current. One thing that confuses me is that how does libc_r from 2.2.6-stable and -current compare these days? They used to be identical, but now that -current is getting kernel support for threads and alpha stuff, I assume that they must be quite different now. Primarily, is libc_r from 2.2.6-stable just as usable as libc_r from current? Highwind Software (www.highwind.com) has a beta version of their news software that it is statically linked to a libc_r with fixes they say they got from you. Would this be a -stable libc_r or a -current libc_r that they are using? Sigh, I apologize for the number of questions... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message