Date: Tue, 22 Feb 2005 00:11:48 -0600 From: "Jeremy Messenger" <mezz7@cox.net> To: "Garance A Drosihn" <drosih@rpi.edu> Cc: ports@freebsd.org Subject: Re: FreeBSD Port: ruby18-1.8.2_2 Message-ID: <opsmk4tyj19aq2h7@mezz.mezzweb.com> In-Reply-To: <p06210211be4077eee0cc@[128.113.24.47]> 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]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Feb 2005 00:55:22 -0500, Garance A Drosihn <drosih@rpi.edu>
wrote:
> At 11:36 PM -0600 2/21/05, Jeremy Messenger wrote:
>> On Mon, 21 Feb 2005, Garance A Drosihn <drosih@rpi.edu> wrote:
>>
>>> I tried this on powerPC, and ruby built fine. I haven't tested
>>> it much, but the things I tested seem to work fine.
>>>
>>> I tried it on sparc64, and ruby didn't build. The attempt
>>> ended with:
>>>
>> <snip>
>>
>> Ruby has few '__sparc__' and '__sparc_v9__' in the very few places,
>> but none of '__sparc64__'. Are there any chance that it will need
>> to add a new define, '__sparc64__', to make ruby works better? I am
>> lacking on knowlege of programming, so someone with the programming
>> knowledge should take a look at those.
>>
>> =======================================
>> # find . -name \* | xargs egrep -l "sparc"
>> ./work/ruby-1.8.2/config.guess
>> ./work/ruby-1.8.2/config.sub
>> ./work/ruby-1.8.2/configure.in
>> ./work/ruby-1.8.2/defines.h
>> ./work/ruby-1.8.2/dln.c
>> ./work/ruby-1.8.2/gc.c
>> ./work/ruby-1.8.2/doc/ChangeLog-1.8.0
>> ./work/ruby-1.8.2/ext/digest/sha1/sha1.c
>> ./work/ruby-1.8.2/configure
>> ./work/ruby-1.8.2/configure.lineno
>> ./work/ruby-1.8.2/configure.bak
>> =======================================
>>
>> Looks like about four to five files that need to take a look at.
>
> 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. It means, few ports will be disable like maybe ruby-opengl and few
others. I personal never have test disable thread support in all version
of FreeBSD with louix or my change to see if others ports that required
thread support in ruby will work. I don't mind to test it, but I can't
test on FreeBSD 4.x and 6.x thought.
Cheers,
Mezz
--
mezz7@cox.net - mezz@FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?opsmk4tyj19aq2h7>