| Summary: | ERROR: No recipes available for: | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BSPs | Reporter: | Sukruth <sukruth.h.v> |
| Component: | bsps-meta-intel | Assignee: | Darren Hart <dvhart> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | bluelightning, dvhart, jefro, meta.mr.watcher, meta.watcher, nitin.a.kamble, poky.bs.watcher, poky.watcher, richard.purdie, sgw, srifenbark, tom.zanussi |
| Version: | 1.3 | ||
| Target Milestone: | 1.3 | ||
| Hardware: | x86 | ||
| OS: | x86_64 | ||
| Whiteboard: | 24 March 2014: Set Documentation flag to "Done". | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Done (doc changes complete) | |
This sounds very much like you have the wrong version of the meta-intel layer. You need the version of meta-intel which corresponds to the danny release, it sounds like you have something more recent. Can you provide links or git hashes/urls for what you downloaded please? Sukruth, can you please comment on Richard's note, it does seem like you have mis-matched version of danny and meta-intel. I found the page you are refering to and I think this is more of a documentation issue in the release notes, it should not have master/head listed for the dependencies. Nitin, our BSP READMEs in meta-intel reference the master branch of the layers which should be changed in the release branches to reflect using the same branch as the meta-intel release. For example: meta-crownbay/README: Dependencies ============ This layer depends on: URI: git://git.openembedded.org/bitbake branch: master URI: git://git.openembedded.org/openembedded-core layers: meta branch: master URI: git://git.yoctoproject.org/meta-intel layers: intel branch: master we should replace master with the release branch for each of the release branches. Or at the very least for dylan and danny. Darren, This makes very much sense. I will update the danny & dylan brnaches of meta intel for all the BSPs. Nitin BTW the branchname for oecore & bitbake layers can not be switch to dylan, so what to do with the master branchname for these layers? Nitin (In reply to comment #5) > BTW the branchname for oecore & bitbake layers can not be switch to dylan, > so what to do with the master branchname for these layers? > > Nitin Why not? dvhart@envy:~/source/yocto/oe-core [master] $ git branch -a | grep origin remotes/origin/2011-1 remotes/origin/HEAD -> origin/master remotes/origin/danny remotes/origin/denzil remotes/origin/denzil-next remotes/origin/dylan remotes/origin/master remotes/origin/master-next For bitbake.... huh, I don't know. Ask RP I suppose. dvhart@envy:~/source/yocto/bitbake [1.3] $ git branch -a | grep origin remotes/origin/1.10 remotes/origin/1.12 remotes/origin/1.14 remotes/origin/1.16 remotes/origin/1.18 remotes/origin/1.3 remotes/origin/1.4 remotes/origin/1.6 remotes/origin/1.8 remotes/origin/HEAD -> origin/master remotes/origin/master remotes/origin/master-next remotes/origin/master-poky remotes/origin/next remotes/origin/pristine-tar remotes/origin/wmat bitbake has different release cycle as seen here: http://cgit.openembedded.org/bitbake/refs/heads oecore has a matching release cycle as seen here: http://cgit.openembedded.org/openembedded-core/ RP, a question for you here. Nitin, each oe-core/poky has a minimum bitbake version based on the BB_MIN_VERSION, you can find that in meta/conf/sanity.conf (In reply to comment #5) > BTW the branchname for oecore The branchname for OE-Core is dylan. > & bitbake layers can not be switch to dylan, > so what to do with the master branchname for these layers? bitbake is treated as a separate project and has a version number series with point releases. OE-Core defines a particular version requirement for each release. Has this been addressed to everyone's satisfaction? No comments here, so I'm assuming this has been taken care of satisfactorily. Please reopen if this is not the case. I have added two separate notes to the YP docs to make sure users understand the importance of working from matching branches with meta-intel and poky. http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#supported-board-support-packages-(bsps) http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#yocto-project-repositories Darren Hart approved the base note information. I am turning the documentation flag to "Done." Scott |
Hi, I am building the minimal image of the Yocto and encountered the following errors :- sukruth@sukruth-desktop:~/yocto_toolchain/poky-danny-8.0/build$ bitbake core-image-minimal WARNING: Host distribution "Ubuntu 12.04.2 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:15 Parsing of 847 .bb files complete (0 cached, 847 parsed). 1152 targets, 30 skipped, 0 masked, 0 errors. ERROR: No recipes available for: /home/sukruth/yocto_toolchain/poky-danny-8.0/build/meta-intel/meta-n450/recipes-kernel/linux/linux-yocto_3.8.bbappend /home/sukruth/yocto_toolchain/poky-danny-8.0/build/meta-intel/meta-n450/recipes-kernel/linux/linux-yocto-rt_3.8.bbappend /home/sukruth/yocto_toolchain/poky-danny-8.0/build/meta-intel/common/recipes-graphics/mesa/mesa_9.0.2.bbappend ERROR: Command execution failed: Exited with 1 Summary: There was 1 WARNING message shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. sukruth@sukruth-desktop:~/yocto_toolchain/poky-danny-8.0/build$ cd meta-intel/common/recipes-graphics/mesa/ sukruth@sukruth-desktop:~/yocto_toolchain/poky-danny-8.0/build/meta-intel/common/recipes-graphics/mesa$ ls mesa_9.0.2.bbappend I am using "Poky-danny-8.0" and i have provided with the necessary path for the Meta-intel package in bblayers.conf that i have downloaded as per instructions provided in "yocto-project.org/download/intel-core-i3-i5-and-i7", But infact getting the above mentioned errors. Regards, Sukruth H V