From: David Ekhaus <dekhaus@mac.com>
To: ruby.io.splice@librelist.org
Subject: Re: JRuby support
Date: Fri, 15 Mar 2013 19:52:26 -0700 [thread overview]
Message-ID: <E13B2C96-548E-46CE-A142-963E97197742@mac.com> (raw)
In-Reply-To: 20130316020511.GA17263@dcvr.yhbt.net
Fair enough (regarding the linux only comment) - here's what I get when I run
> ruby setup.rb
on RHEL 6.2 …
[root@localhost io_splice-4.2.0]# jruby setup.rb
---> lib
---> lib/io
---> lib/io/splice
<--- lib/io/splice
<--- lib/io
<--- lib
---> ext
---> ext/io_splice
/opt/torquebox-current/jruby/bin/jruby /opt/src/io_splice-4.2.0/ext/io_splice/extconf.rb
WARNING: JRuby does not support native extensions or the `mkmf' library very well.
Check http://kenai.com/projects/jruby/pages/Home for alternatives.
checking for splice() in fcntl.h... checking for tee() in fcntl.h... checking for rb_thread_blocking_region()... checking for F_GETPIPE_SZ in fcntl.h... no
checking for F_SETPIPE_SZ in fcntl.h... no
creating Makefile
<--- ext/io_splice
<--- ext
---> lib
---> lib/io
---> lib/io/splice
<--- lib/io/splice
<--- lib/io
<--- lib
---> ext
---> ext/io_splice
make
cc -shared -o io_splice_ext.so io_splice_ext.o -L"." -L"/opt/torquebox-2.1.2/jruby/lib" -m64
<--- ext/io_splice
<--- ext
rm -f InstalledFiles
---> lib
mkdir -p /opt/torquebox-2.1.2/jruby/lib/ruby/site_ruby/1.8/
---> lib/io
mkdir -p /opt/torquebox-2.1.2/jruby/lib/ruby/site_ruby/1.8/io
install splice.rb /opt/torquebox-2.1.2/jruby/lib/ruby/site_ruby/1.8/io
---> lib/io/splice
mkdir -p /opt/torquebox-2.1.2/jruby/lib/ruby/site_ruby/1.8/io/splice
install mri_18.rb /opt/torquebox-2.1.2/jruby/lib/ruby/site_ruby/1.8/io/splice
<--- lib/io/splice
<--- lib/io
<--- lib
---> ext
---> ext/io_splice
no ruby extention exists: 'ruby setup.rb setup' first
Try 'ruby setup.rb --help' for detailed usage.
The message …
"no ruby extension exists: 'ruby setup.rb setup' first"
leads me to believe that it the command 'jruby setup.rb' didn't work properly.
If it (the 'jruby setup.rb' command) did work properly - then can someone advise me on what the next step(s) are.
If it didn't - similarly, can someone advise me on what I need to do to get it to work.
Thanks
Dave
On Mar 15, 2013, at 7:05 PM, Eric Wong <normalperson@yhbt.net> wrote:
> David Ekhaus <dekhaus@mac.com> wrote:
>> Has anyone got io_splice working with JRuby ?
>>
>> Here are the errors from my mkmf.log - which were generated when I tried to run 'jruby setup.rb' …
>>
>> Davids-MacBook-Pro:io_splice dekhaus$ more mkmf.log
>
> ^^^^^^^^^^^^^^^^^^^^
> Uh... splice() is a Linux-only syscall.
>
> Anyways, I'm not interested in JRuby or anything JVM, but I'll accept
> non-intrusive patches to the C extension.
prev parent reply other threads:[~2013-03-16 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 0:48 JRuby support David Ekhaus
2013-03-16 2:05 ` Eric Wong
2013-03-16 2:52 ` David Ekhaus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/ruby_io_splice/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E13B2C96-548E-46CE-A142-963E97197742@mac.com \
--to=dekhaus@mac.com \
--cc=ruby.io.splice@librelist.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/ruby_io_splice.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).