Date: Tue, 22 Feb 2005 01:30:59 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: "Jeremy Messenger" <mezz7@cox.net> Cc: ports@freebsd.org Subject: Re: FreeBSD Port: ruby18-1.8.2_2 Message-ID: <p06210212be4080f3fdfb@[128.113.24.47]> In-Reply-To: <opsmk4tyj19aq2h7@mezz.mezzweb.com> References: <64348.207.219.213.162.1109011818.squirrel@207.219.213.162> <a5d5f155be4e65d41f9775df96135160@khera.org> <20050221194954.GA49438@xor.obsecurity.org> <opsmkkzit99aq2h7@mezz.mezzweb.com> <6a2d0a658b1cfe9503183eb978e4e2d6@snsonline.net> <opsmklbltj9aq2h7@mezz.mezzweb.com> <p0621020abe40281a2ae3@[128.113.24.47]> <opsmk268vc9aq2h7@mezz.mezzweb.com> <p06210211be4077eee0cc@[128.113.24.47]> <opsmk4tyj19aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:11 AM -0600 2/22/05, Jeremy Messenger wrote:
>On Tue, 22 Feb 2005, Garance A Drosihn <drosih@rpi.edu> wrote:
>>
>>Hmm. Note that ruby-1.8.2_1 is installed and working fine on my
>>sparc64 machine. Has all that much changed between ruby-1.8.2_1
>>and ruby-1.8.2_2 ?
>
>Yes, it enables thread support by default now to reduce the
>problem/complicate for other ports that depend on ruby, but
>turned out another problem for different ${ARCH} too. So far
>from what I can see is to disable thread support in ruby for
>only different ${ARCH} that don't work.
Okay. I might be able to look into this next weekend, but not any
earlier than that. So if someone else has the time to look at it,
then please do go ahead.
>but I can't test on FreeBSD 4.x and 6.x though.
Well, when it comes to powerPC or sparc64, you will not have to
test on FreeBSD 4.x... :-)
--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06210212be4080f3fdfb>