[bug-notifications] [ruby 0004892]: Please upgrade Ruby to a current 1.9.x release (1.9.3-p0)

Mantis Bug Tracker noreply at opencsw.org
Sun Feb 12 02:37:36 CET 2012


A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4892 
====================================================================== 
Reported By:                jcraig
Assigned To:                bwalton
====================================================================== 
Project:                    ruby
Issue ID:                   4892
Category:                   upgrade
Reproducibility:            N/A
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2012-02-06 21:40 CET
Last Modified:              2012-02-12 02:37 CET
====================================================================== 
Summary:                    Please upgrade Ruby to a current 1.9.x release
(1.9.3-p0)
Description: 
What are the plans to move the ruby packages from 1.8.x to 1.9.x. 
====================================================================== 

---------------------------------------------------------------------- 
 (0009591) bwalton (administrator) - 2012-02-12 02:37
 https://www.opencsw.org/mantis/view.php?id=4892#c9591 
---------------------------------------------------------------------- 
Status update:

The recipe was using gcc4 and on i386, things are in good shape.  On sparc,
the binaries were generating bus errors.  I've switched back to sun CC and
sparc looks better (using -xmemalign=li).  I'll see what things are like on
i386 with sun CC.

The errors on i386 are partially ignorable...once we have a released 1.9,
the webrick.cgi tests should work.  They're started with a cleaned
environment and therefore can't leverage LD_PRELOAD set by the test suite.

The only error that seems to be of real significance is a gdbm error...

I think we can get test packages put together in fairly short order.



More information about the bug-notifications mailing list