Date: Mon, 11 Jun 2001 19:43:25 +0900 From: "Akinori MUSHA" <knu@iDaemons.org> To: Maxim Sobolev <sobomax@FreeBSD.ORG> Cc: Alexander Langer <alex@big.endian.de>, Will Andrews <will@physics.purdue.edu>, FreeBSD Ports <ports@FreeBSD.ORG>, jmz@FreeBSD.ORG, sf@FreeBSD.ORG Subject: Re: XFree86 4.1.0 and include/GL/glu.h Message-ID: <86k82jl2k2.wl@archon.local.idaemons.org> In-Reply-To: <3B246867.1010305@FreeBSD.org> References: <20010608122321.W3278@bohr.physics.purdue.edu> <3B210DE6.E938A4B4@FreeBSD.org> <20010610224707.A2388@zerogravity.kawo2.rwth-aachen.d> <3B246867.1010305@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At Mon, 11 Jun 2001 09:42:47 +0300,
sobomax wrote:
> No, it is tolally unrelated problem. This is due to the fact that the
> newest Mesa versions are built with pthreads by default, so due to
> FreeBSD stupidity in this area you have to link all ports that use Mesa3
> with -pthreads. This problem could be solved on 5-CURRENT by linking
> Mesa explicitly with -lc_r, but not on 4-STABLE.
Unfortunately, 5-CURRENT still has the stupidity. When an application
first uses stdio without libc_r and then dynamically loads and calls
an external shared library that is linked with libc_r, stdio gets
messed up somehow. Which means, these kind of applications must have
linked with libc_r in the first place.
Also, using libc_r, I've seen many coredumps occurred right after
fork() in a certain situation. (dumped cores didn't help much since
they were of just born processes)
We must investigate further and fix all these pthread problems by the
5.0-RELEASE, or it won't possibly happen until 6.0... ;)
--
/
/__ __ Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
"Freeze this moment a little bit longer, make each impression
a little bit stronger.. Experience slips away -- Time stand still"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k82jl2k2.wl>