Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: Henning Heinold <heinold@inf.fu-berlin.de>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] classes/chrpath: trigger an error if chrpath fails
Date: Fri, 17 Aug 2012 11:53:51 +0100	[thread overview]
Message-ID: <502E22BF.4050809@communistcode.co.uk> (raw)
In-Reply-To: <20120817102638.GD17007@mi.fu-berlin.de>

On 17/08/12 11:26, Henning Heinold wrote:
> On Fri, Aug 17, 2012 at 11:05:43AM +0100, Jack Mitchell wrote:
>> any provider
>> WARNING: Failed to fetch URL http://kernel.org/pub/linux/kernel/people/jsipek/guilt/guilt-0.33.tar.gz,
>> attempting MIRRORS if available
>> *ERROR: chrpath command failed with exit code 7
>> ERROR: chrpath command failed with exit code 7*
>
> Hi,
>
> you can grep the logfiles in the work-dir for chrpath call and you will find the package. I saw it on some perl modules, but not now.
>
> Bye Henning

Ok, here we go:

    x86_64-linux/perl-native-5.14.2-r1/temp/log.do_populate_sysroot.30355:ERROR:
    chrpath command failed with exit code 7
    x86_64-linux/perl-native-5.14.2-r1/temp/log.do_populate_sysroot.30355:ERROR:
    chrpath command failed with exit code 7

This is on kraj/toolchain-rework, I don't know how synced with master it 
is so apologies if it has already been fixed.


-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  reply	other threads:[~2012-08-17 11:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 16:44 [PATCH] classes/chrpath: trigger an error if chrpath fails Paul Eggleton
2012-08-16 17:06 ` Saul Wold
2012-08-16 17:13 ` Paul Eggleton
2012-08-17  9:53   ` Richard Purdie
2012-08-17 10:05     ` Jack Mitchell
2012-08-17 10:26       ` Henning Heinold
2012-08-17 10:53         ` Jack Mitchell [this message]
2012-08-17 13:31           ` Paul Eggleton
2012-08-17 16:46             ` Richard Purdie
2012-08-18  0:39     ` Khem Raj
2012-08-17 10:03   ` Phil Blundell

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=502E22BF.4050809@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=heinold@inf.fu-berlin.de \
    --cc=openembedded-core@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