kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Mohit Chawla <>
Subject: kgio 2.5.0 failed build/install
Date: Sat, 25 Jun 2011 00:42:16 +0530	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


Seeing this on CentOS 5.6:

### build error

Building native extensions.  This could take a while...
ERROR:  Error installing kgio:
       ERROR: Failed to build gem native extension.

       /usr/bin/ruby extconf.rb
checking for CLOCK_MONOTONIC in "time.h"... yes
checking for clockid_t... yes
checking for clock_gettime() in -lrt... no
checking for t_open() in -lnsl... no
checking for socket() in -lsocket... no
checking for poll()... no
checking for getaddrinfo()... no
getaddrinfo required
*** extconf.rb failed ***

### mkmf.log

have_func: checking for getaddrinfo()... -------------------- no

"gcc -o conftest -I. -I/usr/lib64/ruby/1.8 -I.    -D_GNU_SOURCE
-DPOSIX_C_SOURCE=1-D_POSIX_C_SOURCE=200112L -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -fno-strict-aliasing
-fPIC   conftest.c  -L/usr/lib64      -lruby-static  -lpthread -lrt
-ldl -lcrypt -lm   -lc"
conftest.c: In function ‘t’:
conftest.c:7: error: too few arguments to function ‘getaddrinfo’
checked program was:
/* begin */
1: #include <sys/types.h>
2: #include <sys/socket.h>
3: #include <netdb.h>
5: /*top*/
6: int main() { return 0; }
7: int t() { getaddrinfo(); return 0; }
/* end */

No such issues on my Ubuntu/Scientific Linux 6/CentOS 5.5 boxes. Any
clues what could be the reason ?

       reply	other threads:[~2011-06-24 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 19:12 Mohit Chawla [this message]
2011-06-24 19:40 ` kgio 2.5.0 failed build/install Mohit Chawla
2011-06-24 20:50 ` Eric Wong
2011-06-25  6:32   ` Mohit Chawla

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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

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).