Date: Tue, 20 Mar 2001 07:37:53 +0900 From: "Akinori MUSHA" <knu@iDaemons.org> To: Will Andrews <will@physics.purdue.edu> Cc: FreeBSD Ports <ports@FreeBSD.ORG>, sobomax@FreeBSD.ORG Subject: Re: Qt2X business (KDE2, GL support and XFree86 4.0.2_2+ & xthreads) Message-ID: <86hf0p2xmm.wl@archon.local.idaemons.org> In-Reply-To: <86k85l2y9i.wl@archon.local.idaemons.org> References: <20010318161729.M61859@ohm.physics.purdue.edu> <86r8zuhhzc.wl@archon.local.idaemons.org> <20010318165425.S61859@ohm.physics.purdue.edu> <86lmq1303y.wl@archon.local.idaemons.org> <200103192215.f2JMFri06630@freefall.freebsd.org> <86k85l2y9i.wl@archon.local.idaemons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At Tue, 20 Mar 2001 07:24:09 +0900,
I wrote:
> While the libc & libc_r combo dealt with it completely on 5-CURRENT,
> it just segfaulted on 4-STABLE. So I marked qt2gl as broken without
ruby-^
> hesitation. It couldn't live without a decent libc_r anyway. ;)
This is not a Qt2 specific problem. It's a generic problem when
linking libc against libc_r on FreeBSD 4.x or prior.
I've already seen this in lang/ruby-python, for example. You know,
python is built with -pthread while ruby is not; now you can imagine
what would happen when you put them together..
--
/
/__ __ Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
"We're only at home when we're on the run, on the wing, on the fly"
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?86hf0p2xmm.wl>