openSUSE Ruby June 2012

ruby@lists.opensuse.org

6 participants
3 discussions

[opensuse-ruby] Problem with segfaulting ruby C bindings in factory (1.9)

by Josef Reidinger

Hi, when I port of yast2-ruby-bindings to ruby 1.9 as we use in factory I face segfault when require string from C api. When I attach gdb I don't see anything special. I pass common c string to rb_require method and it segfault. Program received signal SIGSEGV, Segmentation fault. 0x00007ffff5527858 in __longjmp_chk () from /lib64/libc.so.6 (gdb) up #1 0x00007ffff3dd9a5c in rb_require_safe () from /usr/lib64/libruby1.9.so.1.9 (gdb) up #2 0x00007ffff4199e9c in YRuby::loadModule (argList=...) at /home/abuild/rpmbuild/BUILD/yast2-ruby-bindings-0.3.10/src/ruby/YRuby.cc:145 145 VALUE result = rb_require(module_path.c_str()); (gdb) p module_path $1 = "/home/abuild/rpmbuild/BUILD/yast2-ruby-bindings-0.3.10/tests/ycp/URI" To play with it do local osc build and then chroot into it with osc chroot ( I have extra packages for osc vim and gdb ). then if you rebuild package with make DEBUG=1 and make DIST=/home/abuild/rpmbuild/BUILDROOT/yast2-ruby-bindings-0.3.11/ then simple do this: cd /home/abuild/rpmbuild/BUILD/yast2-ruby-bindings-0.3.11/tests export Y2DIR=/home/abuild/rpmbuild/BUILDROOT/yast2-ruby-bindings-0.3.11/usr/lib64/YaST2/ gdb /usr/lib/YaST2/bin/y2base run -l - -M . ./ruby_object.ycp UI and you face also segfault. Do you have any hints what could be wrong? Josef -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

9 years, 11 months

[opensuse-ruby] led display Suppliers shared photos with you

by led display Suppliers

Dear Mr/Miss, Still be puzzling about looking for best led display supplier? Now it will be miles easier working with KEROSA! Here you can find competitive price and excellent quality with a best mix. We"ve been in led display career for many years. We know your market and your country well. Our business is flexible which something is more likely to be a friend chat. We never waste your time. Our conversation will be very efficient base on our good communication. Please reply as soon as possible .if you are working on some led display project. We are ready to make you a satisfied offer! Samuel Shezhen Krosa Techology Co.,Ltd. Address: Building 3,Park,Guanguang road,Bao"an District,Shenzhen,China. post 518000

9 years, 11 months

[opensuse-ruby] -rvendor-specific doesn't exist in ruby 1.9 in Factory

by Tim Serong

Hi All, The devel:languages:ruby:extensions/ruby-fcgi build is failing ATM because: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.vtRX8Z ... + ruby -rvendor-specific install.rb config /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- vendor-specific (LoadError) from /usr/lib64/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' Our ruby 1.8 supported -rvendor-specific, but 1.9 apparently does not. Do we need this? Or can I just get rid of the "-rvendor-specific" bits from the ruby-fcgi spec file? (I'm not familiar with this option...) Thanks, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong(a)suse.com -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

9 years, 11 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

openSUSE Ruby June 2012