> There has been a discussion on the Ruby mailing list. Out of
> curiousity what needs to be fixed specifically in order for 3.5 (and
> below?). I know 3.6-current has the setjmp/longjmp working
> correctly(well to what is expected and not different from others)

You need to recompile libc with src/lib/libc/arch/sparc/gen/_setjmp.S
r1.6 on sparc,or src/lib/libc/arch/sparc64/gen/_setjmp.S r1.3 on
sparc64, then install the new libc.

> ts(a member of ruby-talk) jsut said to replace the setjmp/longjmp with
> _setjmp/_longjmp. Is this correct action. I know it would take some
> time shifting through source to see where it is located.

This is probably a decent workaround, but the best is to either run a
fixed libc, or upgrade to 3.6 when it becomes available.