Re: [oe] [meta-maker] Octoprint on Intel Edison (yocto dizzy): failed python-flask RDEPENDS
On December 30, 2016 7:14:28 AM CET, Vincent Rubiolo <vincent.li...@cryostase.eu> wrote: >Hi everyone, > >I am trying to include the meta-maker layer to enable octoprint on the >Intel Edison. I am using the Yocto project drop that Intel provides[1] >and successfully built it (with a reduced set of packages, I am >interested only in the bits necessary to enable Octoprint). > >Intel drop appears to be based on the yocto daisy branch (bitbake >reports so during a build + I diffed the meta-openembedded daisy git >tree against the Intel drop). I have thus checked out that branch of >meta-maker and added it under my poky subdirectory + added it to >bblayers.conf. > >The problem I have is that the build fails because of a missing >RDEPENDS: >+++ >$ bitbake octoprint -c fetchall >WARNING: Host distribution "Fedora-23" 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. >Loading cache: 100% >|| >ETA: 00:00:00 >Loaded 2170 entries from dependency cache. >NOTE: Resolving any missing task queue dependencies >NOTE: multiple providers are available for python-distribute-native >(python-distribute-native, python-setuptools-native) >NOTE: consider defining a PREFERRED_PROVIDER entry to match >python-distribute-native >ERROR: Nothing RPROVIDES 'python-flask' (but >/yocto/iot-devkit-yp-poky-edison-20160606/build_edison/../poky/meta-openembedded/meta-maker/recipes-webui/octoprint/octoprint_git.bb > >RDEPENDS on or otherwise requires it) >NOTE: Runtime target 'python-flask' is unbuildable, removing... >Missing or unbuildable dependency chain was: ['python-flask'] >ERROR: Required build target 'octoprint' has no buildable providers. >Missing or unbuildable dependency chain was: ['octoprint', >'python-flask'] > >Summary: There was 1 WARNING message shown. >Summary: There were 2 ERROR messages shown, returning a non-zero exit >code. >+++ > >In the meta-maker and meta-openembedded trees dizzy branches, I see no >python-flask recipe/package. It looks to me the patch for octoprint >1.2.10 has been merged into the meta-maker dizzy branch with the >RDEPENDS list still matching that of the newest meta-openembedded (but >I >might be wrong). > >Is my analysis correct? If so, is there a way to know which RDEPEND I >should use for octoprint in the dizzy branch to match the >meta-openembedded one? > >Another possibility could be to use the meta-intel-edison from the >yocto >project git repo[2] with meta-openembedded & meta-maker on master but I > >have yet to try that. > >Thanks a lot for your help! > >Vincent > >[1] >http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip >[2] http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-edison/ > >To reproduce: >get >http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip > >and unzip >cd iot-devkit-yp-poky-edison-20160606/poky/meta-openembedded >git clone git://git.yoctoproject.org/meta-maker -b dizzy >add meta-maker layer to >iot-devkit-yp-poky-edison-20160606/build_edison/conf/bblayers.conf >cd iot-devkit-yp-poky-edison-20160606/poky/ >source oe-init-build-env ../build_edison/ >bitbake octoprint -c fetchall Hello, Would somebody have some advice here? Thanks much, Vincent -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-maker] Octoprint on Intel Edison (yocto dizzy): failed python-flask RDEPENDS
Hello again,
On 12/29/2016 10:14 PM, Vincent Rubiolo wrote:
Another possibility could be to use the meta-intel-edison from the yocto
project git repo[2] with meta-openembedded & meta-maker on master but I
have yet to try that.
I have tried to do that after I sent this email and this does not appear
to be possible. I hit an error about the SAVANNAH_GNU_MIRROR being
missing when bitbake is called:
+++
ERROR: ExpansionError during parsing
/yocto/build_edison/../poky/meta-openembedded/meta-oe/recipes-support/lzip/lzip_1.16.bb:
Failure expanding variable do_fetch[file-checksums], expression was
${@bb.fetch.get_checksum_file_list(d)} which triggered exception
MalformedUrl: The URL: '${SAVANNAH_GNU_MIRROR}/lzip/lzip-1.16.tar.gz' is
invalid and cannot be interpreted
+++
It looks like this is because meta-openembedded and poky have to
version-match[1].
I thus look forward to your advice very much (as I do not see any
workaround anymore).
Thanks again,
Vincent
[1]
https://lists.yoctoproject.org/pipermail/yocto/2014-September/021716.html
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-maker] Octoprint on Intel Edison (yocto dizzy): failed python-flask RDEPENDS
Hi everyone, I am trying to include the meta-maker layer to enable octoprint on the Intel Edison. I am using the Yocto project drop that Intel provides[1] and successfully built it (with a reduced set of packages, I am interested only in the bits necessary to enable Octoprint). Intel drop appears to be based on the yocto daisy branch (bitbake reports so during a build + I diffed the meta-openembedded daisy git tree against the Intel drop). I have thus checked out that branch of meta-maker and added it under my poky subdirectory + added it to bblayers.conf. The problem I have is that the build fails because of a missing RDEPENDS: +++ $ bitbake octoprint -c fetchall WARNING: Host distribution "Fedora-23" 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. Loading cache: 100% || ETA: 00:00:00 Loaded 2170 entries from dependency cache. NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for python-distribute-native (python-distribute-native, python-setuptools-native) NOTE: consider defining a PREFERRED_PROVIDER entry to match python-distribute-native ERROR: Nothing RPROVIDES 'python-flask' (but /yocto/iot-devkit-yp-poky-edison-20160606/build_edison/../poky/meta-openembedded/meta-maker/recipes-webui/octoprint/octoprint_git.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'python-flask' is unbuildable, removing... Missing or unbuildable dependency chain was: ['python-flask'] ERROR: Required build target 'octoprint' has no buildable providers. Missing or unbuildable dependency chain was: ['octoprint', 'python-flask'] Summary: There was 1 WARNING message shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. +++ In the meta-maker and meta-openembedded trees dizzy branches, I see no python-flask recipe/package. It looks to me the patch for octoprint 1.2.10 has been merged into the meta-maker dizzy branch with the RDEPENDS list still matching that of the newest meta-openembedded (but I might be wrong). Is my analysis correct? If so, is there a way to know which RDEPEND I should use for octoprint in the dizzy branch to match the meta-openembedded one? Another possibility could be to use the meta-intel-edison from the yocto project git repo[2] with meta-openembedded & meta-maker on master but I have yet to try that. Thanks a lot for your help! Vincent [1] http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip [2] http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-edison/ To reproduce: get http://iotdk.intel.com/src/3.5/edison/iot-devkit-yp-poky-edison-20160606.zip and unzip cd iot-devkit-yp-poky-edison-20160606/poky/meta-openembedded git clone git://git.yoctoproject.org/meta-maker -b dizzy add meta-maker layer to iot-devkit-yp-poky-edison-20160606/build_edison/conf/bblayers.conf cd iot-devkit-yp-poky-edison-20160606/poky/ source oe-init-build-env ../build_edison/ bitbake octoprint -c fetchall -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
