atthaced there are patches for the dev-lang/ruby-1.8.4* series (almost arch and ~arch) to let compile ruby with or without gbdm support using "gdbm" USE flag. p.s.: i know that the 1.8.5 serie have an automatic gdbm detection, so my patches are valid only for 1.8.4 series.
Created attachment 90277 [details, diff] dev-lang/ruby-1.8.4-r1
Created attachment 90278 [details, diff] dev-lang/ruby-1.8.4.20060529
Urm.. are you sure? I grepped for "gdbm" from configure.in in ruby-1.8.5-p2 and found nothing. This bug may relate to bug #128837
(In reply to comment #3) > Urm.. are you sure? I grepped for "gdbm" from configure.in in ruby-1.8.5-p2 and > found nothing. This bug may relate to bug #128837 > as i have wrote in the previous comment, my patches was valid only for 1.8.4 version, *NOT FOR* 1.8.5 where there is not a configure option for gdbm. p.s.: my bugreport is 6 months old, is totaly useless to discuss this problem now that 1.8.5 serie is into the stable portage branch. however, thinking about bug #128837, yes, my bugreport is more related to #128837 since the ruby configure process is know to be borked because enable conditionaly a lot of extensions (curses,gdbm,tk). the actual configure process can be ok for normal usage, but it's a pita for embedded environments where peoples *probably* do not want curses,gdbm,tk,tcl as dependencies. a configure patch that made extensions as options can be a very good solution (IMHO).