unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Olivier FAURAX <olivier.faurax@anyces.com>
Cc: unicorn-public@bogomips.org
Subject: Re: Build error of 5.1.0 due to RString
Date: Mon, 7 Nov 2016 20:39:20 +0000	[thread overview]
Message-ID: <20161107203920.GA10287@starla> (raw)
In-Reply-To: <5ace6a20-e094-293d-93df-b557480e12d5@anyces.com>

Olivier FAURAX <olivier.faurax@anyces.com> wrote:
> It is about a RString that has not some members, so perhaps an API has been
> modified somewhere.

<snip>

> /opt/bitnami/apps/gitlab/htdocs/vendor/bundle/ruby/2.1.0/gems/unicorn-5.1.0/unicorn.gemspec
> Building native extensions.  This could take a while...
> /opt/bitnami/ruby/bin/ruby extconf.rb
> checking for SIZEOF_OFF_T in ruby.h... yes
> checking for SIZEOF_SIZE_T in ruby.h... yes
> checking for SIZEOF_LONG in ruby.h... yes

OK, ruby.h is there, so development headers exist...

> checking for rb_str_set_len() in ruby.h... no
> checking for rb_hash_clear() in ruby.h... no

These last two lines do not look right.  Can you show us your
mkmf.log file?  The output you originally posted is not enough
as it doesn't show the long compiler options and paths used.

Perhaps a library file is missing for static linking,
since these function checks require.

I'm not familiar with bitnami and how it builds/installs
Ruby, so maybe it's missing libruby*static.a or looking
in the wrong place somehow.

<snip> The failing code should've never been compiled
in the first place and should probably be removed.
However, the rb_hash_clear() detection is still necessary...

Thanks for reporting this.  You might want to loop in somebody
familiar with bitnami to poke around, too.

  reply	other threads:[~2016-11-07 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07 17:13 Build error of 5.1.0 due to RString Olivier FAURAX
2016-11-07 20:39 ` Eric Wong [this message]
2016-11-08  8:56   ` Olivier FAURAX
2016-11-08  9:43     ` Build error of 5.1.0 due to RString Eric Wong

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/unicorn/

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

  git send-email \
    --in-reply-to=20161107203920.GA10287@starla \
    --to=e@80x24.org \
    --cc=olivier.faurax@anyces.com \
    --cc=unicorn-public@bogomips.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/unicorn.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).