Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001103]: Ruby compile breaks on the "socket" routine
Date: Mon, 24 Sep 2007 02:06:21 -0700	[thread overview]
Message-ID: <e091900952a3fb6232e155593d64ac06@busybox.net> (raw)


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1103 
====================================================================== 
Reported By:                znmeb
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   1103
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             11-25-2006 22:08 PST
Last Modified:              09-24-2007 02:06 PDT
====================================================================== 
Summary:                    Ruby compile breaks on the "socket" routine
Description: 
When compiling on an IPV6 aware system, Ruby's configure step enables use
of IPV6 in compiling "socket.c". However, on the Buildroot system, this
compile fails:

make[2]: Leaving directory
`/data1/GenericBuildroot/buildroot/build_i386/ruby-1.8.5/ext/sdbm'
compiling socket

Fatal: --enable-ipv6 is specified, and your OS seems to support IPv6
feature.
But your getaddrinfo() and getnameinfo() are appeared to be broken. 
Sorry,
you cannot compile IPv6 socket classes with broken these functions.
You can try --enable-wide-getaddrinfo.
compiling stringio
make[2]: Entering directory
`/data1/GenericBuildroot/buildroot/build_i386/ruby-1.8.5/ext/stringio'


Adding the line

    --disable-ipv6 \

in the configure step of buildroot/package/ruby/ruby.mk fixes this.
====================================================================== 

---------------------------------------------------------------------- 
 bernhardf - 09-24-07 02:06  
---------------------------------------------------------------------- 
Does this work fine with uClibc-0.9.29 (the current release) and a current
ruby? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-25-06 22:08  znmeb          New Issue                                    
11-25-06 22:08  znmeb          Status                   new => assigned     
11-25-06 22:08  znmeb          Assigned To               => uClibc          
11-25-06 22:08  znmeb          Issue Monitored: znmeb                       
02-12-07 05:34  vapier         Assigned To              uClibc => buildroot 
09-24-07 02:06  bernhardf      Note Added: 0002785                          
======================================================================

             reply	other threads:[~2007-09-24  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24  9:06 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-12 13:34 [Buildroot] [buildroot 0001103]: Ruby compile breaks on the "socket" routine bugs at busybox.net

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

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

  git send-email \
    --in-reply-to=e091900952a3fb6232e155593d64ac06@busybox.net \
    --to=bugs@busybox.net \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox