From owner-freebsd-current Tue Oct 31 11:48:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from white.dogwood.com (white.dogwood.com [63.96.228.130]) by hub.freebsd.org (Postfix) with ESMTP id 8932437B479 for ; Tue, 31 Oct 2000 11:48:55 -0800 (PST) Received: (from dave@localhost) by white.dogwood.com (8.11.1/8.9.3) id e9VJmqL53635; Tue, 31 Oct 2000 11:48:52 -0800 (PST) (envelope-from dave) From: Dave Cornejo Message-Id: <200010311948.e9VJmqL53635@white.dogwood.com> Subject: Re: threaded python seg faults? In-Reply-To: <200010311816.e9VIGBc04408@vashon.polstra.com> from John Polstra at "Oct 31, 2000 10:16:11 am" To: John Polstra Date: Tue, 31 Oct 2000 11:48:52 -0800 (PST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch seems to solve my problems, thank you! dave c John Polstra wrote: > It's because libc_r isn't getting initialized in time. > > Please try applying the appended patch to "src/gnu/lib/libgcc_r/Makefile" > and let us know if it fixes the problem. You will need to rebuild > and reinstall libgcc_r, and then rebuild python. > > Thanks for providing the detailed information! This never would > have caught my eye otherwise. > > John > > > Index: Makefile > =================================================================== > RCS file: /home/ncvs/src/gnu/lib/libgcc_r/Makefile,v > retrieving revision 1.4 > diff -u -r1.4 Makefile > --- Makefile 1999/10/03 02:43:20 1.4 > +++ Makefile 2000/10/31 18:06:34 > @@ -2,5 +2,6 @@ > > LIB= gcc_r > CFLAGS+=-D_PTHREADS > +CFLAGS+=-D'__GTHREAD_MUTEX_INIT_FUNCTION(m)=pthread_mutex_init(m, NULL)' > > .include "../libgcc/Makefile" > > > -- Dave Cornejo @ Dogwood Media, Fremont, California "There aren't any monkeys chasing us..." - Xochi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message