search for: libruby

...d. /home/eumario/.themes/Clearlooks-Vista/gtk-2.0/gtkrc:56: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1211709760 (LWP 17294)] 0xb7e49010 in Init_heap () from /usr/lib/libruby.so.1.8 (gdb) whe #0 0xb7e49010 in Init_heap () from /usr/lib/libruby.so.1.8 #1 0xb7e48b21 in Init_heap () from /usr/lib/libruby.so.1.8 #2 0xb7a3f766 in DoGCMarkItemData () from /usr/lib/ruby/site_ruby/1.8/i586-linux-gnu/wxruby2.so #3 0xb7a3dd88 in RecurseOverTreeIds () from /usr/lib/ruby/...

Hi I''d like to put out a 1.9.3 release perhaps later this week/weekend. If you have a chance to test the build and samples esp with latest rubygems, please do. There are still some bugs on the list, and samples to do, but this should address all the build/install probs that have come up. And it would be good to get some testing and feedback on some of the new classes. A note on the

Hi, this small series cherry-picks a couple of the portability fixes recently done in libguestfs to hivex. There should be no actual change on Linux. Thanks, -- Pino Pino Toscano (2): normalize iconv handling ruby: fix detection of ruby library bootstrap | 1 + configure.ac | 8 +++++++- lib/utf16.c | 3 +-- 3 files changed, 9 insertions(+), 3 deletions(-) -- 1.9.3

Hi, I just downloaded the svn version of libtorrent-ruby Previously I installed libtorrent But when I run "ruby setup ruby" it returns me: xan at servidor:~/provar/torrentkeeper-per-installar/2-libruby/libtorrent- ruby/trun k$ ruby setup.rb ---> ext ---> ext/libtorrent /usr/bin/ruby1.8 /home/xan/provar/torrentkeeper-per-installar/2- libruby/libtorre nt-ruby/trunk/ext/libtorrent/extconf.rb checking for main() in -ltorrent... *** /home/xan/provar/torrentkeeper- per-insta llar/2-libruby/libtor...

Hi, I installed libtorrent-0.11.tar.gz in my system (ubuntu) and now I want to install libtorrent-ruby but it does not works: I downloaded svn version and I run: xan at rulot:~/provar/2-libruby/libtorrent-ruby/trunk$ ruby setup.rb ---> ext ---> ext/libtorrent /usr/bin/ruby1.8 /home/xan/provar/2-libruby/libtorrent-ruby/trunk/ext/libtorrent /extconf.rb checking for main() in -ltorrent... yes checking for swig... yes generating libtorrent wrapper... *** /home/xan/provar/2-libruby/lib...

...or package: ruby-augeas-0.4.1-1.el6.x86_64 --> Processing Dependency: libaugeas.so.0(AUGEAS_0.8.0)(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64 --> Processing Dependency: libaugeas.so.0(AUGEAS_0.12.0)(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64 --> Processing Dependency: libruby.so.1.8()(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64 --> Processing Dependency: libaugeas.so.0()(64bit) for package: ruby-augeas-0.4.1-1.el6.x86_64 ---> Package ruby-shadow.x86_64 0:1.4.1-13.el6 will be installed --> Processing Dependency: ruby(abi) = 1.8 for package: ruby-sha...

Query RbConfig::CONFIG for "libdir", and use that when trying to link to the ruby library. This fixes the libruby detection when it is installed in a non-standard library directory. (This is the same change as 3d02e53c48266669675cc237f61ae2c4e1816e66 in libguestfs.) --- configure.ac | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 3d85afe..554ff87 1...

...tected *** irb: double free or corruption (fasttop): 0x0a51d6c0 *** ======= Backtrace: ========= /lib/libc.so.6[0x638ac1] /lib/libc.so.6(cfree+0x90)[0x63c0f0] /usr/lib/ruby/gems/gems/ferret-0.11.4/lib/ferret_ext.so[0x247d75] /usr/lib/ruby/gems/gems/ferret-0.11.4/lib/ferret_ext.so[0x219745] /usr/lib/libruby.so.1.8(rb_gc_call_finalizer_at_exit+0xa7)[0xc3e237] /usr/lib/libruby.so.1.8[0xc239e7] /usr/lib/libruby.so.1.8(ruby_cleanup+0x100)[0xc2c280] /usr/lib/libruby.so.1.8(ruby_stop+0x1d)[0xc2c3ad] /usr/lib/libruby.so.1.8[0xc372c1] irb[0x804868d] /lib/libc.so.6(__libc_start_main+0xe0)[0x5e5390] irb[0x80485...

These three patches ought to fix configure script detection of Ruby, especially on Debian where the Ruby C extensions library can be something like '-lruby1.8'. Rich.

This fixes the wxRED Mac link error. Thanks to Nick for pointing out that I hadn''t removed some wxRED code related to an earlier experiment. Hopefully this one will build on Mac, end-to-end. I also found and fixed a problem that was causing the crash on exit: wxWindows automatically deletes the C++ app object as soon as the last frame is closed. Later, when ruby garbage collected the

...3.0 for apache2 on Ubuntu 10.10. It says that I need to install libopenssl-ruby. But when I did ''sudo apt-get install libopenssl-ruby'', I got the following error. Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting ''libruby'' instead of ''libopenssl-ruby'' libruby is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded. How do I install libopenssl-ruby? Thanks. Sam -- Posted via http://www.ruby-forum.com/. -- You received this message because you are...

I needed to add a few patches to be able to build libguestfs 1.20.2 out of tree. Mostly srcdir/builddir issues -- I think that I had posted something for building the daemon before. As mentioned on IRC, I found that compiling (Ruby bindings) caused config.h file shipped with the Ruby headers to be included rather than ${builddir}/config.h. This can be fixed because the relevant checks can be

...ot;] and Config::CONFIG["LIBS"] contains the right values? Here is a grep of the config hash -- shs@cybert /store/download/wxruby-2.0.1 $ grep -r ''CONFIG\['' * rake/rakemswin.rb:lib_ruby = File.join(Config::CONFIG[''libdir''], Config::CONFIG[''LIBRUBY'']) rake/rakemswin.rb: mv ''msvcp80.dll'', Config::CONFIG[''bindir''] rake/rakemswin.rb: mv ''msvcr80.dll'', Config::CONFIG[''bindir''] rake/rakemswin.rb: ruby_manifest = File.join(Config::CONFIG[''bindir''],...

Hi, I''m having a weird issue and was wondering if anyone else had run into it. I recently upgraded from puppet 2.7 -> 3.0.1 After cleaning up some gems on my puppet master everything seemed to be working ok. I had originally used the EPEL repo''s to deploy puppet, but switched to the Puppet Labs repos so I could upgrade to 2.7 then 3. On RHEL5 only, I get a RSTRING_PTR

...t;/usr/local/pgsql/lib" -L"/usr/lib" -o postgres.so postgres.o -lruby -lpq -lnsl -lpthread -ldl -lcrypt -lm -lc # make install /usr/bin/install -c -m 0755 postgres.so /usr/lib/ruby/site_ruby/1.8/ i386-linux # ldd ./postgres.so linux-gate.so.1 => (0x0091b000) libruby.so.1.8 => /usr/lib/libruby.so.1.8 (0x00ef8000) libpq.so.5 => /usr/local/pgsql/lib/libpq.so.5 (0x009b7000) libnsl.so.1 => /lib/libnsl.so.1 (0x0085d000) libpthread.so.0 => /lib/libpthread.so.0 (0x00110000) libdl.so.2 => /lib/libdl.so.2 (0x00b1f000)...

...Ruby-1.8.4, I added gcc to the environment using "gcc=/usr/local/bin/gcc" & "export gcc". I have run ./configure successfully. Then when I run "make" under Ruby-1.8.4, it gives me make: Warning: Illegal dependency list for target `.DEFAULT'' gcc main.o libruby-static.a -ldl -lcrypt -lm -o miniruby -g -O2 -DRUBY_EXPORT Undefined first referenced symbol in file Init_ext libruby-static.a(ruby.o) ld: fatal: Symbol referencing errors. No output written to miniruby collect2: ld returned 1 exit status **...

Still fairly new to Ruby and Rails in general and trying to figure out how to address this error. I recently migrated to a new computer and now I get this error message when I try to start the rails server. -bash: /Users/user1/.rvm/gems/ruby-1.9.3-p125/bin/rails: /Users/user/.rvm/rubies/ruby-1.9.3-p125/bin/ruby: bad interpreter: No such file or directory I know what the problem is and

I''m getting the following on OS X (under locomotive) when running the tests for ferret. Is anybody else getting this error? rm -f ext/mem_pool.* rm -f ext/defines.h ** Execute test_units /Applications/Locomotive/Bundles/rmagickRailsJan2007_x86.locobundle/framework/bin/ruby -Ilib:test/unit

Here are three patches that fix issues with out-of-tree building and one that uses Ruby's own autoconf stuff for determining how Ruby bindings should be built. Cheers, -Hilko

This commit starts to split our massive, monolithic configure.ac file into smaller files, using the m4_include mechanism to combine them. I don't know if we should really do this, so I'm open to comments about it. However: - Our configure.ac script is 1800+ lines long, and that's pretty long. - configure.ac lacks structure; splitting it up might improve that. - From what I read,