/lang/wamcc/

which means the ruby interpreter is linked with libpthread. This will allow threaded extension libraries to run and work properly on those systems. The --march=cputype flag is disabled because it gets ruby to malfunction and fail to build. I don't know if the problem is in libpthread or in gcc. (It really makes me wonder if they had actually tested before asking me to do this somewhat risky change ;-) 
dropped and the lang/ruby16_r and lang/ruby18_r ports have been
removed, since no one seems to appreciate the partially working
solution.

Good news is that the pthread support of lang/ruby18 is now enabled by
default for newer systems, which means the ruby interpreter is linked
with libpthread.  This will allow threaded extension libraries to run
and work properly on those systems.

The --march=cputype flag is disabled because it gets ruby to
malfunction and fail to build.  I don't know if the problem is in
libpthread or in gcc.

(It really makes me wonder if they had actually tested before asking
me to do this somewhat risky change ;-)
Now that ruby 1.8.0 is officially released, rename ruby to ruby16, and 2003-08-07T11:10:05+00:00 knu knu@FreeBSD.org 2003-08-07T11:10:05+00:00 f0eebb853291d276eca49a6b995c1578a9fad9ac ruby-devel to ruby18. 
ruby-devel to ruby18.
Update RUBY_VER and fix the build. 2002-12-26T02:58:39+00:00 knu knu@FreeBSD.org 2002-12-26T02:58:39+00:00 57e530d4aaf0cf2fce31dfbfbf3634df651b04ec Submitted by: nork 
Submitted by:	nork
Add lang/ruby_r and lang/ruby_r-devel, ruby binary linked with libc_r. 2001-06-04T15:02:52+00:00 knu knu@FreeBSD.org 2001-06-04T15:02:52+00:00 ccba0f286a9fb4cf87e128ea26c50d7e06ffdff1 As there are unidentified problems with libc_r + ruby, please use this with care. I'd appreciate if any of you could join me in debugging. 
As there are unidentified problems with libc_r + ruby, please use this
with care.  I'd appreciate if any of you could join me in debugging.