Nothing PROVIDES 'u-boot' machine qemux86?

[LoveMeow]

Since I am unable to work with my own setup of oe-core, I decided to follow the documentation on the mender site word to word.

I still run into difficulties.

First I tried to set the machine as apalis-imx6, it kept saying invalid machine?
Secondly, when I try to bitbake it says:

ERROR: Nothing PROVIDES 'u-boot'
ERROR: u-boot was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the qemux86 machine configuration.
ERROR: Required build target 'core-image-minimal' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 'u-boot']


I clone the u-boot-imx6 repo but I am not sure what to do after this?

[Drew Moseley]

Are you able to build the apalis-imx6 machine without the Mender layers enabled?  Do you have the meta-freescale-3rdpart and meta-toradex-nxp repositories in your setup?  Those are the layers that provide that machine.

Also, it seems that for the current master/rocko branches you need to specify the MACHINE as an environment variable rather than in the local.conf file.  I’m not sure why that it but that was a detail that one of the Toradex engineers mentioned to me and it seems to be a requirement of the Toradex layers.

Given that the error here is specifically referring to the qemux86 machine (which is the default) it seems there is an issue with the actual setting of the bitbake variable.

Drew

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.
To post to this group, send email to men...@lists.mender.io.
Visit this group at https://groups.google.com/a/lists.mender.io/group/mender/.

[Ramapriya Sridharan]

hi,

I did what you said, it now seems to start bitbaking(accepts the machine as valid), but it says the following:

ParseError at meta/classes/image.bbclass:185: Could not inherit file classes/image_types_uboot.bbclass

I added the following meta layers:

1. meta-fsl-arm

2. meta-fsl-arm-extra

3. meta-toradex

4. meta-angstrom

5. meta-qt5

Thanks

Meow

On Mon, Dec 11, 2017 at 8:17 PM, 'Drew Moseley' via Mender List mender.io <men...@lists.mender.io> wrote:

Are you able to build the apalis-imx6 machine without the Mender layers enabled?  Do you have the meta-freescale-3rdpart and meta-toradex-nxp repositories in your setup?  Those are the layers that provide that machine.

Also, it seems that for the current master/rocko branches you need to specify the MACHINE as an environment variable rather than in the local.conf file.  I’m not sure why that it but that was a detail that one of the Toradex engineers mentioned to me and it seems to be a requirement of the Toradex layers.

Given that the error here is specifically referring to the qemux86 machine (which is the default) it seems there is an issue with the actual setting of the bitbake variable.

Drew

On Dec 11, 2017, at 5:45 AM, LoveMeow <ramapriya.sridharan@rapyuta-robotics.com> wrote:

Since I am unable to work with my own setup of oe-core, I decided to follow the documentation on the mender site word to word.

I still run into difficulties.

First I tried to set the machine as apalis-imx6, it kept saying invalid machine?
Secondly, when I try to bitbake it says:

ERROR: Nothing PROVIDES 'u-boot'
ERROR: u-boot was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the qemux86 machine configuration.
ERROR: Required build target 'core-image-minimal' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 'u-boot']


I clone the u-boot-imx6 repo but I am not sure what to do after this?

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.

To post to this group, send email to men...@lists.mender.io.
Visit this group at https://groups.google.com/a/lists.mender.io/group/mender/.

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.

[LoveMeow]

Hi,

I am on the pyro branch, and I still have the same error. iS there any fix for this?

[Drew Moseley]

The image_types_uboot stuff has been removed in the pyro branch.  See https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d096d7e850f12d7440d285b4eaa6ed1c61558ef5

The only thing I can guess is that your poky sources are out of date.

Drew

To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.

[Ramapriya Sridharan]

Hi,

I replaced some of the meta-libraries with others, seems to be working better, I now get the following error:

NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal-4.8"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "apalis-imx6"
DISTRO            = "poky"
DISTRO_VERSION    = "2.3.2"
TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU        = "hard"
meta             
meta-poky        
meta-yocto-bsp   
meta-toradex      = "pyro:a75a2f4272226e924d8c9deb699a19ca9e606a5b"
meta-mender-core  = "pyro:302111e4a79e4844cad536fcc9475764eb254611"
meta-freescale    = "pyro:06178400afbd641a6709473fd21d893dcd3cfbfa"
meta-freescale-3rdparty = "pyro:9613dbc02ca970122a01c935bc9e5789ced73a9d"

Initialising tasks: 100% |##################################################################################################################| Time: 0:00:04
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: systemd-1_232-r0 do_patch: Command Error: 'quilt --quiltrc /home/rama/repositories/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/systemd/1_232-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0  Output:
Applying patch 0001-systemd-udevd.service.in-set-MountFlags-shared.patch
patching file units/systemd-udevd.service.in
Hunk #1 FAILED at 21.
1 out of 1 hunk FAILED -- rejects in file units/systemd-udevd.service.in
Patch 0001-systemd-udevd.service.in-set-MountFlags-shared.patch does not apply (enforce with -f)
ERROR: systemd-1_232-r0 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/rama/repositories/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/systemd/1_232-r0/temp/log.do_patch.1928
ERROR: Task (/home/rama/repositories/poky/meta/recipes-core/systemd/systemd_232.bb:do_patch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1156 tasks of which 1105 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/rama/repositories/poky/meta/recipes-core/systemd/systemd_232.bb:do_patch
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

What does this error mean? Google doesnt seem to have the answer.

Thanks!

Meow

On Tue, Dec 12, 2017 at 5:02 PM, 'Drew Moseley' via Mender List mender.io <men...@lists.mender.io> wrote:

The image_types_uboot stuff has been removed in the pyro branch.  See https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d096d7e850f12d7440d285b4eaa6ed1c61558ef5

The only thing I can guess is that your poky sources are out of date.

Drew

To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.
To post to this group, send email to men...@lists.mender.io.
Visit this group at https://groups.google.com/a/lists.mender.io/group/mender/.

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.
To post to this group, send email to men...@lists.mender.io.
Visit this group at https://groups.google.com/a/lists.mender.io/group/mender/.

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mender+unsubscribe@lists.mender.io.
To post to this group, send email to men...@lists.mender.io.
Visit this group at https://groups.google.com/a/lists.mender.io/group/mender/.

[Drew Moseley]

It means that a patch specified in the systemd recipes is not applying. Specifically the patch file 0001-systemd-udevd.service.in-set-MountFlags-shared.patch.  I don’t have that file in any of my source dirs.  You’ll need to find out which layer is providing it and why.  Grepping through all your sources for the file name should show you where it is being added.

Drew

[Ramapriya Sridharan]

Hi,

I found it in meta-toradex, should I remove it?

Meow

On Wed, Dec 13, 2017 at 5:21 PM, 'Drew Moseley' via Mender List mender.io <men...@lists.mender.io> wrote:

It means that a patch specified in the systemd recipes is not applying. Specifically the patch file 0001-systemd-udevd.service.in-set-MountFlags-shared.patch.  I don’t have that file in any of my source dirs.  You’ll need to find out which layer is providing it and why.  Grepping through all your sources for the file name should show you where it is being added.

Drew

[Drew Moseley]

We don’t use the meta-toradex layer, only meta-toradex-nxp, meta-toradex-bsp-common and meta-freescale-3rdparty.  I don’t know what the u-boot recipe updates in meta-toradex are trying to accomplish so I cannot say whether they should just be removed or updated.

Drew