Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
Even after using your workaround i can still reproduce this issue. Yocto linux still fails. | 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 ERROR: Task 3 (/media/HDD/yocto/poky/meta/recipes-kernel/linux/ linux-yocto_3.0.bb, do_patch) failed with exit code '1' On Thu, May 17, 2012 at 11:48 PM, Flanagan, Elizabeth elizabeth.flana...@intel.com wrote: On Thu, May 17, 2012 at 7:59 AM, Andrei Gherzan and...@gherzan.ro wrote: Today i just gave another try same result. Responding here as well as the yocto list: A few people have been having this issue and after some discussion we think we have a root cause. Let me first explain what happened. The autobuilder infrastructure shares a common DL_DIR in order to optimize the builds and provide the source mirror. This DL_DIR is rsynced to the publicaly available source mirror on a regular basis. During our infrastructure upgrade the autobuilder attempted to pull the tar archive for linux-yocto-3.0 ( http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz ) but due to network issues related to our recent infrastructure upgrade the file ended up as a 0 byte file. This file was rsynced the the source mirror. A few days ago this was mentioned as an issue. Michael Halstead corrected the network issue and I manually removed the file. The autobuilder repulled the archive correctly and repopulated the source mirror with it. Things should have been ok at this point. However, we were still getting reports of people sporadically running into a 0 byte file. Not all the time, but some of the time. Michael Halstead and I just tailed out the apache logs with Tom Zanussi wgetting the problematic file, watching for failures. No failures were seen in the error logs however Tom was still getting sporadic 0 byte files. Which means that his request wasn't even hitting the server. I was not able to replicate this. The only difference we could see is that I generally do not go through a proxy whereas Tom was. Our theory at this point is that all of the people who are hitting this issue are going through a proxy and that their proxy setup has cached that 0 byte file and refuses to regenerate it. There isn't a lot we can do from our end about that other than suggest the following work around. If you run into odd fetch issues with *just* the linux-yocto-3.0 tar archive, clear out your DL_DIR of git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz and set the following: PREMIRRORS ?= \ bzr://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ cvs://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ hg://.*/.*http://autobuilder.yoctoproject.org/sources/ \n \ osc://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ p4://.*/.*http://autobuilder.yoctoproject.org/sources/ \n \ svk://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ svn://.*/.* http://autobuilder.yoctoproject.org/sources/ \n MIRRORS =+ \ ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ https://.*/.*http://autobuilder.yoctoproject.org/sources/ \n This will force the fetch to go to the autobuilder host of sources and should work around any proxy caching issues. Then call your local IT folks and ask them to clear out your proxy cache. If you run into any fetch issues not related to this file, please let me know. -b ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
Same for me again on a try today: | build/tmp-eglibc-eglibc/sysroots/x86_64-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 Florin On 05/22/2012 01:02 PM, Andrei Gherzan wrote: Even after using your workaround i can still reproduce this issue. Yocto linux still fails. | 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 ERROR: Task 3 (/media/HDD/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb http://linux-yocto_3.0.bb, do_patch) failed with exit code '1' On Thu, May 17, 2012 at 11:48 PM, Flanagan, Elizabeth elizabeth.flana...@intel.com mailto:elizabeth.flana...@intel.com wrote: On Thu, May 17, 2012 at 7:59 AM, Andrei Gherzan and...@gherzan.ro mailto:and...@gherzan.ro wrote: Today i just gave another try same result. Responding here as well as the yocto list: A few people have been having this issue and after some discussion we think we have a root cause. Let me first explain what happened. The autobuilder infrastructure shares a common DL_DIR in order to optimize the builds and provide the source mirror. This DL_DIR is rsynced to the publicaly available source mirror on a regular basis. During our infrastructure upgrade the autobuilder attempted to pull the tar archive for linux-yocto-3.0 (http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz) but due to network issues related to our recent infrastructure upgrade the file ended up as a 0 byte file. This file was rsynced the the source mirror. A few days ago this was mentioned as an issue. Michael Halstead corrected the network issue and I manually removed the file. The autobuilder repulled the archive correctly and repopulated the source mirror with it. Things should have been ok at this point. However, we were still getting reports of people sporadically running into a 0 byte file. Not all the time, but some of the time. Michael Halstead and I just tailed out the apache logs with Tom Zanussi wgetting the problematic file, watching for failures. No failures were seen in the error logs however Tom was still getting sporadic 0 byte files. Which means that his request wasn't even hitting the server. I was not able to replicate this. The only difference we could see is that I generally do not go through a proxy whereas Tom was. Our theory at this point is that all of the people who are hitting this issue are going through a proxy and that their proxy setup has cached that 0 byte file and refuses to regenerate it. There isn't a lot we can do from our end about that other than suggest the following work around. If you run into odd fetch issues with *just* the linux-yocto-3.0 tar archive, clear out your DL_DIR of git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz and set the following: PREMIRRORS ?= \ bzr://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ cvs://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ hg://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ osc://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ p4://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ svk://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ svn://.*/.* http://autobuilder.yoctoproject.org/sources/ \n MIRRORS =+ \ ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n This will force the fetch to go to the autobuilder host of sources and should work around any proxy caching issues. Then call your local IT folks and ask them to clear out your proxy cache. If you run into any fetch issues not related to this file, please let me know. -b ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org mailto:Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
On Tue, 2012-05-22 at 13:02 +0300, Andrei Gherzan wrote: Even after using your workaround i can still reproduce this issue. Yocto linux still fails. | 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 ERROR: Task 3 (/media/HDD/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb, do_patch) failed with exit code '1' Have you tried this against a clean DL_DIR so there is no risk of any of the files contained within there being corrupted? We need to get to the bottom of this but most people who were reporting issues have reported this as resolved now... Cheers, Richard ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
This one above was on a clean DL_DIR. @g On Tue, May 22, 2012 at 4:20 PM, Richard Purdie richard.pur...@linuxfoundation.org wrote: On Tue, 2012-05-22 at 13:02 +0300, Andrei Gherzan wrote: Even after using your workaround i can still reproduce this issue. Yocto linux still fails. | 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 ERROR: Task 3 (/media/HDD/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb, do_patch) failed with exit code '1' Have you tried this against a clean DL_DIR so there is no risk of any of the files contained within there being corrupted? We need to get to the bottom of this but most people who were reporting issues have reported this as resolved now... Cheers, Richard ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
FWIW, I just did a fresh minimal beagleboard build without any workaround and didn't see any problems building. This was using the proxy setup that had previously failed for me with the zero-length 3.0 kernel tarball. Tom On Tue, 2012-05-22 at 13:02 +0300, Andrei Gherzan wrote: Even after using your workaround i can still reproduce this issue. Yocto linux still fails. | 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 ERROR: Task 3 (/media/HDD/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb, do_patch) failed with exit code '1' On Thu, May 17, 2012 at 11:48 PM, Flanagan, Elizabeth elizabeth.flana...@intel.com wrote: On Thu, May 17, 2012 at 7:59 AM, Andrei Gherzan and...@gherzan.ro wrote: Today i just gave another try same result. Responding here as well as the yocto list: A few people have been having this issue and after some discussion we think we have a root cause. Let me first explain what happened. The autobuilder infrastructure shares a common DL_DIR in order to optimize the builds and provide the source mirror. This DL_DIR is rsynced to the publicaly available source mirror on a regular basis. During our infrastructure upgrade the autobuilder attempted to pull the tar archive for linux-yocto-3.0 (http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz) but due to network issues related to our recent infrastructure upgrade the file ended up as a 0 byte file. This file was rsynced the the source mirror. A few days ago this was mentioned as an issue. Michael Halstead corrected the network issue and I manually removed the file. The autobuilder repulled the archive correctly and repopulated the source mirror with it. Things should have been ok at this point. However, we were still getting reports of people sporadically running into a 0 byte file. Not all the time, but some of the time. Michael Halstead and I just tailed out the apache logs with Tom Zanussi wgetting the problematic file, watching for failures. No failures were seen in the error logs however Tom was still getting sporadic 0 byte files. Which means that his request wasn't even hitting the server. I was not able to replicate this. The only difference we could see is that I generally do not go through a proxy whereas Tom was. Our theory at this point is that all of the people who are hitting this issue are going through a proxy and that their proxy setup has cached that 0 byte file and refuses to regenerate it. There isn't a lot we can do from our end about that other than suggest the following work around. If you run into odd fetch issues with *just* the linux-yocto-3.0 tar archive, clear out your DL_DIR of git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz and set the following: PREMIRRORS ?= \ bzr://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ cvs://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ hg://.*/.*http://autobuilder.yoctoproject.org/sources/ \n \ osc://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ p4://.*/.*http://autobuilder.yoctoproject.org/sources/ \n \ svk://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ svn://.*/.* http://autobuilder.yoctoproject.org/sources/ \n MIRRORS =+ \ ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ https://.*/.*http://autobuilder.yoctoproject.org/sources/ \n This will force the fetch to go to the autobuilder host of sources and should work around any proxy caching issues. Then call your local IT folks and ask them to clear out your proxy cache. If you run into any fetch issues not related to this file, please let me know. -b
[OE-core] Linux-yocto 3.0 crashes at do_patch...
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 |
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
I confirm I still encounter the same error. On 05/17/2012 01:09 PM, Andrei Gherzan 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:
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
On Thu, May 17, 2012 at 6:09 AM, Andrei Gherzan and...@gherzan.ro 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: The tools fixes are in place for this, can you send your full configuration ? i.e. what layers, their head commits, and machine config. Bruce 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
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
On Thu, May 17, 2012 at 6:09 AM, Andrei Gherzan and...@gherzan.ro 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
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
On 05/17/2012 04:38 PM, Bruce Ashfield wrote: On Thu, May 17, 2012 at 6:09 AM, Andrei Gherzanand...@gherzan.ro 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) |
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
On Thu, May 17, 2012 at 6:41 AM, Andrei Gherzan and...@gherzan.ro wrote: On 05/17/2012 04:38 PM, Bruce Ashfield wrote: On Thu, May 17, 2012 at 6:09 AM, Andrei Gherzanand...@gherzan.ro 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
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
Today i just gave another try same result. On Thu, May 17, 2012 at 5:56 PM, Flanagan, Elizabeth elizabeth.flana...@intel.com wrote: On Thu, May 17, 2012 at 6:41 AM, Andrei Gherzan and...@gherzan.ro wrote: On 05/17/2012 04:38 PM, Bruce Ashfield wrote: On Thu, May 17, 2012 at 6:09 AM, Andrei Gherzanand...@gherzan.ro 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 |
Re: [OE-core] Linux-yocto 3.0 crashes at do_patch...
On Thu, May 17, 2012 at 7:59 AM, Andrei Gherzan and...@gherzan.ro wrote: Today i just gave another try same result. Responding here as well as the yocto list: A few people have been having this issue and after some discussion we think we have a root cause. Let me first explain what happened. The autobuilder infrastructure shares a common DL_DIR in order to optimize the builds and provide the source mirror. This DL_DIR is rsynced to the publicaly available source mirror on a regular basis. During our infrastructure upgrade the autobuilder attempted to pull the tar archive for linux-yocto-3.0 (http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz) but due to network issues related to our recent infrastructure upgrade the file ended up as a 0 byte file. This file was rsynced the the source mirror. A few days ago this was mentioned as an issue. Michael Halstead corrected the network issue and I manually removed the file. The autobuilder repulled the archive correctly and repopulated the source mirror with it. Things should have been ok at this point. However, we were still getting reports of people sporadically running into a 0 byte file. Not all the time, but some of the time. Michael Halstead and I just tailed out the apache logs with Tom Zanussi wgetting the problematic file, watching for failures. No failures were seen in the error logs however Tom was still getting sporadic 0 byte files. Which means that his request wasn't even hitting the server. I was not able to replicate this. The only difference we could see is that I generally do not go through a proxy whereas Tom was. Our theory at this point is that all of the people who are hitting this issue are going through a proxy and that their proxy setup has cached that 0 byte file and refuses to regenerate it. There isn't a lot we can do from our end about that other than suggest the following work around. If you run into odd fetch issues with *just* the linux-yocto-3.0 tar archive, clear out your DL_DIR of git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz and set the following: PREMIRRORS ?= \ bzr://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ cvs://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ hg://.*/.*http://autobuilder.yoctoproject.org/sources/ \n \ osc://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ p4://.*/.*http://autobuilder.yoctoproject.org/sources/ \n \ svk://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ svn://.*/.* http://autobuilder.yoctoproject.org/sources/ \n MIRRORS =+ \ ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \ https://.*/.*http://autobuilder.yoctoproject.org/sources/ \n This will force the fetch to go to the autobuilder host of sources and should work around any proxy caching issues. Then call your local IT folks and ask them to clear out your proxy cache. If you run into any fetch issues not related to this file, please let me know. -b ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
