On 05/17/2012 04:38 PM, Bruce Ashfield wrote:
On Thu, May 17, 2012 at 6:09 AM, Andrei Gherzan<[email protected]> wrote:
Today i ran into an issue that Florin Sarbu signaled sometime last week. It
seems like do_patch crashes while compiling linux 3.0:
ERROR: Logfile of failure stored in:
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/work/vexpressa9-poky-linux-gnueabi/linux-yocto-3.0.24+git1+34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23_1+6b4bf6173b0bd2d1619a8218bac66ebc4681dd35-r4/temp/log.do_patch.10864
Log data follows:
| Branch meta-temp set up to track remote branch meta from origin.
| git reset --mixed 620917de59eeb934b9f8cf35cc2d95c1ac8ed0fc
| Deleted branch meta-temp (was 620917d).
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme:
line 434: yocto/standard/beagleboard-standard.scc: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme:
line 436: yocto/standard/beagleboard-standard.scc: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme:
line 437: yocto/standard/beagleboard-standard.scc: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme:
line 438: yocto/standard/beagleboard-standard.scc: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/updateme:
line 441: yocto/standard/beagleboard-standard.scc: No such file or directory
| readlink: missing operand
| Try `readlink --help' for more information.
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
| /media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmERROR: Function failed:
do_patch (see
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/work/vexpressa9-poky-linux-gnueabi/linux-yocto-3.0.24+git1+34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23_1+6b4bf6173b0bd2d1619a8218bac66ebc4681dd35-r4/temp/log.do_patch.10864
for further information)
| p/sysroots/i686-linux/usr/bin/scc: line 399:
yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
|
/media/HDD-WRS/yocto/2012-05-10-discovery-vea9/tmp/sysroots/i686-linux/usr/bin/scc:
line 399: yocto/standard/beagleboard-standard: No such file or directory
| ERROR. Could not find an excutable target for yocto/standard/base
| ERROR. Could not locate meta series for yocto/standard/beagleboard
| ERROR. Could not modify yocto/standard/base
NOTE: package
linux-yocto-3.0.24+git1+34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23_1+6b4bf6173b0bd2d1619a8218bac66ebc4681dd35-r4:
task do_patch: Failed
I didn't have time to understand were is the source of this problem but i
suspect that is a sever-sided issue as this was reproducible yesterday even
if i didn't change anything in layers.
I should remember to read all the way to the bottom :) I just
configured and built the beagle
board here, out of master. But my kernel is already fetched and
complete, so I didn't
run into any issues.
We've got other reports of the servers pushing out a zero byte file
for the kernel tree
(again), so that very well could be what is happening here as well.
That's my opinion as well. I think what we got from server is corrupted.
Anyway i'm was talking about a vexpressa9 machine based on beagleboard
kernel.
Hope somebody will find the fast fix for this. We need it asap.
@g
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
