From owner-freebsd-ports@FreeBSD.ORG Tue Feb 22 08:10:48 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F9AA16A4CE for ; Tue, 22 Feb 2005 08:10:48 +0000 (GMT) Received: from lakermmtao02.cox.net (lakermmtao02.cox.net [68.230.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A6C043D46 for ; Tue, 22 Feb 2005 08:10:47 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by lakermmtao02.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050222081045.EKDQ22208.lakermmtao02.cox.net@mezz.mezzweb.com>; Tue, 22 Feb 2005 03:10:45 -0500 Date: Tue, 22 Feb 2005 02:11:38 -0600 To: "Garance A Drosihn" References: <64348.207.219.213.162.1109011818.squirrel@207.219.213.162> <20050221194954.GA49438@xor.obsecurity.org> <6a2d0a658b1cfe9503183eb978e4e2d6@snsonline.net> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: User-Agent: Opera M2/7.54 (Linux, build 955) cc: ports@freebsd.org Subject: Re: FreeBSD Port: ruby18-1.8.2_2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2005 08:10:48 -0000 On Tue, 22 Feb 2005 00:11:48 -0600, Jeremy Messenger wrote: > On Tue, 22 Feb 2005 00:55:22 -0500, Garance A Drosihn > wrote: > >> At 11:36 PM -0600 2/21/05, Jeremy Messenger wrote: >>> On Mon, 21 Feb 2005, Garance A Drosihn 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: >>>> >>> >>> >>> 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 Oops, wrong person, it's lofi.. My plan of tonight or tomorrow is to still use this new patch then reinstall it. Also, rebuild/reinstall all apps that depend on ruby. After that I am going to test on few ruby ports that need threads (ruby-opengl, ruby-gtk2, ruby-gnome2 and etc) to see if they still will working or not. I am hoping that lofi will have time to test it on FreeBSD 4.x. New patch: http://people.freebsd.org/~mezz/diff/ruby18.diff Be sure to 'rm -rf /usr/ports/lang/ruby18/*' and update your ports tree before you use this patch. The difference between ruby-1.8.2_2 to new patch is that disable thread again, teach ruby about ${PTHREAD_*}, and use patches from Gentoo/Debian. If this new patch doesn't work, then I guess one of us will have to mark ruby-opengl and few other that require threads as broke for on sparc64 and other ${ARCH} and disable thread support in ruby. It's a lot better than re-create a voodoo '_r'. Cheers, Mezz > 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