cvs commit: ports/Mk bsd.ruby.mk ports/lang/ruby18 Makefile
distinfo pkg-plist ports/lang/ruby18/files patch-cgi.rb
ports/x11-toolkits/ruby-tk pkg-plist
Akinori MUSHA
knu at iDaemons.org
Thu Dec 23 13:01:20 PST 2004
At Thu, 23 Dec 2004 14:41:45 -0600,
Jeremy Messenger wrote:
> On Thu, 23 Dec 2004 20:30:10 +0000 (UTC), Akinori MUSHA
> <knu at FreeBSD.org> wrote:
>
> > knu 2004-12-23 20:30:09 UTC
> >
> > FreeBSD ports repository
> >
> > Modified files:
> > Mk bsd.ruby.mk
> > lang/ruby18 Makefile distinfo pkg-plist
> > x11-toolkits/ruby-tk pkg-plist
> > Removed files:
> > lang/ruby18/files patch-cgi.rb
> > Log:
> > Update lang/ruby18 to 1.8.2-preview4.
> > * Please upgrade sysutils/portupgrade prior to this one, or pkgdb(1)
> > may coredump with a double free() problem from a misuse of the DL
> > module. In that case, reinstall sysutils/portupgrade manually.
>
> I didn't check those yet, but have you add '-pthread' as default yet?
> ruby-gtk2/ruby-gnome2 are broke by default in FreeBSD 5.x and 6.x,
> because of ruby doesn't use -pthread. I have emailed to you few times
> and you never have reply back.
>
> Also, I think we should get rid of _r stuff if it possible. The _r is
> creating problems, so how about enable it by default?
Sorry, but I have't got to be sure that ruby with -pthread enabled
works flawlessly. Do you? I'll do some more tests this weekend on my
FreeBSD 5.x box. If it goes fine, I'll happily enable it by default.
On the other hand, I still believe ruby with -pthread enabled does
coredump on FreeBSD 4.x when combined with a certain kind of external
libraries, so we can only enable it on FreeBSD >=5.x. What is your
suggestion with ruby_r vs. FreeBSD 4.x?
--
/
/__ __ Akinori.org / MUSHA.org
/ ) ) ) ) / FreeBSD.org / Ruby-lang.org
Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp
"It seems to me as we make our own few circles 'round the sun
We get it backwards and our seven years go by like one"
More information about the cvs-all
mailing list