Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 168939 - dev-lang/ruby ebuild needs different config parameters for -ipv6
Summary: dev-lang/ruby ebuild needs different config parameters for -ipv6
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
: 278574 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-03-01 22:03 UTC by Roy Wright
Modified: 2010-01-10 22:05 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roy Wright 2007-03-01 22:03:43 UTC
When the underlying OS does not support IPv6, ruby should be compiled with:

  ./configure --enable-ipv6 --with-lookup-order-hack=INET

Upstream bug:

  http://rubyforge.org/tracker/?func=detail&atid=1698&aid=5627&group_id=426

Thank you
Comment 1 Hans de Graaff gentoo-dev Security 2008-12-15 21:19:59 UTC
A problem here might be that we can't really determine whether the underlying OS is truely lacking ipv6 support. We can't just go with the ipv6 USE flag since this only indicates whether the user wants to enable specific ipv6 extensions, not whether ipv6 is available and working properly on the OS level.

Furthermore this appears to be a bug in glibc? So it should really be reported and fixed there. Ruby just seems to be relaying the information to the getaddrinfo libc call.
Comment 2 Alex Legler (RETIRED) archtester gentoo-dev Security 2009-07-23 20:37:57 UTC
*** Bug 278574 has been marked as a duplicate of this bug. ***
Comment 3 Alex Legler (RETIRED) archtester gentoo-dev Security 2009-09-09 14:48:42 UTC
Fixed in 1.9.1_p243.
Comment 4 Alex Legler (RETIRED) archtester gentoo-dev Security 2009-10-06 20:00:20 UTC
...and ruby-1.8.7_p174-r1
Comment 5 Alex Legler (RETIRED) archtester gentoo-dev Security 2010-01-10 22:05:35 UTC
...and ruby-1.8.6_p388.

We now have this in all supported Ruby branches: 1.8.6, 1.8.7 and 1.9. I think the bug can be closed now.