| Summary: | Yocto BSP create via JSON file fails - do_patch error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | Laurentiu Serban <laurentiu.serban> | ||||
| Component: | linux-yocto | Assignee: | Tom Zanussi <tom.zanussi> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Undecided | ||||||
| Version: | 1.3 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | --- | |||||
| Attachments: |
|
||||||
Please when reporting always specify which branches you're using for each of the layers you're using along with the checked-out commits for those branches. As it stands, I have no way of reproducing or testing this myself - this should have been fixed in both denzil and master and is something I did test for Bug 2693. To verify, I successfully created new bsps using the same json file and was successful with both denzil and master when using the following commits: poky/denzil: 65ffa7395055f7e012cb973f63f92380828eed0d poky/master: 5343cdb20ee56a8b507733c637dcc2466ae13288 |
Created attachment 775 [details] log do patch failure Using this text in the json file: {"kernel_choice":"linux-yocto_3.2","use_default_kernel":"n","keyboard":"y","qemuarch":"i386","smp":"y","touchscreen":"n","need_new_kbranch":"y","new_kbranch":"standard/default/base"} After creating the layer using yocto-bsp command and adding the resulting layer to tbe bblayers.conf, running bitbake core-image-minimal returns the following errors: ERROR: Function failed: do_patch (see /home/lserban/work/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+7cc31a952f78b8f8e8469eed93c23e9675a8eeb5-r4.0.1/temp/log.do_patch.27238 for further information) ERROR: Logfile of failure stored in: /home/lserban/work/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+7cc31a952f78b8f8e8469eed93c23e9675a8eeb5-r4.0.1/temp/log.do_patch.27238 Log data follows: | DEBUG: Executing shell function do_patch | Branch meta-temp set up to track remote branch meta from origin. | Deleted branch meta-temp (was 3499d64). | warning: could not find (or was already included): features/logbuf/size-normal.scc (/home/lserban/work/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+7cc31a952f78b8f8e8469eed93c23e9675a8eeb5-r4.0.1/linux/meta/cfg/scratch/obj/home/lserban/work/poky/meta-mymachine/recipes-kernel/linux/files) | warning: could not find (or was already included): user-patches.scc (/home/lserban/work/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+7cc31a952f78b8f8e8469eed93c23e9675a8eeb5-r4.0.1/linux/meta/cfg/scratch/obj/home/lserban/work/poky/meta-mymachine/recipes-kernel/linux/files) | [INFO] validating against known patches (myqemux86-standard-meta) Branch standard/default/common-pc/myqemux86 set up to track remote branch standard/default/common-pc/base from origin. | error: pathspec 'standard/default/base/myqemux86' did not match any file(s) known to git. | ERROR: could not complete git cmd "git checkout standard/default/base/myqemux86" | ERROR. could not update git tree | ERROR. Could not apply updates for myqemux86 | ERROR: Function failed: do_patch (see /home/lserban/work/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto-3.2.18+git1+486f7aec824b4127e91ef53228823e996b3696f0_1+7cc31a952f78b8f8e8469eed93c23e9675a8eeb5-r4.0.1/temp/log.do_patch.27238 for further information) ERROR: Task 703 (/home/lserban/work/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb, do_patch) failed with exit code '1' NOTE: Tasks Summary: Attempted 1487 tasks of which 1352 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/lserban/work/poky/meta/recipes-kernel/linux/linux-yocto_3.2.bb, do_patch Summary: There were 5 WARNING messages shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code.