All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Straka <derek@asterius.io>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-ruby][PATCH] bundler: resolve build issues with RSS
Date: Mon, 27 Feb 2017 20:15:52 -0500	[thread overview]
Message-ID: <CADNbA1o1CR_yGUdW0FGLg78oB8O3q4WWzdqX++aLw5AUYdPZ3A@mail.gmail.com> (raw)
In-Reply-To: <CA+chaQcMcm3mkYNpMnHhvVw78TXBSzRihKa3so5am+Jbwd+sKQ@mail.gmail.com>

I'll take a look at the failure, but I may not get to it for a few days.
Feel free to drop it until I send a v2.

-Derek

On Mon, Feb 27, 2017 at 9:08 AM, Martin Jansa <martin.jansa@gmail.com>
wrote:

> Still fails in bitbake world:
>
> ERROR: bundler-1.9.4-r0 do_compile: Function failed: do_compile (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/i586-oe-linux/bundler/1.9.4-r0/temp/log.do_compile.3462)
> ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/i586-oe-linux/bundler/1.9.4-r0/temp/log.do_compile.3462
> Log data follows:
> | DEBUG: Executing shell function do_compile
> | ERROR:  Loading command: build (LoadError)
> | 	cannot load such file -- zlib
> | ERROR:  While executing gem ... (NoMethodError)
> |     undefined method `invoke_with_build_args' for nil:NilClass
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compile (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/i586-oe-linux/bundler/1.9.4-r0/temp/log.do_compile.3462)
> NOTE: recipe bundler-1.9.4-r0: task do_compile: Failed
> ERROR: Task (/home/jenkins/oe/world/shr-core/meta-openembedded/meta-ruby/recipes-devtools/ruby/bundler_git.bb:do_compile) failed with exit code '1'
>
>
> On Fri, Feb 24, 2017 at 8:41 PM, Derek Straka <derek@asterius.io> wrote:
>
>> Signed-off-by: Derek Straka <derek@asterius.io>
>> ---
>>  meta-ruby/recipes-devtools/ruby/bundler_git.bb | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta-ruby/recipes-devtools/ruby/bundler_git.bb
>> b/meta-ruby/recipes-devtools/ruby/bundler_git.bb
>> index f2d8f3c..2b5cef4 100644
>> --- a/meta-ruby/recipes-devtools/ruby/bundler_git.bb
>> +++ b/meta-ruby/recipes-devtools/ruby/bundler_git.bb
>> @@ -20,6 +20,8 @@ PV = "1.9.4"
>>
>>  S = "${WORKDIR}/git"
>>
>> +DEPENDS += "zlib"
>> +
>>  SRC_URI = " \
>>      git://github.com/bundler/bundler.git;branch=${BRANCH}
>> <http://github.com/bundler/bundler.git;branch=$%7BBRANCH%7D> \
>>      "
>> @@ -29,5 +31,3 @@ inherit ruby
>>  RDEPENDS_${PN} = "git"
>>
>>  BBCLASSEXTEND = "native"
>> -
>> -PNBLACKLIST[bundler] ?= "Fails to build with RSS
>> http://errors.yoctoproject.org/Errors/Details/130640/"
>> --
>> 2.7.4
>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
>


  reply	other threads:[~2017-02-28  1:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 19:41 [meta-ruby][PATCH] bundler: resolve build issues with RSS Derek Straka
2017-02-27 14:08 ` Martin Jansa
2017-02-28  1:15   ` Derek Straka [this message]
2017-02-28 21:25 Derek Straka

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=CADNbA1o1CR_yGUdW0FGLg78oB8O3q4WWzdqX++aLw5AUYdPZ3A@mail.gmail.com \
    --to=derek@asterius.io \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.