Date: Wed, 23 Feb 2005 00:51:45 -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: <opsmm1cjkz9aq2h7@mezz.mezzweb.com> In-Reply-To: <p0621021cbe41c5901398@[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]> <opsmk4tyj19aq2h7@mezz.mezzweb.com> <opsmladoez9aq2h7@mezz.mezzweb.com> <fe58da1363cefb8f0cbf9c24ba7b2aa9@snsonline.net> <opsmlb11jb9aq2h7@mezz.mezzweb.com> <opsmleaxs29aq2h7@mezz.mezzweb.com> <p06210218be4149c30f49@[128.113.24.47]> <opsmma9em59aq2h7@mezz.mezzweb.com> <p06210219be4190359234@[128.113.24.47]> <opsmmv5lj89aq2h7@mezz.mezzweb.com> <p0621021cbe41c5901398@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Feb 2005 01:12:02 -0500, Garance A Drosihn <drosih@rpi.edu>
wrote:
> At 10:59 PM -0600 2/22/05, Jeremy Messenger wrote:
>> On Tue, 22 Feb 2005, Garance A Drosihn <drosih@rpi.edu> wrote:
>>>
>>> It seems there are two different issues.
>>>
>>> When it comes to the present port (ruby-1.8.2_2), it compiles
>>> fine on sparc64 if I change one line in the Makefile:
>>
>> Oh, I thought you mean by ruby-1.8.2_1...
>
> The previous port, version ruby-1.8.2_1, compiles and runs on
> sparc64 without any problem. The present port, (ruby-1.8.2_2),
> will coredump while building unless the following one-line
> change is made. By "present port", I mean the port that users
> will get when they cvsup the ports collection right now.
>
>>> .include <bsd.port.pre.mk>
>>> -.if ${OSVERSION} >= 502102
>>> +.if ${OSVERSION} >= 502102 && ${ARCH} != "sparc64"
>>> RUBY_ENABLE_PTHREAD?= public demand
>>> .endif
>
>> This should be no difference with with my patch, because my
>> patch doesn't enable pthread stuff. I removed the pthread
>> stuff because it causes few more troubles.
>
> I do not completely understand what your patch is attempting
> to do. I just played with it until I had something which
> compiled and seems to work on both sparc64 and powerPC.
>
>>> The patch that I end up with is at:
>>>
>>> http://people.freebsd.org/~gad/ports/ruby18+mezz+gad_3.diff
>>>
>>> My patch is about the same as your last patch, minus the
>>> patch-ruby-1.6.8-fix-x86_64 file, plus my changes to the Makefile.
>>
>> This is very weird.. Why does sparc64 dislike the -pthread?
>> sparc64 doesn't has libpthread support?
>
> It might not. I seem to remember that the sparc64 port is
> missing some parts of support for threaded applications.
I had a chat with marcus and he said that he knows that sparc64 is using
libc_r, so I believe that my lastest ruby18.diff should solve your problem
by remove '-lc'.. libc and libc_r can't be coexist; it's same as with
FreeBSD 4.x stuff.
>> [...] My ruby28.diff is such smaller now.
>
> At this point, I really have no more time for testing this.
> Hopefully your latest patch works as well as you expect it to.
Ok, it's no problem.. I will asking kwm. Thanks!
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?opsmm1cjkz9aq2h7>