Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Henri Bragge <henri.bragge@dcombus.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: numerous &quot; strip command failed&quot; ERRORs in building beagle image
Date: Fri, 4 Jun 2010 08:27:00 +0000 (UTC)	[thread overview]
Message-ID: <loom.20100604T102513-753@post.gmane.org> (raw)
In-Reply-To: 4BED7085.9020608@zenlinux.com

Scott Garman <sgarman <at> zenlinux.com> writes:

> This happens in the do_package task of many of the kernel builds. I was 
> looking into it just the other night as it triggers BuildBot to think 
> that the build failed (because it sees a non-zero exit status from this 
> section).
> 
> Is it even necessary to stage the kernel scripts/ directory? That's the 
> final thing happening in the do_install task in kernel.bbclass. Removing 
> that line would be a one-liner patch fix to this issue.

Has there been, or will there ever be any progress on this? Just asking if I
should work around this on my own build system..

- Henri





      reply	other threads:[~2010-06-04  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14 10:00 numerous "strip command failed" ERRORs in building beagle image Robert P. J. Day
2010-05-14 15:47 ` Scott Garman
2010-06-04  8:27   ` Henri Bragge [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

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

  git send-email \
    --in-reply-to=loom.20100604T102513-753@post.gmane.org \
    --to=henri.bragge@dcombus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox