Public bug reported:
[Impact]
On precise/arm*, we had to disable ruby's testsuite so that it would
build. The reason for this was that, at the time, precise's eglibc
didn't have get/setcontext routines for ARM, and ruby was forced to
select its own (broken) implementation instead.
Later in the precise development, eglibc grew support for get/setcontext
on ARM, but we never rebuilt ruby to pick this up and fix itself. The
obvious solution to this is to turn on the testsuite again and SRU so a
rebuilt ruby fixes itself on ARM.
[Testcase]
If ruby passes its testsuite on both ARM builds, it's clearly ahead of
where it was before, and that's pretty much all the test needed to prove
the above is fixed.
[Regression Potential]
For all arches other than ARM, this is just a rebuild with precise's
current toolchain. For ARM, this is a rebuild that will flip ruby from
using a broken internal implementation to using a much saner glibc
implementation of the same thing, so any potential for regression here
is between nonexistant and tiny.
** Affects: ruby1.9.1 (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: ruby1.9.1 (Ubuntu Precise)
Importance: Undecided
Assignee: Adam Conrad (adconrad)
Status: New
** Also affects: ruby1.9.1 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: ruby1.9.1 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021604
Title:
ruby uses broken internal get/setcontext routines on precise/ARM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby1.9.1/+bug/1021604/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
