Summary: | USE=-threads emerge dev-lang/ruby fails with glibc-2.3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | mips |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | HPPA | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 168131 | ||
Bug Blocks: |
Description
Jeroen Roovers (RETIRED)
2007-02-23 13:49:45 UTC
(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. Good bye. 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. <http://groups.google.de/group/ruby-talk-google/msg/062070e6fa71d699> *** This bug has been marked as a duplicate of bug 161566 *** |