Problem: `USE=-threads emerge dev-lang/ruby` fails on any HPPA system (probably any system with sys-libs/glibc-2.3). See bug #161566 for a few examples, and attachment #111003 [details] for a build log of the exact failure.
14:31:36 @<GMsoft> [ebuild R ] dev-lang/ruby-1.8.5_p2 USE="ipv6 -cjk
-debug -doc -examples -socks5 -threads -tk" 0 kB
14:31:59 @<GMsoft> [ebuild R ] dev-ruby/rubygems-0.9.0-r2 0 kB
That is a PARISC system with glibc-2.5. No problem there, although it fails the same 4 tests that any x86 fails.
Solution I: Set USE=threads.
Solution II: Wait for glibc-2.5 to be ready for HPPA.
(In reply to comment #0)
> Solution I: Set USE=threads.
It compiles OK therefore it works, or maybe not.
Does that really solve the problem or does it bury it deeper?
> Solution II: Wait for glibc-2.5 to be ready for HPPA.
And until then?
Solution III: p.mask autoconf-2.61 until >=glibc-2.4 is stable on hppa, just like hardened did.
> Solution III: p.mask autoconf-2.61 until >=glibc-2.4 is stable on hppa, just
> like hardened did.
All HPPA users are autoconf-2.61 users, but not all HPPA users are ruby users, so there is no reason to have *all* HPPA users downgrade. Downgrading is evil.
HPPA users can easily get a (partly?) working ruby by setting USE=threads for dev-lang/ruby:
# echo "dev-lang/ruby threads" >> /etc/portage/package.use
Downgrading is evil, but willingly leaving bugs is not. Go figure.
Quite fortunately, we run www.g.o on hardened/x86 and not hppa.
In case anyone who wonders why ruby does not build on a default config stable Gentoo/hppa box, finds this bug:
# echo =sys-devel/autoconf-2.61 >> /etc/portage/package.mask
# emerge autoconf ruby
glibc-2.5 is stable for HPPA. Same 4 tests as on x86 fail. Have a nice day. :)
(Reassigning bug properly in case more arches join.)
Apparently Ruby is slower when built with pthreads support.
*** This bug has been marked as a duplicate of bug 161566 ***