Date   

[meta-baryon][PATCH 1/1] nfs-utils: workaround for nfsd regression in the 3.4 kernel

Kevin Strasser <kevin.strasser@...>
 

The version of nfsd used in 3.4 kernels tries to upcall the
new reboot-recovery daemon and gets stuck if it is not found.
This causes client mounts to fail and prints the following
error message during boot:

"NFSD: starting 90-second grace period
NFSD: Unable to end grace period: -110"

If the directory "/var/lib/nfs/v4recovery" exists, nfsd will
revert back to the old method.

Signed-off-by: Kevin Strasser <kevin.strasser@...>
---
.../nfs-utils/nfs-utils_1.2.3.bbappend | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend

diff --git a/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend b/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend
new file mode 100644
index 0000000..2c91a93
--- /dev/null
+++ b/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend
@@ -0,0 +1,8 @@
+PR = "r5"
+
+# Work around linux 3.4 nfsd regression
+do_install_prepend () {
+ install -d ${D}/var/lib/nfs/v4recovery
+}
+
+FILES_${PN} += "/var/lib/nfs/v4recovery"
--
1.7.9.5


[meta-baryon][PATCH 0/1] nfs regression workaround

Kevin Strasser <kevin.strasser@...>
 

The new recovery mechanism used by nfs in 3.4 kernels is currently
failing when building baryon against poky 1.3_M3. This workaround
causes nfs to revert back to the old recovery mechanism.

The issue is discussed in more detail here:
https://lkml.org/lkml/2012/6/11/243

The following changes since commit e4efadec4a1ded0a66fa67c7cca868b7a4b6221b:

talloc: specify the version of LGPL and include the license text (2012-09-27 16:54:08 -0700)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib strassek/baryon-nfsd-regression
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=strassek/baryon-nfsd-regression

Kevin Strasser (1):
nfs-utils: workaround for nfsd regression in the 3.4 kernel

.../nfs-utils/nfs-utils_1.2.3.bbappend | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend

--
1.7.9.5


Re: The term Package as used in the YP docs

Trevor Woerner
 

On Fri, Sep 28, 2012 at 2:34 PM, Paul Eggleton
<paul.eggleton@...> wrote:
On Friday 28 September 2012 11:27:37 Rudolf Streif wrote:
Unfortunately, changing variables like P, PN, PV, PR etc.
may cause some pain. If a transition is what the broader community would
like to achieve then a period where old and new variables can be used
interchangeably (if possible) would be the way to go.
I'm not sure there's a huge amount to be gained by doing this when weighed
against the cost - it would certainly cause a massive amount of churn, with
the potential for problems with layer interaction where one layer has done the
big rename and another that bbappends recipes in the first hasn't.
Not that it matters in the grand scheme of things, but I would be in
favour of switching the variable names. Consistency is as consistency
does; if there's any hope people can stop confusing "poky" for
"yocto", "yocto" with "the yocto project", and "packages" for
"recipes" then it needs to be pervasively correct.

Provided the Yocto Project continues to grow, changes like this only
get harder with time, and if the project gets bigger (i.e. more uses)
the confusion only spreads further the longer it is left unchecked.

In any case I applaud all the efforts to standardize the wording,
especially in the documentation. As such I think it would be quite
helpful to have the proposed historical note included. Hopefully, the
sooner newcomers are aware of the issue, the less they're likely to
trip up over it.


Re: The term Package as used in the YP docs

Tim Bird <tim.bird@...>
 

On 09/28/2012 11:44 AM, Rudolf Streif wrote:
I am not advocating changing the variable names. I know that this is a huge undertaking and prone to many problems. This probably one of the many legacy things people will have to live with and
understand. In most cases recipe name and version exactly reflect the name and version of the package it is intended to build which to some extend mitigates the issue.

As far as the Terms section in the manuals is concerned, I see that you already changed the describing text for the variables. That's sufficient, I think.
(I answered Scott privately by mistake - here's some feedback on-list)

I'm in favor of mentioning the history somewhere, because the names
do have a 'P' in them, and this is confusing otherwise.

Overall, I think the new wording is worthwhile.
-- Tim

=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================


Re: The term Package as used in the YP docs

Rifenbark, Scott M <scott.m.rifenbark@...>
 

Rudolf,

 

This is good feedback on the descriptions for the variable names Rudolf.  I did try and clean things up there a bit.

 

Thanks,

Scott

 

From: rstreif@... [mailto:rstreif@...] On Behalf Of Rudolf Streif
Sent: Friday, September 28, 2012 11:45 AM
To: Rifenbark, Scott M
Cc: Paul Eggleton; yocto@...
Subject: Re: [yocto] The term Package as used in the YP docs

 

I am not advocating changing the variable names. I know that this is a huge undertaking and prone to many problems. This probably one of the many legacy things people will have to live with and understand. In most cases recipe name and version exactly reflect the name and version of the package it is intended to build which to some extend mitigates the issue.

 

As far as the Terms section in the manuals is concerned, I see that you already changed the describing text for the variables. That's sufficient, I think.

 

:rjs

On Fri, Sep 28, 2012 at 11:37 AM, Rifenbark, Scott M <scott.m.rifenbark@...> wrote:

I have tried to weed out the ambiguous use of "package" for this upcoming version of the manual set.  I don't think I would want to suggest changing any of the "P*" type variable names in the code.  I agree with Paul here that the potential for really messing things up out-weighs any other benefit.  This is why I was trying to worm in a bit of history behind those names for the people that might struggle like me.

Scott


-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Paul Eggleton
Sent: Friday, September 28, 2012 11:34 AM
To: Rudolf Streif
Cc: yocto@...
Subject: Re: [yocto] The term Package as used in the YP docs

On Friday 28 September 2012 11:27:37 Rudolf Streif wrote:
> +1
>
> I agree with Scott's definition. In the general Linux context a Package is
> a compilation of binaries, documentation, development files, etc. wrapped
> up in a format that can be used by a package management system to install
> it on a target system.

No dispute there.

> It is somewhat confusing that YP and OE use the term 'package' synonymously
> with 'recipe'. In most cases a package is the output of a recipe.

The thing is, we no longer do that - we've fixed a number of references in the
documentation, help text and error messages for this release so that "recipe"
is used when that's what we mean. If we've left any references that should be
considered a bug.

> Unfortunately, changing variables like P, PN, PV, PR etc.
> may cause some pain. If a transition is what the broader community would
> like to achieve then a period where old and new variables can be used
> interchangeably (if possible) would be the way to go.

I'm not sure there's a huge amount to be gained by doing this when weighed
against the cost - it would certainly cause a massive amount of churn, with
the potential for problems with layer interaction where one layer has done the
big rename and another that bbappends recipes in the first hasn't.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre

_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

 


Re: The term Package as used in the YP docs

Rudolf Streif <rudolf.streif@...>
 

I am not advocating changing the variable names. I know that this is a huge undertaking and prone to many problems. This probably one of the many legacy things people will have to live with and understand. In most cases recipe name and version exactly reflect the name and version of the package it is intended to build which to some extend mitigates the issue.

As far as the Terms section in the manuals is concerned, I see that you already changed the describing text for the variables. That's sufficient, I think.

:rjs


On Fri, Sep 28, 2012 at 11:37 AM, Rifenbark, Scott M <scott.m.rifenbark@...> wrote:
I have tried to weed out the ambiguous use of "package" for this upcoming version of the manual set.  I don't think I would want to suggest changing any of the "P*" type variable names in the code.  I agree with Paul here that the potential for really messing things up out-weighs any other benefit.  This is why I was trying to worm in a bit of history behind those names for the people that might struggle like me.

Scott

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Paul Eggleton
Sent: Friday, September 28, 2012 11:34 AM
To: Rudolf Streif
Cc: yocto@...
Subject: Re: [yocto] The term Package as used in the YP docs

On Friday 28 September 2012 11:27:37 Rudolf Streif wrote:
> +1
>
> I agree with Scott's definition. In the general Linux context a Package is
> a compilation of binaries, documentation, development files, etc. wrapped
> up in a format that can be used by a package management system to install
> it on a target system.

No dispute there.

> It is somewhat confusing that YP and OE use the term 'package' synonymously
> with 'recipe'. In most cases a package is the output of a recipe.

The thing is, we no longer do that - we've fixed a number of references in the
documentation, help text and error messages for this release so that "recipe"
is used when that's what we mean. If we've left any references that should be
considered a bug.

> Unfortunately, changing variables like P, PN, PV, PR etc.
> may cause some pain. If a transition is what the broader community would
> like to achieve then a period where old and new variables can be used
> interchangeably (if possible) would be the way to go.

I'm not sure there's a huge amount to be gained by doing this when weighed
against the cost - it would certainly cause a massive amount of churn, with
the potential for problems with layer interaction where one layer has done the
big rename and another that bbappends recipes in the first hasn't.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: The term Package as used in the YP docs

Rifenbark, Scott M <scott.m.rifenbark@...>
 

I have tried to weed out the ambiguous use of "package" for this upcoming version of the manual set. I don't think I would want to suggest changing any of the "P*" type variable names in the code. I agree with Paul here that the potential for really messing things up out-weighs any other benefit. This is why I was trying to worm in a bit of history behind those names for the people that might struggle like me.

Scott

-----Original Message-----
From: yocto-bounces@... [mailto:yocto-bounces@...] On Behalf Of Paul Eggleton
Sent: Friday, September 28, 2012 11:34 AM
To: Rudolf Streif
Cc: yocto@...
Subject: Re: [yocto] The term Package as used in the YP docs

On Friday 28 September 2012 11:27:37 Rudolf Streif wrote:
+1

I agree with Scott's definition. In the general Linux context a Package is
a compilation of binaries, documentation, development files, etc. wrapped
up in a format that can be used by a package management system to install
it on a target system.
No dispute there.

It is somewhat confusing that YP and OE use the term 'package' synonymously
with 'recipe'. In most cases a package is the output of a recipe.
The thing is, we no longer do that - we've fixed a number of references in the
documentation, help text and error messages for this release so that "recipe"
is used when that's what we mean. If we've left any references that should be
considered a bug.

Unfortunately, changing variables like P, PN, PV, PR etc.
may cause some pain. If a transition is what the broader community would
like to achieve then a period where old and new variables can be used
interchangeably (if possible) would be the way to go.
I'm not sure there's a huge amount to be gained by doing this when weighed
against the cost - it would certainly cause a massive amount of churn, with
the potential for problems with layer interaction where one layer has done the
big rename and another that bbappends recipes in the first hasn't.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto


Re: The term Package as used in the YP docs

Paul Eggleton
 

On Friday 28 September 2012 11:27:37 Rudolf Streif wrote:
+1

I agree with Scott's definition. In the general Linux context a Package is
a compilation of binaries, documentation, development files, etc. wrapped
up in a format that can be used by a package management system to install
it on a target system.
No dispute there.

It is somewhat confusing that YP and OE use the term 'package' synonymously
with 'recipe'. In most cases a package is the output of a recipe.
The thing is, we no longer do that - we've fixed a number of references in the
documentation, help text and error messages for this release so that "recipe"
is used when that's what we mean. If we've left any references that should be
considered a bug.

Unfortunately, changing variables like P, PN, PV, PR etc.
may cause some pain. If a transition is what the broader community would
like to achieve then a period where old and new variables can be used
interchangeably (if possible) would be the way to go.
I'm not sure there's a huge amount to be gained by doing this when weighed
against the cost - it would certainly cause a massive amount of churn, with
the potential for problems with layer interaction where one layer has done the
big rename and another that bbappends recipes in the first hasn't.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: The term Package as used in the YP docs

Rudolf Streif <rudolf.streif@...>
 

+1

I agree with Scott's definition. In the general Linux context a Package is a compilation of binaries, documentation, development files, etc. wrapped up in a format that can be used by a package management system to install it on a target system.

It is somewhat confusing that YP and OE use the term 'package' synonymously with 'recipe'. In most cases a package is the output of a recipe.

I am all for making this more consistent at least to start with in the documentation. Unfortunately, changing variables like P, PN, PV, PR etc. may cause some pain. If a transition is what the broader community would like to achieve then a period where old and new variables can be used interchangeably (if possible) would be the way to go.

:rjs 


On Fri, Sep 28, 2012 at 11:14 AM, Rifenbark, Scott M <scott.m.rifenbark@...> wrote:

This post will have some strong opinions and responses.  But, I want to throw this out as a re-write of the term “Package” as defined in the YP Development Manual’s “Terms” section.  I gave this a shot based on my brief understanding and on some email that was tossed about a while back on the term.  What I would like to ultimately come up with is a definition that works for the term as we want to use it in the YP docs and also as an explanation for some of our older variable names like PR, PV, and so forth that really refer to recipes.  Please thrash over it….

 

·         Package: In the context of the Yocto Project, this term refers to the packaged output from a baked recipe. A package is generally the compiled binaries produced from the recipe's sources. You ‘bake’ something by running it through BitBake.

It is worth noting that the term "package" can, in general, have subtle meanings. For example, the packages refered to in the "The Packages" section are compiled binaries that when installed add functionality to your Linux distribution.

Another point worth noting is that historically within the Yocto Project, recipes were referred to as packages - thus, the existence of several BitBake variables that are seemingly mis-named, (e.g. PR, PRINC, PV, and PE).

 

 

Scott Rifenbark

Intel Corporation

Yocto Project Documentation

503.712.2702

503.341.0418 (cell)

 


_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto



Re: The term Package as used in the YP docs

Rifenbark, Scott M <scott.m.rifenbark@...>
 

Paul,

Thanks for the clarification on the host packages. Maybe I should rewrite "The Packages" section to use that term. That seems best. I guess the reason I wanted to explain the weird variable names was because they caused me a lot of angst as I tried to figure things out. Maybe this is not so for others. I certainly don't need to provide a history lesson if I am the minority.

Scott

-----Original Message-----
From: Paul Eggleton [mailto:paul.eggleton@...]
Sent: Friday, September 28, 2012 11:23 AM
To: Rifenbark, Scott M
Cc: yocto@...
Subject: Re: [yocto] The term Package as used in the YP docs

Hi Scott,

On Friday 28 September 2012 18:14:31 Rifenbark, Scott M wrote:
* Package: In the context of the Yocto Project, this term refers to
the packaged output from a baked recipe. A package is generally the
compiled binaries produced from the recipe's sources. You 'bake' something
by running it through BitBake.

It is worth noting that the term "package" can, in general, have subtle
meanings. For example, the packages refered to in the "The
Packages<http://www.yoctoproject.org/docs/1.3/yocto-project-qs/yocto-projec
t-qs.html#packages>" section are compiled binaries that when installed add
functionality to your Linux distribution.
The thing is, this is actually the same meaning, we're just talking about
packages for your host distribution rather than packages for the custom distro
you're building - the concept is the same. If we do need to clarify it I would
suggest using the term "host package" or something very similar for packages
to be installed as pre-requisites on the host system.

Another point worth noting is that historically within the Yocto Project,
recipes were referred to as packages - thus, the existence of several
BitBake variables that are seemingly mis-named, (e.g.
PR<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
l#var-PR>,
PRINC<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.
html#var-PRINC>,
PV<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
l#var-PV>, and
PE<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
l#var-PE>).
I have to say, whilst this is an interesting point of history, I'm not sure
anyone really needs to know this in the manual, particularly if we've replaced
all historical use of the word "package" when we mean "recipe" (as I think we
now have for this release).

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: The term Package as used in the YP docs

Paul Eggleton
 

Hi Scott,

On Friday 28 September 2012 18:14:31 Rifenbark, Scott M wrote:
* Package: In the context of the Yocto Project, this term refers to
the packaged output from a baked recipe. A package is generally the
compiled binaries produced from the recipe's sources. You 'bake' something
by running it through BitBake.

It is worth noting that the term "package" can, in general, have subtle
meanings. For example, the packages refered to in the "The
Packages<http://www.yoctoproject.org/docs/1.3/yocto-project-qs/yocto-projec
t-qs.html#packages>" section are compiled binaries that when installed add
functionality to your Linux distribution.
The thing is, this is actually the same meaning, we're just talking about
packages for your host distribution rather than packages for the custom distro
you're building - the concept is the same. If we do need to clarify it I would
suggest using the term "host package" or something very similar for packages
to be installed as pre-requisites on the host system.

Another point worth noting is that historically within the Yocto Project,
recipes were referred to as packages - thus, the existence of several
BitBake variables that are seemingly mis-named, (e.g.
PR<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
l#var-PR>,
PRINC<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.
html#var-PRINC>,
PV<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
l#var-PV>, and
PE<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
l#var-PE>).
I have to say, whilst this is an interesting point of history, I'm not sure
anyone really needs to know this in the manual, particularly if we've replaced
all historical use of the word "package" when we mean "recipe" (as I think we
now have for this release).

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


The term Package as used in the YP docs

Rifenbark, Scott M <scott.m.rifenbark@...>
 

This post will have some strong opinions and responses.  But, I want to throw this out as a re-write of the term “Package” as defined in the YP Development Manual’s “Terms” section.  I gave this a shot based on my brief understanding and on some email that was tossed about a while back on the term.  What I would like to ultimately come up with is a definition that works for the term as we want to use it in the YP docs and also as an explanation for some of our older variable names like PR, PV, and so forth that really refer to recipes.  Please thrash over it….

 

·         Package: In the context of the Yocto Project, this term refers to the packaged output from a baked recipe. A package is generally the compiled binaries produced from the recipe's sources. You ‘bake’ something by running it through BitBake.

It is worth noting that the term "package" can, in general, have subtle meanings. For example, the packages refered to in the "The Packages" section are compiled binaries that when installed add functionality to your Linux distribution.

Another point worth noting is that historically within the Yocto Project, recipes were referred to as packages - thus, the existence of several BitBake variables that are seemingly mis-named, (e.g. PR, PRINC, PV, and PE).

 

 

Scott Rifenbark

Intel Corporation

Yocto Project Documentation

503.712.2702

503.341.0418 (cell)

 


Re: build failure on current

Evade Flow <evadeflow@...>
 

Just to bring this full circle: I finally got the CRC error on my Ubuntu
10.04 build server to go away by adding the following line to
/etc/apt/sources.list:

deb http://archive.ubuntu.com/ubuntu lucid-updates main universe restricted

and then executing:

sudo apt-get install gzip

to update gzip. Thanks, Paul, for all of your help in tracking this
down...

On Fri, Sep 28, 2012 at 12:34 PM, Evade Flow <evadeflow@...> wrote:
Is it definitely tar that's the problem or gzip? ...
Oh! Didn't even think of that. :-% Looks like it's gzip:

evadeflow% gzip -d perl-5.14.2.tar.gz

gzip: perl-5.14.2.tar.gz: invalid compressed data--crc error


Nice find! I'll see about updating my gzip...


On Fri, Sep 28, 2012 at 12:00 PM, Paul Eggleton
<paul.eggleton@...> wrote:
On Friday 28 September 2012 11:53:53 Evade Flow wrote:
Erm... that *specific* bit prints nothing when pasted into a file and
executed. (Is it really supposed to?)
No, but the rest of the script (the bit following the blank line that
you've omitted) is...
My bad, sorry. (I really need to read more carefully.) Here's what I get
when I add the missing lines:

evadeflow% cat > temp.sh
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}

# Tar version 1.24 and onwards handle overwriting symlinks correctly
# but earlier versions do not; this needs to work properly for sstate
float_test "$TARVERSION > 1.23" && needtar="0"
echo $needtar
evadeflow% chmod +x temp.sh
evadeflow% ./temp.sh
1

So... it correctly determines that it needs to build tar, but... the built
tar can't unpack the tarball from CPAN:

evadeflow% wget http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
--2012-09-28 11:46:13-- http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
Resolving usaprox1.lightning.com... 10.102.184.7
Connecting to usaprox1.lightning.com|10.102.184.7|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 15223598 (15M) [application/x-gzip]
Saving to: `perl-5.14.2.tar.gz'

100%[================================================================>]
15,223,598 62.2M/s in 0.2s

2012-09-28 11:46:13 (62.2 MB/s) - `perl-5.14.2.tar.gz' saved
[15223598/15223598]

evadeflow% ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar xf
perl-5.14.2.tar.gz

gzip: stdin: invalid compressed data--crc error
./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Child returned status
1 ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Error is not
recoverable: exiting now


Weird. Anyway, I have a workaround, so it's not a big deal--especially given
that Ubuntu 10.04 isn't officially supported. I'm happy to run any other
tests you can think of to hunt down the cause of this (I've got a pretty
fast build mchine now), but I totally understand if you've got bigger fish
to fry at the moment...
Is it definitely tar that's the problem or gzip? This would suggest gzip:

http://code.google.com/p/go/issues/detail?id=3443

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: build failure on current

Evade Flow <evadeflow@...>
 

Is it definitely tar that's the problem or gzip? ...
Oh! Didn't even think of that. :-% Looks like it's gzip:

evadeflow% gzip -d perl-5.14.2.tar.gz

gzip: perl-5.14.2.tar.gz: invalid compressed data--crc error


Nice find! I'll see about updating my gzip...


On Fri, Sep 28, 2012 at 12:00 PM, Paul Eggleton
<paul.eggleton@...> wrote:
On Friday 28 September 2012 11:53:53 Evade Flow wrote:
Erm... that *specific* bit prints nothing when pasted into a file and
executed. (Is it really supposed to?)
No, but the rest of the script (the bit following the blank line that
you've omitted) is...
My bad, sorry. (I really need to read more carefully.) Here's what I get
when I add the missing lines:

evadeflow% cat > temp.sh
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}

# Tar version 1.24 and onwards handle overwriting symlinks correctly
# but earlier versions do not; this needs to work properly for sstate
float_test "$TARVERSION > 1.23" && needtar="0"
echo $needtar
evadeflow% chmod +x temp.sh
evadeflow% ./temp.sh
1

So... it correctly determines that it needs to build tar, but... the built
tar can't unpack the tarball from CPAN:

evadeflow% wget http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
--2012-09-28 11:46:13-- http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
Resolving usaprox1.lightning.com... 10.102.184.7
Connecting to usaprox1.lightning.com|10.102.184.7|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 15223598 (15M) [application/x-gzip]
Saving to: `perl-5.14.2.tar.gz'

100%[================================================================>]
15,223,598 62.2M/s in 0.2s

2012-09-28 11:46:13 (62.2 MB/s) - `perl-5.14.2.tar.gz' saved
[15223598/15223598]

evadeflow% ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar xf
perl-5.14.2.tar.gz

gzip: stdin: invalid compressed data--crc error
./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Child returned status
1 ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Error is not
recoverable: exiting now


Weird. Anyway, I have a workaround, so it's not a big deal--especially given
that Ubuntu 10.04 isn't officially supported. I'm happy to run any other
tests you can think of to hunt down the cause of this (I've got a pretty
fast build mchine now), but I totally understand if you've got bigger fish
to fry at the moment...
Is it definitely tar that's the problem or gzip? This would suggest gzip:

http://code.google.com/p/go/issues/detail?id=3443

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: build failure on current

Paul Eggleton
 

On Friday 28 September 2012 11:53:53 Evade Flow wrote:
Erm... that *specific* bit prints nothing when pasted into a file and
executed. (Is it really supposed to?)
No, but the rest of the script (the bit following the blank line that
you've omitted) is...
My bad, sorry. (I really need to read more carefully.) Here's what I get
when I add the missing lines:

evadeflow% cat > temp.sh
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}

# Tar version 1.24 and onwards handle overwriting symlinks correctly
# but earlier versions do not; this needs to work properly for sstate
float_test "$TARVERSION > 1.23" && needtar="0"
echo $needtar
evadeflow% chmod +x temp.sh
evadeflow% ./temp.sh
1

So... it correctly determines that it needs to build tar, but... the built
tar can't unpack the tarball from CPAN:

evadeflow% wget http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
--2012-09-28 11:46:13-- http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
Resolving usaprox1.lightning.com... 10.102.184.7
Connecting to usaprox1.lightning.com|10.102.184.7|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 15223598 (15M) [application/x-gzip]
Saving to: `perl-5.14.2.tar.gz'

100%[================================================================>]
15,223,598 62.2M/s in 0.2s

2012-09-28 11:46:13 (62.2 MB/s) - `perl-5.14.2.tar.gz' saved
[15223598/15223598]

evadeflow% ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar xf
perl-5.14.2.tar.gz

gzip: stdin: invalid compressed data--crc error
./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Child returned status
1 ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Error is not
recoverable: exiting now


Weird. Anyway, I have a workaround, so it's not a big deal--especially given
that Ubuntu 10.04 isn't officially supported. I'm happy to run any other
tests you can think of to hunt down the cause of this (I've got a pretty
fast build mchine now), but I totally understand if you've got bigger fish
to fry at the moment...
Is it definitely tar that's the problem or gzip? This would suggest gzip:

http://code.google.com/p/go/issues/detail?id=3443

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: build failure on current

Evade Flow <evadeflow@...>
 

Erm... that *specific* bit prints nothing when pasted into a file and
executed. (Is it really supposed to?)
No, but the rest of the script (the bit following the blank line that you've
omitted) is...
My bad, sorry. (I really need to read more carefully.) Here's what I get when
I add the missing lines:

evadeflow% cat > temp.sh
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}

# Tar version 1.24 and onwards handle overwriting symlinks correctly
# but earlier versions do not; this needs to work properly for sstate
float_test "$TARVERSION > 1.23" && needtar="0"
echo $needtar
evadeflow% chmod +x temp.sh
evadeflow% ./temp.sh
1

So... it correctly determines that it needs to build tar, but... the built tar
can't unpack the tarball from CPAN:

evadeflow% wget http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
--2012-09-28 11:46:13-- http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
Resolving usaprox1.lightning.com... 10.102.184.7
Connecting to usaprox1.lightning.com|10.102.184.7|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 15223598 (15M) [application/x-gzip]
Saving to: `perl-5.14.2.tar.gz'

100%[================================================================>]
15,223,598 62.2M/s in 0.2s

2012-09-28 11:46:13 (62.2 MB/s) - `perl-5.14.2.tar.gz' saved [15223598/15223598]

evadeflow% ./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar xf
perl-5.14.2.tar.gz

gzip: stdin: invalid compressed data--crc error
./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Child returned status 1
./poky-git/build/tmp/sysroots/i686-linux/usr/bin/tar: Error is not
recoverable: exiting now


Weird. Anyway, I have a workaround, so it's not a big deal--especially given
that Ubuntu 10.04 isn't officially supported. I'm happy to run any other
tests you can think of to hunt down the cause of this (I've got a pretty fast
build mchine now), but I totally understand if you've got bigger fish to fry
at the moment...


On Fri, Sep 28, 2012 at 11:19 AM, Paul Eggleton
<paul.eggleton@...> wrote:
On Friday 28 September 2012 11:13:22 Evade Flow wrote:
... could you put this into a file and run it and tell
me
what it prints on your system?

--------------- snip --------------
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {

echo | awk 'END { exit ( !( '"$1"')); }'

}
Erm... that *specific* bit prints nothing when pasted into a file and
executed. (Is it really supposed to?)
No, but the rest of the script (the bit following the blank line that you've
omitted) is... I wanted to ensure that both the stripping out of the version
and float_test were working.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: build failure on current

Paul Eggleton
 

On Friday 28 September 2012 11:13:22 Evade Flow wrote:
... could you put this into a file and run it and tell
me
what it prints on your system?

--------------- snip --------------
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {

echo | awk 'END { exit ( !( '"$1"')); }'

}
Erm... that *specific* bit prints nothing when pasted into a file and
executed. (Is it really supposed to?)
No, but the rest of the script (the bit following the blank line that you've
omitted) is... I wanted to ensure that both the stripping out of the version
and float_test were working.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: build failure on current

Evade Flow <evadeflow@...>
 

To answer your questions...

Just to confirm, this is the same path you get if you run "cat pseudodone"
in your build directory?
Yessir.

evadeflow% cat pseudodone
/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin


... could you put this into a file and run it and tell me
what it prints on your system?

--------------- snip --------------
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}
Erm... that *specific* bit prints nothing when pasted into a file and
executed. (Is it really supposed to?)

evadeflow% cat > temp.sh
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}
evadeflow% chmod +x temp.sh
evadeflow% ./temp.sh
evadeflow% ls -la /bin/sh
lrwxrwxrwx 1 root root 9 2010-08-13 05:08 /bin/sh -> /bin/bash
evadeflow% tar --version | head -n 1 | cut -d ' ' -f 4
1.22


On Fri, Sep 28, 2012 at 10:34 AM, Paul Eggleton
<paul.eggleton@...> wrote:
On Friday 28 September 2012 10:16:27 Evade Flow wrote:
Seems it definitely didn't build tar:

evadeflow% pwd
/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin
Just to confirm, this is the same path you get if you run "cat pseudodone" in
your build directory?

evadeflow% ls t*
tabs tailf taskset tic toe tput tset tunctl tzselect
evadeflow% tar --version
tar (GNU tar) 1.22
...
This is on denzil, BTW. (Maybe the check against the tar version was added
later?)
No, the code to do this was there in denzil as well. Here's the code cut out
into a shell script - could you put this into a file and run it and tell me
what it prints on your system?

--------------- snip --------------
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}

# Tar version 1.24 and onwards handle overwriting symlinks correctly
# but earlier versions do not; this needs to work properly for sstate
float_test "$TARVERSION > 1.23" && needtar="0"
echo $needtar
--------------- snip --------------

Thanks,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: build failure on current

Evade Flow <evadeflow@...>
 

It definitely chokes on perl when building core-image-minimal from scratch on
my Ubuntu 10.04 LTS machine. But... it *did* build tar 1.26!(?) And even this
tar cannot, it seems, unpack the perl-5.14.2.tar.gz archive from CPAN:


evadeflow% ls tmp/sysroots/i686-linux/usr/bin/tar
tmp/sysroots/i686-linux/usr/bin/tar
evadeflow% tmp/sysroots/i686-linux/usr/bin/tar --version
tar (GNU tar) 1.26
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.
evadeflow% tmp/sysroots/i686-linux/usr/bin/tar xf ~/projects/perl-5.14.2.tar.gz

gzip: stdin: invalid compressed data--crc error
tmp/sysroots/i686-linux/usr/bin/tar: Child returned status 1
tmp/sysroots/i686-linux/usr/bin/tar: Error is not recoverable: exiting now



I really don't know what to make of this. Appending the complete output below,
in case it's useful...

----------

evadeflow% git status
# On branch denzil
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# ./
# ../build_1/
# ../build_sato_hide/
# ../meta/recipes-devtools/perl/perl-native_5.14.2.bb.tar122
# ../meta/recipes-devtools/perl/perl_5.14.2.bb.tar122
nothing added to commit but untracked files present (use "git add" to track)
evadeflow% time bitbake core-image-minimal
Pseudo is not present but is required, building this first before the main
build
WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated with this
version of the build system; you may possibly experience unexpected failures.
It is recommended that you use a tested distribution.
Parsing recipes: 100%
|###################################################################| Time:
00:00:13
Parsing of 829 .bb files complete (0 cached, 829 parsed). 1105 targets, 34
skipped, 0 masked, 0 errors.

OE Build Configuration:
BB_VERSION = "1.15.2"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "qemuarm"
DISTRO = "poky"
DISTRO_VERSION = "1.2.1"
TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"
meta
meta-yocto = "denzil:65ffa7395055f7e012cb973f63f92380828eed0d"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 1 of 77 (ID: 18,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/quilt/quilt-native_0.51.bb,
do_fetch)
NOTE: Running task 2 of 77 (ID: 53,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/gnu-config/gnu-config_20111111.bb,
do_fetch)
NOTE: Running task 3 of 77 (ID: 67,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/m4/m4-native_1.4.16.bb,
do_fetch)
NOTE: Running task 4 of 77 (ID: 32,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/autoconf/autoconf_2.68.bb,
do_fetch)
NOTE: Running task 5 of 77 (ID: 39,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/automake/automake_1.11.2.bb,
do_fetch)
NOTE: Running task 6 of 77 (ID: 46,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb,
do_fetch)
NOTE: Running task 7 of 77 (ID: 74,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pkgconfig/pkgconfig_0.25.bb,
do_fetch)
NOTE: Running task 8 of 77 (ID: 60,
/home/evadeflow/projects/poky-git/meta/recipes-core/gettext/gettext-minimal-native_0.18.1.1.bb,
do_fetch)
NOTE: Running task 9 of 77 (ID: 25,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/sqlite/sqlite3_3.7.10.bb,
do_fetch)
NOTE: Running task 10 of 77 (ID: 11,
/home/evadeflow/projects/poky-git/meta/recipes-extended/tar/tar-replacement-native_1.26.bb,
do_fetch)
NOTE: Running task 11 of 77 (ID: 4,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pseudo/pseudo_1.3.bb,
do_fetch)
NOTE: package m4-native-1.4.16-r2: task do_fetch: Started
NOTE: package quilt-native-0.51-r1: task do_fetch: Started
NOTE: package gnu-config-native-20111111-r1: task do_fetch: Started
NOTE: package gnu-config-native-20111111-r1: task do_fetch: Succeeded
NOTE: package m4-native-1.4.16-r2: task do_fetch: Succeeded
NOTE: package autoconf-native-2.68-r7: task do_fetch: Started
NOTE: package libtool-native-2.4.2-r3.0: task do_fetch: Started
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_fetch: Started
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_fetch: Succeeded
NOTE: package tar-replacement-native-1.26-r1: task do_fetch: Started
NOTE: Running task 12 of 77 (ID: 49,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/gnu-config/gnu-config_20111111.bb,
do_unpack)
NOTE: package pkgconfig-native-0.25-r3: task do_fetch: Started
NOTE: package sqlite3-native-3.7.10-r2: task do_fetch: Started
NOTE: package pseudo-native-1.3-r10: task do_fetch: Started
NOTE: Running task 13 of 77 (ID: 63,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/m4/m4-native_1.4.16.bb,
do_unpack)
NOTE: package quilt-native-0.51-r1: task do_fetch: Succeeded
NOTE: Running task 14 of 77 (ID: 14,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/quilt/quilt-native_0.51.bb,
do_unpack)
NOTE: Running task 15 of 77 (ID: 56,
/home/evadeflow/projects/poky-git/meta/recipes-core/gettext/gettext-minimal-native_0.18.1.1.bb,
do_unpack)
NOTE: package automake-native-1.11.2-r3: task do_fetch: Started
NOTE: package pkgconfig-native-0.25-r3: task do_fetch: Succeeded
NOTE: package m4-native-1.4.16-r2: task do_unpack: Started
NOTE: package quilt-native-0.51-r1: task do_unpack: Started
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_unpack: Started
NOTE: package libtool-native-2.4.2-r3.0: task do_fetch: Succeeded
NOTE: Running task 16 of 77 (ID: 42,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb,
do_unpack)
NOTE: package gnu-config-native-20111111-r1: task do_unpack: Started
NOTE: Running task 17 of 77 (ID: 70,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pkgconfig/pkgconfig_0.25.bb,
do_unpack)
NOTE: package sqlite3-native-3.7.10-r2: task do_fetch: Succeeded
NOTE: package tar-replacement-native-1.26-r1: task do_fetch: Succeeded
NOTE: package pseudo-native-1.3-r10: task do_fetch: Succeeded
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_unpack: Succeeded
NOTE: package libtool-native-2.4.2-r3.0: task do_unpack: Started
NOTE: Running task 18 of 77 (ID: 21,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/sqlite/sqlite3_3.7.10.bb,
do_unpack)
NOTE: Running task 19 of 77 (ID: 7,
/home/evadeflow/projects/poky-git/meta/recipes-extended/tar/tar-replacement-native_1.26.bb,
do_unpack)
NOTE: package gnu-config-native-20111111-r1: task do_unpack: Succeeded
NOTE: package automake-native-1.11.2-r3: task do_fetch: Succeeded
NOTE: Running task 20 of 77 (ID: 35,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/automake/automake_1.11.2.bb,
do_unpack)
NOTE: package quilt-native-0.51-r1: task do_unpack: Succeeded
NOTE: Running task 21 of 77 (ID: 0,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pseudo/pseudo_1.3.bb,
do_unpack)
NOTE: package autoconf-native-2.68-r7: task do_fetch: Succeeded
NOTE: package pkgconfig-native-0.25-r3: task do_unpack: Started
NOTE: Running task 22 of 77 (ID: 28,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/autoconf/autoconf_2.68.bb,
do_unpack)
NOTE: Running task 23 of 77 (ID: 15,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/quilt/quilt-native_0.51.bb,
do_patch)
NOTE: package pkgconfig-native-0.25-r3: task do_unpack: Succeeded
NOTE: package tar-replacement-native-1.26-r1: task do_unpack: Started
NOTE: package m4-native-1.4.16-r2: task do_unpack: Succeeded
NOTE: package libtool-native-2.4.2-r3.0: task do_unpack: Succeeded
NOTE: package pseudo-native-1.3-r10: task do_unpack: Started
NOTE: package pseudo-native-1.3-r10: task do_unpack: Succeeded
NOTE: package quilt-native-0.51-r1: task do_patch: Started
NOTE: package sqlite3-native-3.7.10-r2: task do_unpack: Started
NOTE: package automake-native-1.11.2-r3: task do_unpack: Started
NOTE: package autoconf-native-2.68-r7: task do_unpack: Started
NOTE: package quilt-native-0.51-r1: task do_patch: Succeeded
NOTE: package sqlite3-native-3.7.10-r2: task do_unpack: Succeeded
NOTE: Running task 24 of 77 (ID: 19,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/quilt/quilt-native_0.51.bb,
do_configure)
NOTE: package quilt-native-0.51-r1: task do_configure: Started
NOTE: package automake-native-1.11.2-r3: task do_unpack: Succeeded
NOTE: package autoconf-native-2.68-r7: task do_unpack: Succeeded
NOTE: package tar-replacement-native-1.26-r1: task do_unpack: Succeeded
NOTE: package quilt-native-0.51-r1: task do_configure: Succeeded
NOTE: Running task 25 of 77 (ID: 20,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/quilt/quilt-native_0.51.bb,
do_compile)
NOTE: package quilt-native-0.51-r1: task do_compile: Started
NOTE: package quilt-native-0.51-r1: task do_compile: Succeeded
NOTE: Running task 26 of 77 (ID: 16,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/quilt/quilt-native_0.51.bb,
do_install)
NOTE: package quilt-native-0.51-r1: task do_install: Started
NOTE: package quilt-native-0.51-r1: task do_install: Succeeded
NOTE: Running task 27 of 77 (ID: 17,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/quilt/quilt-native_0.51.bb,
do_populate_sysroot)
NOTE: package quilt-native-0.51-r1: task do_populate_sysroot: Started
NOTE: package quilt-native-0.51-r1: task do_populate_sysroot: Succeeded
NOTE: Running task 28 of 77 (ID: 50,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/gnu-config/gnu-config_20111111.bb,
do_patch)
NOTE: Running task 29 of 77 (ID: 64,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/m4/m4-native_1.4.16.bb,
do_patch)
NOTE: Running task 30 of 77 (ID: 29,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/autoconf/autoconf_2.68.bb,
do_patch)
NOTE: Running task 31 of 77 (ID: 36,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/automake/automake_1.11.2.bb,
do_patch)
NOTE: Running task 32 of 77 (ID: 43,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb,
do_patch)
NOTE: Running task 33 of 77 (ID: 71,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pkgconfig/pkgconfig_0.25.bb,
do_patch)
NOTE: Running task 34 of 77 (ID: 57,
/home/evadeflow/projects/poky-git/meta/recipes-core/gettext/gettext-minimal-native_0.18.1.1.bb,
do_patch)
NOTE: Running task 35 of 77 (ID: 22,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/sqlite/sqlite3_3.7.10.bb,
do_patch)
NOTE: Running task 36 of 77 (ID: 8,
/home/evadeflow/projects/poky-git/meta/recipes-extended/tar/tar-replacement-native_1.26.bb,
do_patch)
NOTE: Running task 37 of 77 (ID: 1,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pseudo/pseudo_1.3.bb,
do_patch)
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_patch: Started
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_patch: Succeeded
NOTE: Running task 38 of 77 (ID: 61,
/home/evadeflow/projects/poky-git/meta/recipes-core/gettext/gettext-minimal-native_0.18.1.1.bb,
do_configure)
NOTE: package m4-native-1.4.16-r2: task do_patch: Started
NOTE: package libtool-native-2.4.2-r3.0: task do_patch: Started
NOTE: package gnu-config-native-20111111-r1: task do_patch: Started
NOTE: package autoconf-native-2.68-r7: task do_patch: Started
NOTE: package pkgconfig-native-0.25-r3: task do_patch: Started
NOTE: package tar-replacement-native-1.26-r1: task do_patch: Started
NOTE: package tar-replacement-native-1.26-r1: task do_patch: Succeeded
NOTE: package m4-native-1.4.16-r2: task do_patch: Succeeded
NOTE: package automake-native-1.11.2-r3: task do_patch: Started
NOTE: package pseudo-native-1.3-r10: task do_patch: Started
NOTE: package sqlite3-native-3.7.10-r2: task do_patch: Started
NOTE: package pseudo-native-1.3-r10: task do_patch: Succeeded
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_configure: Started
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_configure: Succeeded
NOTE: Running task 39 of 77 (ID: 62,
/home/evadeflow/projects/poky-git/meta/recipes-core/gettext/gettext-minimal-native_0.18.1.1.bb,
do_compile)
NOTE: package sqlite3-native-3.7.10-r2: task do_patch: Succeeded
NOTE: package gnu-config-native-20111111-r1: task do_patch: Succeeded
NOTE: Running task 40 of 77 (ID: 54,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/gnu-config/gnu-config_20111111.bb,
do_configure)
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_compile: Started
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_compile: Succeeded
NOTE: package automake-native-1.11.2-r3: task do_patch: Succeeded
NOTE: package pkgconfig-native-0.25-r3: task do_patch: Succeeded
NOTE: Running task 41 of 77 (ID: 58,
/home/evadeflow/projects/poky-git/meta/recipes-core/gettext/gettext-minimal-native_0.18.1.1.bb,
do_install)
NOTE: package autoconf-native-2.68-r7: task do_patch: Succeeded
NOTE: package gnu-config-native-20111111-r1: task do_configure: Started
NOTE: package gnu-config-native-20111111-r1: task do_configure: Succeeded
NOTE: Running task 42 of 77 (ID: 55,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/gnu-config/gnu-config_20111111.bb,
do_compile)
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_install: Started
NOTE: package libtool-native-2.4.2-r3.0: task do_patch: Succeeded
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_install: Succeeded
NOTE: Running task 43 of 77 (ID: 59,
/home/evadeflow/projects/poky-git/meta/recipes-core/gettext/gettext-minimal-native_0.18.1.1.bb,
do_populate_sysroot)
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_populate_sysroot:
Started
NOTE: package gnu-config-native-20111111-r1: task do_compile: Started
NOTE: package gnu-config-native-20111111-r1: task do_compile: Succeeded
NOTE: Running task 44 of 77 (ID: 51,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/gnu-config/gnu-config_20111111.bb,
do_install)
NOTE: package gettext-minimal-native-0.18.1.1-r3: task do_populate_sysroot:
Succeeded
NOTE: package gnu-config-native-20111111-r1: task do_install: Started
NOTE: package gnu-config-native-20111111-r1: task do_install: Succeeded
NOTE: Running task 45 of 77 (ID: 52,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/gnu-config/gnu-config_20111111.bb,
do_populate_sysroot)
NOTE: package gnu-config-native-20111111-r1: task do_populate_sysroot: Started
NOTE: package gnu-config-native-20111111-r1: task do_populate_sysroot:
Succeeded
NOTE: Running task 46 of 77 (ID: 68,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/m4/m4-native_1.4.16.bb,
do_configure)
NOTE: package m4-native-1.4.16-r2: task do_configure: Started
NOTE: package m4-native-1.4.16-r2: task do_configure: Succeeded
NOTE: Running task 47 of 77 (ID: 69,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/m4/m4-native_1.4.16.bb,
do_compile)
NOTE: package m4-native-1.4.16-r2: task do_compile: Started
NOTE: package m4-native-1.4.16-r2: task do_compile: Succeeded
NOTE: Running task 48 of 77 (ID: 65,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/m4/m4-native_1.4.16.bb,
do_install)
NOTE: package m4-native-1.4.16-r2: task do_install: Started
NOTE: package m4-native-1.4.16-r2: task do_install: Succeeded
NOTE: Running task 49 of 77 (ID: 66,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/m4/m4-native_1.4.16.bb,
do_populate_sysroot)
NOTE: package m4-native-1.4.16-r2: task do_populate_sysroot: Started
NOTE: package m4-native-1.4.16-r2: task do_populate_sysroot: Succeeded
NOTE: Running task 50 of 77 (ID: 33,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/autoconf/autoconf_2.68.bb,
do_configure)
NOTE: package autoconf-native-2.68-r7: task do_configure: Started
NOTE: package autoconf-native-2.68-r7: task do_configure: Succeeded
NOTE: Running task 51 of 77 (ID: 34,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/autoconf/autoconf_2.68.bb,
do_compile)
NOTE: package autoconf-native-2.68-r7: task do_compile: Started
NOTE: package autoconf-native-2.68-r7: task do_compile: Succeeded
NOTE: Running task 52 of 77 (ID: 30,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/autoconf/autoconf_2.68.bb,
do_install)
NOTE: package autoconf-native-2.68-r7: task do_install: Started
NOTE: package autoconf-native-2.68-r7: task do_install: Succeeded
NOTE: Running task 53 of 77 (ID: 31,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/autoconf/autoconf_2.68.bb,
do_populate_sysroot)
NOTE: package autoconf-native-2.68-r7: task do_populate_sysroot: Started
NOTE: package autoconf-native-2.68-r7: task do_populate_sysroot: Succeeded
NOTE: Running task 54 of 77 (ID: 40,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/automake/automake_1.11.2.bb,
do_configure)
NOTE: package automake-native-1.11.2-r3: task do_configure: Started
NOTE: package automake-native-1.11.2-r3: task do_configure: Succeeded
NOTE: Running task 55 of 77 (ID: 41,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/automake/automake_1.11.2.bb,
do_compile)
NOTE: package automake-native-1.11.2-r3: task do_compile: Started
NOTE: package automake-native-1.11.2-r3: task do_compile: Succeeded
NOTE: Running task 56 of 77 (ID: 37,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/automake/automake_1.11.2.bb,
do_install)
NOTE: package automake-native-1.11.2-r3: task do_install: Started
NOTE: package automake-native-1.11.2-r3: task do_install: Succeeded
NOTE: Running task 57 of 77 (ID: 38,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/automake/automake_1.11.2.bb,
do_populate_sysroot)
NOTE: package automake-native-1.11.2-r3: task do_populate_sysroot: Started
NOTE: package automake-native-1.11.2-r3: task do_populate_sysroot: Succeeded
NOTE: Running task 58 of 77 (ID: 47,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb,
do_configure)
NOTE: package libtool-native-2.4.2-r3.0: task do_configure: Started
NOTE: package libtool-native-2.4.2-r3.0: task do_configure: Succeeded
NOTE: Running task 59 of 77 (ID: 48,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb,
do_compile)
NOTE: package libtool-native-2.4.2-r3.0: task do_compile: Started
NOTE: package libtool-native-2.4.2-r3.0: task do_compile: Succeeded
NOTE: Running task 60 of 77 (ID: 44,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb,
do_install)
NOTE: package libtool-native-2.4.2-r3.0: task do_install: Started
NOTE: package libtool-native-2.4.2-r3.0: task do_install: Succeeded
NOTE: Running task 61 of 77 (ID: 45,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/libtool/libtool-native_2.4.2.bb,
do_populate_sysroot)
NOTE: package libtool-native-2.4.2-r3.0: task do_populate_sysroot: Started
NOTE: package libtool-native-2.4.2-r3.0: task do_populate_sysroot: Succeeded
NOTE: Running task 62 of 77 (ID: 75,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pkgconfig/pkgconfig_0.25.bb,
do_configure)
NOTE: Running task 63 of 77 (ID: 12,
/home/evadeflow/projects/poky-git/meta/recipes-extended/tar/tar-replacement-native_1.26.bb,
do_configure)
NOTE: package tar-replacement-native-1.26-r1: task do_configure: Started
NOTE: package pkgconfig-native-0.25-r3: task do_configure: Started
NOTE: package pkgconfig-native-0.25-r3: task do_configure: Succeeded
NOTE: Running task 64 of 77 (ID: 76,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pkgconfig/pkgconfig_0.25.bb,
do_compile)
NOTE: package pkgconfig-native-0.25-r3: task do_compile: Started
NOTE: package pkgconfig-native-0.25-r3: task do_compile: Succeeded
NOTE: Running task 65 of 77 (ID: 72,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pkgconfig/pkgconfig_0.25.bb,
do_install)
NOTE: package pkgconfig-native-0.25-r3: task do_install: Started
NOTE: package pkgconfig-native-0.25-r3: task do_install: Succeeded
NOTE: Running task 66 of 77 (ID: 73,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pkgconfig/pkgconfig_0.25.bb,
do_populate_sysroot)
NOTE: package pkgconfig-native-0.25-r3: task do_populate_sysroot: Started
NOTE: package pkgconfig-native-0.25-r3: task do_populate_sysroot: Succeeded
NOTE: Running task 67 of 77 (ID: 26,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/sqlite/sqlite3_3.7.10.bb,
do_configure)
NOTE: package sqlite3-native-3.7.10-r2: task do_configure: Started
NOTE: package sqlite3-native-3.7.10-r2: task do_configure: Succeeded
NOTE: Running task 68 of 77 (ID: 27,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/sqlite/sqlite3_3.7.10.bb,
do_compile)
NOTE: package sqlite3-native-3.7.10-r2: task do_compile: Started
NOTE: package tar-replacement-native-1.26-r1: task do_configure: Succeeded
NOTE: Running task 69 of 77 (ID: 13,
/home/evadeflow/projects/poky-git/meta/recipes-extended/tar/tar-replacement-native_1.26.bb,
do_compile)
NOTE: package tar-replacement-native-1.26-r1: task do_compile: Started
NOTE: package tar-replacement-native-1.26-r1: task do_compile: Succeeded
NOTE: Running task 70 of 77 (ID: 9,
/home/evadeflow/projects/poky-git/meta/recipes-extended/tar/tar-replacement-native_1.26.bb,
do_install)
NOTE: package tar-replacement-native-1.26-r1: task do_install: Started
NOTE: package tar-replacement-native-1.26-r1: task do_install: Succeeded
NOTE: Running task 71 of 77 (ID: 10,
/home/evadeflow/projects/poky-git/meta/recipes-extended/tar/tar-replacement-native_1.26.bb,
do_populate_sysroot)
NOTE: package tar-replacement-native-1.26-r1: task do_populate_sysroot:
Started
NOTE: package tar-replacement-native-1.26-r1: task do_populate_sysroot:
Succeeded
NOTE: package sqlite3-native-3.7.10-r2: task do_compile: Succeeded
NOTE: Running task 72 of 77 (ID: 23,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/sqlite/sqlite3_3.7.10.bb,
do_install)
NOTE: package sqlite3-native-3.7.10-r2: task do_install: Started
NOTE: package sqlite3-native-3.7.10-r2: task do_install: Succeeded
NOTE: Running task 73 of 77 (ID: 24,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/sqlite/sqlite3_3.7.10.bb,
do_populate_sysroot)
NOTE: package sqlite3-native-3.7.10-r2: task do_populate_sysroot: Started
NOTE: package sqlite3-native-3.7.10-r2: task do_populate_sysroot: Succeeded
NOTE: Running task 74 of 77 (ID: 5,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pseudo/pseudo_1.3.bb,
do_configure)
NOTE: package pseudo-native-1.3-r10: task do_configure: Started
NOTE: package pseudo-native-1.3-r10: task do_configure: Succeeded
NOTE: Running task 75 of 77 (ID: 6,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pseudo/pseudo_1.3.bb,
do_compile)
NOTE: package pseudo-native-1.3-r10: task do_compile: Started
NOTE: package pseudo-native-1.3-r10: task do_compile: Succeeded
NOTE: Running task 76 of 77 (ID: 2,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pseudo/pseudo_1.3.bb,
do_install)
NOTE: package pseudo-native-1.3-r10: task do_install: Started
NOTE: package pseudo-native-1.3-r10: task do_install: Succeeded
NOTE: Running task 77 of 77 (ID: 3,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/pseudo/pseudo_1.3.bb,
do_populate_sysroot)
NOTE: package pseudo-native-1.3-r10: task do_populate_sysroot: Started
NOTE: package pseudo-native-1.3-r10: task do_populate_sysroot: Succeeded
NOTE: Tasks Summary: Attempted 77 tasks of which 0 didn't need to be rerun and
all succeeded.

Summary: There was 1 WARNING message shown.
WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated with this
version of the build system; you may possibly experience unexpected failures.
It is recommended that you use a tested distribution.
Parsing recipes: 100%
|###################################################################| Time:
00:00:07
Parsing of 829 .bb files complete (0 cached, 829 parsed). 1105 targets, 34
skipped, 0 masked, 0 errors.

OE Build Configuration:
BB_VERSION = "1.15.2"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "qemuarm"
DISTRO = "poky"
DISTRO_VERSION = "1.2.1"
TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"
meta
meta-yocto = "denzil:65ffa7395055f7e012cb973f63f92380828eed0d"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 43 of 1353 (ID: 863,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/gmp/gmp_5.0.4.bb,
do_fetch)
NOTE: Running task 44 of 1353 (ID: 335,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/zlib/zlib_1.2.6.bb,
do_fetch)
NOTE: Running task 59 of 1353 (ID: 852,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/mpfr/mpfr_3.1.0.bb,
do_fetch)
NOTE: Running task 74 of 1353 (ID: 1346,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/gcc/gcc-cross-initial_4.6.bb,
do_fetch)
NOTE: Running task 75 of 1353 (ID: 720,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/bison/bison_2.5.bb,
do_fetch)
NOTE: Running task 76 of 1353 (ID: 709,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/flex/flex_2.5.35.bb,
do_fetch)
NOTE: Running task 77 of 1353 (ID: 874,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/libmpc/libmpc_0.8.2.bb,
do_fetch)
NOTE: Running task 78 of 1353 (ID: 841,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/binutils/binutils-cross_2.22.bb,
do_fetch)
NOTE: Running task 79 of 1353 (ID: 1246,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/unifdef/unifdef-native_2.6.18+git.bb,
do_fetch)
NOTE: Running task 80 of 1353 (ID: 909,
/home/evadeflow/projects/poky-git/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.2.bb,
do_fetch)
NOTE: Running task 81 of 1353 (ID: 1235,
/home/evadeflow/projects/poky-git/meta/recipes-core/eglibc/eglibc-initial_2.13.bb,
do_fetch)
NOTE: Running task 82 of 1353 (ID: 920,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/gperf/gperf_3.0.4.bb,
do_fetch)
NOTE: Running task 83 of 1353 (ID: 437,
/home/evadeflow/projects/poky-git/meta/recipes-core/eglibc/eglibc_2.13.bb,
do_fetch)
NOTE: Running task 84 of 1353 (ID: 1212,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/ocf-linux_20100325.bb,
do_fetch)
NOTE: Running task 85 of 1353 (ID: 654,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/openssl_1.0.0i.bb,
do_fetch)
NOTE: Running task 86 of 1353 (ID: 160,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/pigz/pigz_2.2.4.bb,
do_fetch)
NOTE: package gmp-native-5.0.4-r0: task do_fetch: Started
NOTE: package zlib-native-1.2.6-r1: task do_fetch: Started
NOTE: package zlib-native-1.2.6-r1: task do_fetch: Succeeded
NOTE: package gcc-cross-initial-4.6.3+svnr184847-r28: task do_fetch: Started
NOTE: package binutils-cross-2.22-r6: task do_fetch: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_fetch: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_fetch: Succeeded
NOTE: package linux-libc-headers-3.2-r1: task do_fetch: Started
NOTE: Running task 87 of 1353 (ID: 331,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/zlib/zlib_1.2.6.bb,
do_unpack)
NOTE: package mpfr-native-3.1.0-r1: task do_fetch: Started
NOTE: package bison-native-2.5-r1: task do_fetch: Started
NOTE: package flex-native-2.5.35-r3: task do_fetch: Started
NOTE: package libmpc-native-0.8.2-r0: task do_fetch: Started
NOTE: package eglibc-initial-2.13-r28+svnr15508: task do_fetch: Started
NOTE: package gperf-native-3.0.4-r0: task do_fetch: Started
NOTE: package eglibc-2.13-r28+svnr15508: task do_fetch: Started
NOTE: package ocf-linux-native-20100325-r3.0: task do_fetch: Started
NOTE: package openssl-native-1.0.0i-r0.2: task do_fetch: Started
NOTE: package pigz-native-2.2.4-r2: task do_fetch: Started
NOTE: Running task 88 of 1353 (ID: 1242,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/unifdef/unifdef-native_2.6.18+git.bb,
do_unpack)
NOTE: package zlib-native-1.2.6-r1: task do_unpack: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_unpack: Started
NOTE: package gcc-cross-initial-4.6.3+svnr184847-r28: task do_fetch: Succeeded
NOTE: package unifdef-native-2.6.18+git-r0: task do_unpack: Succeeded
NOTE: Running task 89 of 1353 (ID: 1342,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/gcc/gcc-cross-initial_4.6.bb,
do_unpack)
NOTE: Running task 90 of 1353 (ID: 1243,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/unifdef/unifdef-native_2.6.18+git.bb,
do_patch)
NOTE: package gcc-cross-initial-4.6.3+svnr184847-r28: task do_unpack: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_patch: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_patch: Succeeded
NOTE: Running task 91 of 1353 (ID: 1247,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/unifdef/unifdef-native_2.6.18+git.bb,
do_configure)
NOTE: package libmpc-native-0.8.2-r0: task do_fetch: Succeeded
NOTE: package gperf-native-3.0.4-r0: task do_fetch: Succeeded
NOTE: Running task 92 of 1353 (ID: 870,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/libmpc/libmpc_0.8.2.bb,
do_unpack)
NOTE: Running task 94 of 1353 (ID: 916,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/gperf/gperf_3.0.4.bb,
do_unpack)
NOTE: package unifdef-native-2.6.18+git-r0: task do_configure: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_configure: Succeeded
NOTE: package zlib-native-1.2.6-r1: task do_unpack: Succeeded
NOTE: Running task 95 of 1353 (ID: 332,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/zlib/zlib_1.2.6.bb,
do_patch)
NOTE: Running task 96 of 1353 (ID: 1248,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/unifdef/unifdef-native_2.6.18+git.bb,
do_compile)
NOTE: package libmpc-native-0.8.2-r0: task do_unpack: Started
NOTE: package gperf-native-3.0.4-r0: task do_unpack: Started
NOTE: package gmp-native-5.0.4-r0: task do_fetch: Succeeded
NOTE: Running task 97 of 1353 (ID: 859,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/gmp/gmp_5.0.4.bb,
do_unpack)
NOTE: package libmpc-native-0.8.2-r0: task do_unpack: Succeeded
NOTE: Running task 98 of 1353 (ID: 871,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/libmpc/libmpc_0.8.2.bb,
do_patch)
NOTE: package gperf-native-3.0.4-r0: task do_unpack: Succeeded
NOTE: package zlib-native-1.2.6-r1: task do_patch: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_compile: Started
NOTE: Running task 99 of 1353 (ID: 917,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/gperf/gperf_3.0.4.bb,
do_patch)
NOTE: package gmp-native-5.0.4-r0: task do_unpack: Started
NOTE: package libmpc-native-0.8.2-r0: task do_patch: Started
NOTE: package libmpc-native-0.8.2-r0: task do_patch: Succeeded
NOTE: Running task 101 of 1353 (ID: 469,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/ncurses/ncurses_5.9.bb,
do_fetch)
NOTE: package eglibc-initial-2.13-r28+svnr15508: task do_fetch: Succeeded
NOTE: Running task 102 of 1353 (ID: 1230,
/home/evadeflow/projects/poky-git/meta/recipes-core/eglibc/eglibc-initial_2.13.bb,
do_unpack)
NOTE: package eglibc-2.13-r28+svnr15508: task do_fetch: Succeeded
NOTE: Running task 103 of 1353 (ID: 432,
/home/evadeflow/projects/poky-git/meta/recipes-core/eglibc/eglibc_2.13.bb,
do_unpack)
NOTE: package gperf-native-3.0.4-r0: task do_patch: Started
NOTE: package gperf-native-3.0.4-r0: task do_patch: Succeeded
NOTE: Running task 104 of 1353 (ID: 921,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/gperf/gperf_3.0.4.bb,
do_configure)
NOTE: package zlib-native-1.2.6-r1: task do_patch: Succeeded
NOTE: package ncurses-native-5.9-r9.1: task do_fetch: Started
NOTE: package eglibc-initial-2.13-r28+svnr15508: task do_unpack: Started
NOTE: package eglibc-2.13-r28+svnr15508: task do_unpack: Started
NOTE: Running task 105 of 1353 (ID: 336,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/zlib/zlib_1.2.6.bb,
do_configure)
NOTE: package unifdef-native-2.6.18+git-r0: task do_compile: Succeeded
NOTE: package gperf-native-3.0.4-r0: task do_configure: Started
NOTE: package zlib-native-1.2.6-r1: task do_configure: Started
NOTE: package flex-native-2.5.35-r3: task do_fetch: Succeeded
NOTE: package pigz-native-2.2.4-r2: task do_fetch: Succeeded
NOTE: Running task 106 of 1353 (ID: 705,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/flex/flex_2.5.35.bb,
do_unpack)
NOTE: Running task 107 of 1353 (ID: 156,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/pigz/pigz_2.2.4.bb,
do_unpack)
NOTE: Running task 108 of 1353 (ID: 1244,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/unifdef/unifdef-native_2.6.18+git.bb,
do_install)
NOTE: package flex-native-2.5.35-r3: task do_unpack: Started
NOTE: package pigz-native-2.2.4-r2: task do_unpack: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_install: Started
NOTE: package unifdef-native-2.6.18+git-r0: task do_install: Succeeded
NOTE: Running task 109 of 1353 (ID: 1245,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/unifdef/unifdef-native_2.6.18+git.bb,
do_populate_sysroot)
NOTE: package pigz-native-2.2.4-r2: task do_unpack: Succeeded
NOTE: package ocf-linux-native-20100325-r3.0: task do_fetch: Succeeded
NOTE: Running task 110 of 1353 (ID: 1208,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/ocf-linux_20100325.bb,
do_unpack)
NOTE: Running task 111 of 1353 (ID: 157,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/pigz/pigz_2.2.4.bb,
do_patch)
NOTE: package ocf-linux-native-20100325-r3.0: task do_unpack: Started
NOTE: package pigz-native-2.2.4-r2: task do_patch: Started
NOTE: package ncurses-native-5.9-r9.1: task do_fetch: Succeeded
NOTE: package zlib-native-1.2.6-r1: task do_configure: Succeeded
NOTE: package bison-native-2.5-r1: task do_fetch: Succeeded
NOTE: package unifdef-native-2.6.18+git-r0: task do_populate_sysroot: Started
NOTE: Running task 112 of 1353 (ID: 716,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/bison/bison_2.5.bb,
do_unpack)
NOTE: package ocf-linux-native-20100325-r3.0: task do_unpack: Succeeded
NOTE: package mpfr-native-3.1.0-r1: task do_fetch: Succeeded
NOTE: package binutils-cross-2.22-r6: task do_fetch: Succeeded
NOTE: Running task 113 of 1353 (ID: 848,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/mpfr/mpfr_3.1.0.bb,
do_unpack)
NOTE: package gmp-native-5.0.4-r0: task do_unpack: Succeeded
NOTE: Running task 114 of 1353 (ID: 837,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/binutils/binutils-cross_2.22.bb,
do_unpack)
NOTE: Running task 115 of 1353 (ID: 860,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/gmp/gmp_5.0.4.bb,
do_patch)
NOTE: package openssl-native-1.0.0i-r0.2: task do_fetch: Succeeded
NOTE: Running task 116 of 1353 (ID: 650,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/openssl_1.0.0i.bb,
do_unpack)
NOTE: Running task 117 of 1353 (ID: 465,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/ncurses/ncurses_5.9.bb,
do_unpack)
NOTE: Running task 118 of 1353 (ID: 337,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/zlib/zlib_1.2.6.bb,
do_compile)
NOTE: Running task 119 of 1353 (ID: 1209,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/ocf-linux_20100325.bb,
do_patch)
NOTE: package flex-native-2.5.35-r3: task do_unpack: Succeeded
NOTE: package bison-native-2.5-r1: task do_unpack: Started
NOTE: package mpfr-native-3.1.0-r1: task do_unpack: Started
NOTE: Running task 120 of 1353 (ID: 706,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/flex/flex_2.5.35.bb,
do_patch)
NOTE: package binutils-cross-2.22-r6: task do_unpack: Started
NOTE: package pigz-native-2.2.4-r2: task do_patch: Succeeded
NOTE: package gmp-native-5.0.4-r0: task do_patch: Started
NOTE: package openssl-native-1.0.0i-r0.2: task do_unpack: Started
NOTE: package ncurses-native-5.9-r9.1: task do_unpack: Started
NOTE: package zlib-native-1.2.6-r1: task do_compile: Started
NOTE: package ocf-linux-native-20100325-r3.0: task do_patch: Started
NOTE: package ocf-linux-native-20100325-r3.0: task do_patch: Succeeded
NOTE: package unifdef-native-2.6.18+git-r0: task do_populate_sysroot:
Succeeded
NOTE: Running task 123 of 1353 (ID: 698,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/perl/perl-native_5.14.2.bb,
do_fetch)
NOTE: Running task 124 of 1353 (ID: 687,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/expat/expat_2.0.1.bb,
do_fetch)
NOTE: Running task 125 of 1353 (ID: 1213,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/ocf-linux_20100325.bb,
do_configure)
NOTE: package perl-native-5.14.2-r0: task do_fetch: Started
NOTE: package expat-native-2.0.1-r1: task do_fetch: Started
NOTE: package ocf-linux-native-20100325-r3.0: task do_configure: Started
NOTE: package expat-native-2.0.1-r1: task do_fetch: Succeeded
NOTE: package ocf-linux-native-20100325-r3.0: task do_configure: Succeeded
NOTE: Running task 126 of 1353 (ID: 676,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/readline/readline_6.2.bb,
do_fetch)
NOTE: Running task 127 of 1353 (ID: 1214,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/ocf-linux_20100325.bb,
do_compile)
NOTE: package readline-native-6.2-r2: task do_fetch: Started
NOTE: package ocf-linux-native-20100325-r3.0: task do_compile: Started
NOTE: package perl-native-5.14.2-r0: task do_fetch: Succeeded
NOTE: Running task 128 of 1353 (ID: 694,
/home/evadeflow/projects/poky-git/meta/recipes-devtools/perl/perl-native_5.14.2.bb,
do_unpack)
NOTE: package ocf-linux-native-20100325-r3.0: task do_compile: Succeeded
NOTE: Running task 129 of 1353 (ID: 1210,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/ocf-linux_20100325.bb,
do_install)
NOTE: package readline-native-6.2-r2: task do_fetch: Succeeded
NOTE: package perl-native-5.14.2-r0: task do_unpack: Started
NOTE: package linux-libc-headers-3.2-r1: task do_fetch: Succeeded
NOTE: Running task 130 of 1353 (ID: 905,
/home/evadeflow/projects/poky-git/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.2.bb,
do_unpack)
NOTE: Running task 131 of 1353 (ID: 672,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/readline/readline_6.2.bb,
do_unpack)
NOTE: package ocf-linux-native-20100325-r3.0: task do_install: Started
NOTE: package linux-libc-headers-3.2-r1: task do_unpack: Started
NOTE: package readline-native-6.2-r2: task do_unpack: Started
NOTE: package ocf-linux-native-20100325-r3.0: task do_install: Succeeded
NOTE: package readline-native-6.2-r2: task do_unpack: Succeeded
NOTE: Running task 132 of 1353 (ID: 1211,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/ocf-linux_20100325.bb,
do_populate_sysroot)
NOTE: Running task 133 of 1353 (ID: 673,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/readline/readline_6.2.bb,
do_patch)
NOTE: package ocf-linux-native-20100325-r3.0: task do_populate_sysroot:
Started
NOTE: package readline-native-6.2-r2: task do_patch: Started
NOTE: package flex-native-2.5.35-r3: task do_patch: Started
NOTE: package zlib-native-1.2.6-r1: task do_compile: Succeeded
NOTE: Running task 134 of 1353 (ID: 333,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/zlib/zlib_1.2.6.bb,
do_install)
NOTE: package mpfr-native-3.1.0-r1: task do_unpack: Succeeded
NOTE: package flex-native-2.5.35-r3: task do_patch: Succeeded
NOTE: Running task 135 of 1353 (ID: 849,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/mpfr/mpfr_3.1.0.bb,
do_patch)
NOTE: Running task 136 of 1353 (ID: 710,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/flex/flex_2.5.35.bb,
do_configure)
NOTE: package zlib-native-1.2.6-r1: task do_install: Started
NOTE: package mpfr-native-3.1.0-r1: task do_patch: Started
NOTE: package flex-native-2.5.35-r3: task do_configure: Started
NOTE: package readline-native-6.2-r2: task do_patch: Succeeded
NOTE: package mpfr-native-3.1.0-r1: task do_patch: Succeeded
NOTE: package bison-native-2.5-r1: task do_unpack: Succeeded
NOTE: package gmp-native-5.0.4-r0: task do_patch: Succeeded
NOTE: Running task 137 of 1353 (ID: 717,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/bison/bison_2.5.bb,
do_patch)
NOTE: Running task 138 of 1353 (ID: 864,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/gmp/gmp_5.0.4.bb,
do_configure)
NOTE: Running task 139 of 1353 (ID: 808,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/attr/attr_2.4.46.bb,
do_fetch)
NOTE: Running task 140 of 1353 (ID: 291,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/elfutils/elfutils_0.148.bb,
do_fetch)
NOTE: package ocf-linux-native-20100325-r3.0: task do_populate_sysroot:
Succeeded
NOTE: package bison-native-2.5-r1: task do_patch: Started
NOTE: package gmp-native-5.0.4-r0: task do_configure: Started
NOTE: package attr-native-2.4.46-r4: task do_fetch: Started
NOTE: package elfutils-native-0.148-r7: task do_fetch: Started
NOTE: Running task 141 of 1353 (ID: 390,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/file/file_5.11.bb,
do_fetch)
NOTE: package zlib-native-1.2.6-r1: task do_install: Succeeded
NOTE: package file-native-5.11-r0: task do_fetch: Started
NOTE: package ncurses-native-5.9-r9.1: task do_unpack: Succeeded
NOTE: Running task 142 of 1353 (ID: 466,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/ncurses/ncurses_5.9.bb,
do_patch)
NOTE: Running task 143 of 1353 (ID: 334,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/zlib/zlib_1.2.6.bb,
do_populate_sysroot)
NOTE: package bison-native-2.5-r1: task do_patch: Succeeded
NOTE: Running task 144 of 1353 (ID: 721,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/bison/bison_2.5.bb,
do_configure)
NOTE: package attr-native-2.4.46-r4: task do_fetch: Succeeded
NOTE: Running task 145 of 1353 (ID: 804,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/attr/attr_2.4.46.bb,
do_unpack)
NOTE: package file-native-5.11-r0: task do_fetch: Succeeded
NOTE: package zlib-native-1.2.6-r1: task do_populate_sysroot: Started
NOTE: package bison-native-2.5-r1: task do_configure: Started
NOTE: package attr-native-2.4.46-r4: task do_unpack: Started
NOTE: package ncurses-native-5.9-r9.1: task do_patch: Started
NOTE: Running task 146 of 1353 (ID: 386,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/file/file_5.11.bb,
do_unpack)
NOTE: package attr-native-2.4.46-r4: task do_unpack: Succeeded
NOTE: Running task 147 of 1353 (ID: 805,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/attr/attr_2.4.46.bb,
do_patch)
NOTE: package file-native-5.11-r0: task do_unpack: Started
NOTE: package ncurses-native-5.9-r9.1: task do_patch: Succeeded
NOTE: package attr-native-2.4.46-r4: task do_patch: Started
NOTE: Running task 148 of 1353 (ID: 470,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-core/ncurses/ncurses_5.9.bb,
do_configure)
NOTE: package elfutils-native-0.148-r7: task do_fetch: Succeeded
NOTE: Running task 149 of 1353 (ID: 287,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/elfutils/elfutils_0.148.bb,
do_unpack)
NOTE: package openssl-native-1.0.0i-r0.2: task do_unpack: Succeeded
NOTE: package file-native-5.11-r0: task do_unpack: Succeeded
NOTE: package attr-native-2.4.46-r4: task do_patch: Succeeded
NOTE: Running task 150 of 1353 (ID: 651,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-connectivity/openssl/openssl_1.0.0i.bb,
do_patch)
NOTE: Running task 151 of 1353 (ID: 387,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/file/file_5.11.bb,
do_patch)
NOTE: Running task 152 of 1353 (ID: 324,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/curl/curl_7.24.0.bb,
do_fetch)
NOTE: package ncurses-native-5.9-r9.1: task do_configure: Started
NOTE: package elfutils-native-0.148-r7: task do_unpack: Started
NOTE: package curl-native-7.24.0-r2: task do_fetch: Started
NOTE: package openssl-native-1.0.0i-r0.2: task do_patch: Started
NOTE: package file-native-5.11-r0: task do_patch: Started
NOTE: package zlib-native-1.2.6-r1: task do_populate_sysroot: Succeeded
NOTE: Running task 153 of 1353 (ID: 161,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/pigz/pigz_2.2.4.bb,
do_configure)
NOTE: package curl-native-7.24.0-r2: task do_fetch: Succeeded
NOTE: package file-native-5.11-r0: task do_patch: Succeeded
NOTE: package pigz-native-2.2.4-r2: task do_configure: Started
NOTE: Running task 154 of 1353 (ID: 391,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-devtools/file/file_5.11.bb,
do_configure)
NOTE: Running task 155 of 1353 (ID: 320,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-support/curl/curl_7.24.0.bb,
do_unpack)
NOTE: package pigz-native-2.2.4-r2: task do_configure: Succeeded
NOTE: Running task 156 of 1353 (ID: 162,
virtual:native:/home/evadeflow/projects/poky-git/meta/recipes-extended/pigz/pigz_2.2.4.bb,
do_compile)
NOTE: package file-native-5.11-r0: task do_configure: Started
ERROR: Function failed: Unpack failure for URL:
'http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz'. Unpack command
PATH="/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin/armv5te-linux:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/sbin:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/sbin:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux//bin:/home/evadeflow/projects/poky-git/scripts/native-intercept:/home/evadeflow/projects/poky-git/scripts:/home/evadeflow/projects/poky-git/bitbake/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/evadeflow/projects/poky-git/scripts"
tar xz --no-same-owner -f
/home/evadeflow/projects/poky-git/build/downloads/perl-5.14.2.tar.gz failed with
return value 2
ERROR: Logfile of failure stored in:
/home/evadeflow/projects/poky-git/build/tmp/work/i686-linux/perl-native-5.14.2-r0/temp/log.do_unpack.3005
Log data follows:
| NOTE: Unpacking
/home/evadeflow/projects/poky-git/build/downloads/perl-5.14.2.tar.gz to
/home/evadeflow/projects/poky-git/build/tmp/work/i686-linux/perl-native-5.14.2-r0/
|
| gzip: stdin: invalid compressed data--crc error
| tar: Child returned status 1
| tar: Error is not recoverable: exiting now
| ERROR: Function failed: Unpack failure for URL:
'http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz'. Unpack command
PATH="/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin/armv5te-linux:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/sbin:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/sbin:/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux//bin:/home/evadeflow/projects/poky-git/scripts/native-intercept:/home/evadeflow/projects/poky-git/scripts:/home/evadeflow/projects/poky-git/bitbake/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/evadeflow/projects/poky-git/scripts"
tar xz --no-same-owner -f
/home/evadeflow/projects/poky-git/build/downloads/perl-5.14.2.tar.gz failed with
return value 2
NOTE: package perl-native-5.14.2-r0: task do_unpack: Failed
NOTE: package curl-native-7.24.0-r2: task do_unpack: Started
NOTE: package pigz-native-2.2.4-r2: task do_compile: Started
ERROR: Task 694
(/home/evadeflow/projects/poky-git/meta/recipes-devtools/perl/perl-native_5.14.2.bb,
do_unpack) failed with exit code '1'
Waiting for 15 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: eglibc-initial-2.13-r28+svnr15508 do_unpack (pid 2344)
2: eglibc-2.13-r28+svnr15508 do_unpack (pid 2345)
3: gperf-native-3.0.4-r0 do_configure (pid 2348)
4: binutils-cross-2.22-r6 do_unpack (pid 2617)
5: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
6: flex-native-2.5.35-r3 do_configure (pid 3635)
7: gmp-native-5.0.4-r0 do_configure (pid 3858)
8: bison-native-2.5-r1 do_configure (pid 4006)
9: ncurses-native-5.9-r9.1 do_configure (pid 4215)
10: elfutils-native-0.148-r7 do_unpack (pid 4229)
11: openssl-native-1.0.0i-r0.2 do_patch (pid 4244)
12: file-native-5.11-r0 do_configure (pid 4743)
13: curl-native-7.24.0-r2 do_unpack (pid 4748)
14: pigz-native-2.2.4-r2 do_compile (pid 4809)
NOTE: package pigz-native-2.2.4-r2: task do_compile: Succeeded
Waiting for 14 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: eglibc-initial-2.13-r28+svnr15508 do_unpack (pid 2344)
2: eglibc-2.13-r28+svnr15508 do_unpack (pid 2345)
3: gperf-native-3.0.4-r0 do_configure (pid 2348)
4: binutils-cross-2.22-r6 do_unpack (pid 2617)
5: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
6: flex-native-2.5.35-r3 do_configure (pid 3635)
7: gmp-native-5.0.4-r0 do_configure (pid 3858)
8: bison-native-2.5-r1 do_configure (pid 4006)
9: ncurses-native-5.9-r9.1 do_configure (pid 4215)
10: elfutils-native-0.148-r7 do_unpack (pid 4229)
11: openssl-native-1.0.0i-r0.2 do_patch (pid 4244)
12: file-native-5.11-r0 do_configure (pid 4743)
13: curl-native-7.24.0-r2 do_unpack (pid 4748)
NOTE: package elfutils-native-0.148-r7: task do_unpack: Succeeded
Waiting for 13 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: eglibc-initial-2.13-r28+svnr15508 do_unpack (pid 2344)
2: eglibc-2.13-r28+svnr15508 do_unpack (pid 2345)
3: gperf-native-3.0.4-r0 do_configure (pid 2348)
4: binutils-cross-2.22-r6 do_unpack (pid 2617)
5: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
6: flex-native-2.5.35-r3 do_configure (pid 3635)
7: gmp-native-5.0.4-r0 do_configure (pid 3858)
8: bison-native-2.5-r1 do_configure (pid 4006)
9: ncurses-native-5.9-r9.1 do_configure (pid 4215)
10: openssl-native-1.0.0i-r0.2 do_patch (pid 4244)
11: file-native-5.11-r0 do_configure (pid 4743)
12: curl-native-7.24.0-r2 do_unpack (pid 4748)
NOTE: package openssl-native-1.0.0i-r0.2: task do_patch: Succeeded
Waiting for 12 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: eglibc-initial-2.13-r28+svnr15508 do_unpack (pid 2344)
2: eglibc-2.13-r28+svnr15508 do_unpack (pid 2345)
3: gperf-native-3.0.4-r0 do_configure (pid 2348)
4: binutils-cross-2.22-r6 do_unpack (pid 2617)
5: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
6: flex-native-2.5.35-r3 do_configure (pid 3635)
7: gmp-native-5.0.4-r0 do_configure (pid 3858)
8: bison-native-2.5-r1 do_configure (pid 4006)
9: ncurses-native-5.9-r9.1 do_configure (pid 4215)
10: file-native-5.11-r0 do_configure (pid 4743)
11: curl-native-7.24.0-r2 do_unpack (pid 4748)
NOTE: package curl-native-7.24.0-r2: task do_unpack: Succeeded
Waiting for 11 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: eglibc-initial-2.13-r28+svnr15508 do_unpack (pid 2344)
2: eglibc-2.13-r28+svnr15508 do_unpack (pid 2345)
3: gperf-native-3.0.4-r0 do_configure (pid 2348)
4: binutils-cross-2.22-r6 do_unpack (pid 2617)
5: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
6: flex-native-2.5.35-r3 do_configure (pid 3635)
7: gmp-native-5.0.4-r0 do_configure (pid 3858)
8: bison-native-2.5-r1 do_configure (pid 4006)
9: ncurses-native-5.9-r9.1 do_configure (pid 4215)
10: file-native-5.11-r0 do_configure (pid 4743)
NOTE: package eglibc-initial-2.13-r28+svnr15508: task do_unpack: Succeeded
Waiting for 10 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: eglibc-2.13-r28+svnr15508 do_unpack (pid 2345)
2: gperf-native-3.0.4-r0 do_configure (pid 2348)
3: binutils-cross-2.22-r6 do_unpack (pid 2617)
4: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
5: flex-native-2.5.35-r3 do_configure (pid 3635)
6: gmp-native-5.0.4-r0 do_configure (pid 3858)
7: bison-native-2.5-r1 do_configure (pid 4006)
8: ncurses-native-5.9-r9.1 do_configure (pid 4215)
9: file-native-5.11-r0 do_configure (pid 4743)
NOTE: package eglibc-2.13-r28+svnr15508: task do_unpack: Succeeded
Waiting for 9 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: gperf-native-3.0.4-r0 do_configure (pid 2348)
2: binutils-cross-2.22-r6 do_unpack (pid 2617)
3: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
4: flex-native-2.5.35-r3 do_configure (pid 3635)
5: gmp-native-5.0.4-r0 do_configure (pid 3858)
6: bison-native-2.5-r1 do_configure (pid 4006)
7: ncurses-native-5.9-r9.1 do_configure (pid 4215)
8: file-native-5.11-r0 do_configure (pid 4743)
NOTE: package binutils-cross-2.22-r6: task do_unpack: Succeeded
Waiting for 8 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: gperf-native-3.0.4-r0 do_configure (pid 2348)
2: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
3: flex-native-2.5.35-r3 do_configure (pid 3635)
4: gmp-native-5.0.4-r0 do_configure (pid 3858)
5: bison-native-2.5-r1 do_configure (pid 4006)
6: ncurses-native-5.9-r9.1 do_configure (pid 4215)
7: file-native-5.11-r0 do_configure (pid 4743)
NOTE: package gperf-native-3.0.4-r0: task do_configure: Succeeded
Waiting for 7 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
2: flex-native-2.5.35-r3 do_configure (pid 3635)
3: gmp-native-5.0.4-r0 do_configure (pid 3858)
4: bison-native-2.5-r1 do_configure (pid 4006)
5: ncurses-native-5.9-r9.1 do_configure (pid 4215)
6: file-native-5.11-r0 do_configure (pid 4743)
NOTE: package flex-native-2.5.35-r3: task do_configure: Succeeded
Waiting for 6 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
2: gmp-native-5.0.4-r0 do_configure (pid 3858)
3: bison-native-2.5-r1 do_configure (pid 4006)
4: ncurses-native-5.9-r9.1 do_configure (pid 4215)
5: file-native-5.11-r0 do_configure (pid 4743)
NOTE: package file-native-5.11-r0: task do_configure: Succeeded
Waiting for 5 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
2: gmp-native-5.0.4-r0 do_configure (pid 3858)
3: bison-native-2.5-r1 do_configure (pid 4006)
4: ncurses-native-5.9-r9.1 do_configure (pid 4215)
NOTE: package ncurses-native-5.9-r9.1: task do_configure: Succeeded
Waiting for 4 running tasks to finish:
0: gcc-cross-initial-4.6.3+svnr184847-r28 do_unpack (pid 2304)
1: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
2: gmp-native-5.0.4-r0 do_configure (pid 3858)
3: bison-native-2.5-r1 do_configure (pid 4006)
NOTE: package gcc-cross-initial-4.6.3+svnr184847-r28: task do_unpack:
Succeeded
Waiting for 3 running tasks to finish:
0: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
1: gmp-native-5.0.4-r0 do_configure (pid 3858)
2: bison-native-2.5-r1 do_configure (pid 4006)
NOTE: package gmp-native-5.0.4-r0: task do_configure: Succeeded
Waiting for 2 running tasks to finish:
0: linux-libc-headers-3.2-r1 do_unpack (pid 3027)
1: bison-native-2.5-r1 do_configure (pid 4006)
NOTE: package linux-libc-headers-3.2-r1: task do_unpack: Succeeded
Waiting for 1 running tasks to finish:
0: bison-native-2.5-r1 do_configure (pid 4006)
NOTE: package bison-native-2.5-r1: task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 156 tasks of which 74 didn't need to be rerun
and 1 failed.

Summary: 1 task failed:
/home/evadeflow/projects/poky-git/meta/recipes-devtools/perl/perl-native_5.14.2.bb,
do_unpack
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
bitbake core-image-minimal 486.67s user 110.35s system 213% cpu 4:39.60

On Fri, Sep 28, 2012 at 10:16 AM, Evade Flow <evadeflow@...> wrote:
Seems it definitely didn't build tar:

evadeflow% pwd
/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin
evadeflow% ls t*
tabs tailf taskset tic toe tput tset tunctl tzselect
evadeflow% tar --version
tar (GNU tar) 1.22
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.


This is on denzil, BTW. (Maybe the check against the tar version was added
later?)


evadeflow% bitbake core-image-sato
WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated
with this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
Parsing recipes: 100%
|###################################################################|
Time: 00:00:07
Parsing of 829 .bb files complete (0 cached, 829 parsed). 1105
targets, 34 skipped, 0 masked, 0 errors.

OE Build Configuration:
BB_VERSION = "1.15.2"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "qemuarm"
DISTRO = "poky"
DISTRO_VERSION = "1.2.1"
TUNE_FEATURES = "armv5 dsp thumb arm926ejs"
TARGET_FPU = "soft"
meta
meta-yocto = "denzil:65ffa7395055f7e012cb973f63f92380828eed0d"


Maybe I got my build tree into an inconsistent state somehow when I was trying
to 'fix' this. I can try rebuilding if it helps, using the original perl
archive (not the one I re-tarballed with tar 1.22)...


On Thu, Sep 27, 2012 at 6:58 PM, Paul Eggleton
<paul.eggleton@...> wrote:
On Thursday 27 September 2012 17:55:45 Evade Flow wrote:
Fair enough. And I should mention that the error I reported occurs on
Ubuntu 10.04. It's not like I wasn't warned. :-}

WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated
with this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.

(Other than this oddity with the perl package, things seem to work fine.)
Yeah, it's just a warning :)

This issue is rather perplexing. We're supposed to not be using the host tar
if it is older than 1.24 due to another bug in earlier versions - if an older
version is found we build tar-replacement-native before anything else gets
built. Was tar-replacement-native built on the machine where it was failing?
You can verify it built by just checking under tmp/sysroots/<native
sysroot>/usr/bin/ to see if tar exists there.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre


Re: build failure on current

Paul Eggleton
 

On Friday 28 September 2012 10:16:27 Evade Flow wrote:
Seems it definitely didn't build tar:

evadeflow% pwd
/home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin
Just to confirm, this is the same path you get if you run "cat pseudodone" in
your build directory?

evadeflow% ls t*
tabs tailf taskset tic toe tput tset tunctl tzselect
evadeflow% tar --version
tar (GNU tar) 1.22
...
This is on denzil, BTW. (Maybe the check against the tar version was added
later?)
No, the code to do this was there in denzil as well. Here's the code cut out
into a shell script - could you put this into a file and run it and tell me
what it prints on your system?

--------------- snip --------------
#!/bin/sh
needtar=1
TARVERSION=`tar --version | head -n 1 | cut -d ' ' -f 4`
float_test() {
echo | awk 'END { exit ( !( '"$1"')); }'
}

# Tar version 1.24 and onwards handle overwriting symlinks correctly
# but earlier versions do not; this needs to work properly for sstate
float_test "$TARVERSION > 1.23" && needtar="0"
echo $needtar
--------------- snip --------------

Thanks,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre