Date: Sun, 08 Feb 2004 17:29:06 -0500 From: Joe Marcus Clarke <marcus@FreeBSD.org> To: Wesley Morgan <morganw@chemikals.org> Cc: current@FreeBSD.org Subject: Re: Firebird linked against libc_r and libpthread? Message-ID: <1076279346.16832.33.camel@shumai.marcuscom.com> In-Reply-To: <20040208172313.V24023@volatile.chemikals.org> References: <200402081937.i18JbC9X045079@repoman.freebsd.org> <20040208221236.GA8150@eeyore.local.dohd.org> <20040208172313.V24023@volatile.chemikals.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, 2004-02-08 at 17:24, 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. Please be more specific. What are the messages? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAJrgyb2iPiv4Uz4cRArn8AKCoiUNQCzWSLwS4Ke3AS4bMutPeyQCfQE54 VhBynTSSgN++GurzFlJz14I= =g8k7 -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1076279346.16832.33.camel>