From owner-freebsd-gnome@FreeBSD.ORG Sun Feb 8 14:34:31 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89A6816A4D0; Sun, 8 Feb 2004 14:34:31 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AB5343D1F; Sun, 8 Feb 2004 14:34:31 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i18MY4fo029110; Sun, 8 Feb 2004 17:34:04 -0500 (EST) Date: Sun, 8 Feb 2004 17:34:04 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Wesley Morgan In-Reply-To: <20040208172313.V24023@volatile.chemikals.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: gnome@freebsd.org cc: Mark Huizer cc: Joe Marcus Clarke cc: current@freebsd.org Subject: Re: Firebird linked against libc_r and libpthread? X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2004 22:34:31 -0000 On Sun, 8 Feb 2004, Wesley Morgan wrote: > On Sun, 8 Feb 2004, Mark Huizer wrote: > > > On Sun, Feb 08, 2004 at 11:37:12AM -0800, Joe Marcus Clarke wrote: > > > marcus 2004/02/08 11:37:12 PST > > > > > > * Clean up the pkg-message a bit to reflect reality with respect to Perl > > > > > > Thanks to casaveli on BSDForums for finding it was esound causing the lock up > > > as well as testing the patch mentioned above. > > > > I just rebuild firebird on a recent -current, and it seems this port is > > suffering from the pthread changes, because it is linked to both libc_r > > and libpthread. It seems to run though, but not as stable as 0.6 was > > doing. > > I'm having some trouble with libtool wanting to use libc_r with several > ports, such as like g-wrap. Yeah, I've seem several slightly different versions of libfool and I recall them sometimes knowing about libc_r. Why do some ports include their own libfool? <\rant> -- Dan Eischen