Summary: | stabilize dev-lang/ruby-1.8.6_p287-r4 (was: dev-lang/ruby-1.8.6 / dev-libs/openssl-0.9.8j - openssl_missing.h:123: error: conflicting types for 'BN_rand_range') | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Legler (RETIRED) <a3li> |
Component: | New packages | Assignee: | Gentoo Ruby Team <ruby> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | a_tevelev, cheoppy, danyl, dark, purple_skunk, pva, superheron, xitij.patel+gentoo |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alex Legler (RETIRED)
2009-01-09 12:47:18 UTC
The interesting part here is, that the fiel is called: openssl_missing.h. It does include some additional prototypes missing in older openssl version. Now, the Problem is, that: 1.) The header gets included unconditionally 2.) Most of the prototypes are unconditional I currently assume that the headers of the newer openssl version now include some additional prototypes and thus collide, because the ruby package did not 'expect' for this to happen. I didn't have a chance to diff the openssl.h files yet though and investigate this further. This should now be fixed in ruby-1.8.6_p287-r11. I have also added a fixed version of ruby-1.8.6_p287-r4 using the same patch for those arches that have not re-added their keyword yet due to the change from ruby-config to eselect. I'm leaving this bug open for now since this problem also affects current stable versions. My intention is to file a stabilization bug tomorrow or the day after for ruby-1.8.6-p287-r4. Hans, probably it's time to stabilize ruby-1.8.6-p287-r4. I've checked it and it works here. (In reply to comment #3) > Hans, probably it's time to stabilize ruby-1.8.6-p287-r4. I've checked it and > it works here. Agreed. Arches, please stabilize dev-lang/ruby-1.8.6_p287-r4. The recent stabilization of openssl-0.8.9j is breaking compilation of the currently stable ruby 1.8.6_p287-r1. The -r4 version fixes this and also contains two fixes for minor problems (in -r2 and -r3). We'd normally wait longer before stabilization, but with the current stable releases broken it is better to stabilize this version quickly. I'm trying to figure out where -r4 came from; not clear from the ChangeLog. I'm on -r11 right now for sparc. (In reply to comment #5) > I'm trying to figure out where -r4 came from; not clear from the ChangeLog. > I'm on -r11 right now for sparc. > -r10 was split off of -r3 for testing the eselect-ruby module. -r4 is -r3 (= still with ruby-config) with the openssl fix applied. *** Bug 254919 has been marked as a duplicate of this bug. *** Stable for HPPA. ppc64 stable amd64/x86 stable *** Bug 255159 has been marked as a duplicate of this bug. *** ppc stable Stable on alpha. arm/ia64/s390/sh/sparc stable, closing |