[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Ruby gems crash on OpenBSD Sparc64

Wes Moxam

9/29/2004 1:20:00 AM

Hi,

I attempted to run ruby gems on my 'new' Sun Ultra 5 machine which
runs OpenBSD 3.5. Here is the output:

# gem install rails
Attempting local installation of 'rails'
Local gem file not found: rails*.gem
Attempting remote installation of 'rails'
longjmp botch.
Illegal instruction (core dumped)

I have posted the core dump to
http://wmoxam.freeshell.org/files... but I'm not sure if it's
of much use. If anyone can help me out with this problem it would be
greatly appriciated.

-- Wes
12 Answers

David Ross

9/29/2004 1:48:00 AM

0

Wes Moxam wrote:
> Hi,
>
> I attempted to run ruby gems on my 'new' Sun Ultra 5 machine which
> runs OpenBSD 3.5. Here is the output:
>
> # gem install rails
> Attempting local installation of 'rails'
> Local gem file not found: rails*.gem
> Attempting remote installation of 'rails'
> longjmp botch.
> Illegal instruction (core dumped)
>
> I have posted the core dump to
> http://wmoxam.freeshell.org/files... but I'm not sure if it's
> of much use. If anyone can help me out with this problem it would be
> greatly appriciated.
>
> -- Wes

this is not a problem with RubyGems, its a problem with ruby. There are
various minor code changes between BSDs. Before I attempt to pass this
core through my debugger(not junk gdb), which ruby version are you
using? Please make sure this is the latest before I spend time. Make you
you try it on the ruby-stable snapshot.

--dross

Wes Moxam

9/29/2004 2:09:00 AM

0

On Wed, 29 Sep 2004 10:48:03 +0900, David Ross <dross@code-exec.net> wrote:
>
>
> Wes Moxam wrote:
> > Hi,
> >
> > I attempted to run ruby gems on my 'new' Sun Ultra 5 machine which
> > runs OpenBSD 3.5. Here is the output:
> >
> > # gem install rails
> > Attempting local installation of 'rails'
> > Local gem file not found: rails*.gem
> > Attempting remote installation of 'rails'
> > longjmp botch.
> > Illegal instruction (core dumped)
> >
> > I have posted the core dump to
> > http://wmoxam.freeshell.org/files... but I'm not sure if it's
> > of much use. If anyone can help me out with this problem it would be
> > greatly appriciated.
> >
> > -- Wes
>
> this is not a problem with RubyGems, its a problem with ruby. There are
> various minor code changes between BSDs. Before I attempt to pass this
> core through my debugger(not junk gdb), which ruby version are you
> using? Please make sure this is the latest before I spend time. Make you
> you try it on the ruby-stable snapshot.
>
> --dross
>
>

Hi David,

I'm using the standard OpenBSD package which is version ruby-1.8.1. I
can download and compile a CVS version if you like.

-- Wes

David Ross

9/29/2004 2:14:00 AM

0

Wes Moxam wrote:

>On Wed, 29 Sep 2004 10:48:03 +0900, David Ross <dross@code-exec.net> wrote:
>
>
>>Wes Moxam wrote:
>>
>>
>>>Hi,
>>>
>>>I attempted to run ruby gems on my 'new' Sun Ultra 5 machine which
>>>runs OpenBSD 3.5. Here is the output:
>>>
>>># gem install rails
>>>Attempting local installation of 'rails'
>>>Local gem file not found: rails*.gem
>>>Attempting remote installation of 'rails'
>>>longjmp botch.
>>>Illegal instruction (core dumped)
>>>
>>>I have posted the core dump to
>>>http://wmoxam.freeshell.org/files... but I'm not sure if it's
>>>of much use. If anyone can help me out with this problem it would be
>>>greatly appriciated.
>>>
>>>-- Wes
>>>
>>>
>>this is not a problem with RubyGems, its a problem with ruby. There are
>>various minor code changes between BSDs. Before I attempt to pass this
>>core through my debugger(not junk gdb), which ruby version are you
>>using? Please make sure this is the latest before I spend time. Make you
>>you try it on the ruby-stable snapshot.
>>
>>--dross
>>
>>
>>
>>
>
>Hi David,
>
>I'm using the standard OpenBSD package which is version ruby-1.8.1. I
>can download and compile a CVS version if you like.
>
>-- Wes
>
>
I would try downloading the Ruby stable snapshot. 1.8.1 might have a bug
that was fixed in the stable CVS. I can't watch the CVS logs and CIA(the
CVS watcher bot on my freenode channel) all the time. This issue might
have already been addressed.

--dross

ts

9/29/2004 10:35:00 AM

0

>>>>> "W" == Wes Moxam <wildwildwes@gmail.com> writes:

W> longjmp botch.

_setjmp()/_longjmp() is broken on OpenBSD/Sparc, replace it with
setjmp()/longjmp()

See [ruby-talk:96816] and [ruby-talk:96957]

You have 2 occurence of _setjmp() to change in ruby


Guy Decoux

David Ross

9/29/2004 12:34:00 PM

0

ts wrote:
>>>>>>"W" == Wes Moxam <wildwildwes@gmail.com> writes:
>
>
> W> longjmp botch.
>
> _setjmp()/_longjmp() is broken on OpenBSD/Sparc, replace it with
> setjmp()/longjmp()
>
> See [ruby-talk:96816] and [ruby-talk:96957]
>
> You have 2 occurence of _setjmp() to change in ruby
>
>
> Guy Decoux

Obviously its broken. The libraries are slightly different. Do you know
if a patch been commited?

--dross

ts

9/29/2004 1:17:00 PM

0

>>>>> "D" == David Ross <dross@code-exec.net> writes:

D> Obviously its broken. The libraries are slightly different. Do you know
D> if a patch been commited?

I don't know who is the maintainer for openbsd/ruby


Guy Decoux

Wes Moxam

9/29/2004 4:12:00 PM

0

On Wed, 29 Sep 2004 22:17:25 +0900, ts <decoux@moulon.inra.fr> wrote:
> >>>>> "D" == David Ross <dross@code-exec.net> writes:
>
> D> Obviously its broken. The libraries are slightly different. Do you know
> D> if a patch been commited?
>
> I don't know who is the maintainer for openbsd/ruby
>
> Guy Decoux
>

I tried ruby-1.8.2-preview2 and had the same problem. I also tried
compiling the latest code from the cvs server, but had problems
compiling it (yacc was complaining about parse.y).

I will try replacing _setjmp()/_longjmp() as suggested and
re-compile. I'll also try sending a message to the package maintainer
for OpenBSD/Sparc so that this can be corrected.

-- Wes

Claudio Jeker

9/30/2004 11:43:00 AM

0

On Wed, Sep 29, 2004 at 07:35:19PM +0900, ts wrote:
> >>>>> "W" == Wes Moxam <wildwildwes@gmail.com> writes:
>
> W> longjmp botch.
>
> _setjmp()/_longjmp() is broken on OpenBSD/Sparc, replace it with
> setjmp()/longjmp()
>
> See [ruby-talk:96816] and [ruby-talk:96957]
>
> You have 2 occurence of _setjmp() to change in ruby
>

This is no longer true. The sparc/sparc64 versions of _setjump/_longjump
are fixed in OpenBSD 3.6. The change did not make it back to 3.5-stable so
you need to patch or update to 3.6/-current.

--
:wq Claudio

David Ross

9/30/2004 12:09:00 PM

0

Claudio Jeker wrote:

>On Wed, Sep 29, 2004 at 07:35:19PM +0900, ts wrote:
>
>
>>>>>>>"W" == Wes Moxam <wildwildwes@gmail.com> writes:
>>>>>>>
>>>>>>>
>>W> longjmp botch.
>>
>> _setjmp()/_longjmp() is broken on OpenBSD/Sparc, replace it with
>> setjmp()/longjmp()
>>
>> See [ruby-talk:96816] and [ruby-talk:96957]
>>
>> You have 2 occurence of _setjmp() to change in ruby
>>
>>
>>
>
>This is no longer true. The sparc/sparc64 versions of _setjump/_longjump
>are fixed in OpenBSD 3.6. The change did not make it back to 3.5-stable so
>you need to patch or update to 3.6/-current.
>
>
>
Oh, good good. So there needs to be a patch for OpenBSD 3.5 and
whichever are incompatible.

--dross

Wes Moxam

9/30/2004 12:32:00 PM

0

On Thu, 30 Sep 2004 21:08:49 +0900, David Ross <dross@code-exec.net> wrote:
>
>
> Claudio Jeker wrote:
>
> >On Wed, Sep 29, 2004 at 07:35:19PM +0900, ts wrote:
> >
> >
> >>>>>>>"W" == Wes Moxam <wildwildwes@gmail.com> writes:
> >>>>>>>
> >>>>>>>
> >>W> longjmp botch.
> >>
> >> _setjmp()/_longjmp() is broken on OpenBSD/Sparc, replace it with
> >> setjmp()/longjmp()
> >>
> >> See [ruby-talk:96816] and [ruby-talk:96957]
> >>
> >> You have 2 occurence of _setjmp() to change in ruby
> >>
> >>
> >>
> >
> >This is no longer true. The sparc/sparc64 versions of _setjump/_longjump
> >are fixed in OpenBSD 3.6. The change did not make it back to 3.5-stable so
> >you need to patch or update to 3.6/-current.
> >
> >
> >
> Oh, good good. So there needs to be a patch for OpenBSD 3.5 and
> whichever are incompatible.
>
> --dross

Great. Thanks for the help guys.

-- Wes