meta-mender-core layer gives errors during bitbake?

783 views
Skip to first unread message

LoveMeow

unread,
Dec 14, 2017, 11:01:45 AM12/14/17
to Mender List mender.io


Hi,


I have a setup with poky on pyro branch and the following layers :



layer                 path                                      priority
==========================================================================
meta                  /home/rama/repositories/poky/meta         5
meta-poky             /home/rama/repositories/poky/meta-poky    5
meta-yocto-bsp        /home/rama/repositories/poky/meta-yocto-bsp  5
meta-toradex          /home/rama/repositories/poky/meta-toradex  90
meta-freescale        /home/rama/repositories/poky/meta-freescale  5
meta-freescale-3rdparty  /home/rama/repositories/poky/meta-freescale-3rdparty  4
oe-meta-go            /home/rama/repositories/poky/oe-meta-go   1


When I add the meta-mender-core I get the following errors:


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.19481
ERROR: Task (/home/rama/repositories/poky/meta/recipes-core/systemd/systemd_232.bb:do_patch) failed with exit code '1'

If I remove mender, the errors are gone. Mender is also on pyro btw.

My setup is poky on pyro branch on Ubuntu 14.04.




Drew Moseley

unread,
Dec 14, 2017, 2:22:52 PM12/14/17
to men...@lists.mender.io
It’s likely that patch is conflicting with some of the changes made in meta-mender-core.  The ordering of the patches will be determined by the layer priority.  You’ll likely need to modify the patch if you want it to apply on top of a Mender-enabled image.  As mentioned in the other thread, we are not using meta-toradex which is evidently supplying this patch file.  Are you sure you need that rather than meta-toradex-nxp and meta-toradex-bsp-common?  I don’t know what that layer is, so I cannot make a recommendation.

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

unread,
Dec 15, 2017, 4:21:02 AM12/15/17
to men...@lists.mender.io
Sure, I made a whole new setup from the toradex site, with the layers you mentioned such as below :

Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "arm-angstrom-linux-gnueabi"
MACHINE           = "colibri-t20"
DISTRO            = "angstrom"
DISTRO_VERSION    = "v2016.12"
TUNE_FEATURES     = "arm armv7a vfp thumb            callconvention-hard"
TARGET_FPU        = "hard"
meta-angstrom     = "HEAD:9625910bb4bb48b3f4d87a1e9ff3576d40bd656a"
meta-toradex-nxp  = "HEAD:c4f34b34bf34f44b974a7add623cafff17d880ad"
meta-freescale    = "HEAD:05681fdf8298bb441c15135eae424c7601b07e98"
meta-freescale-3rdparty = "HEAD:e55167c3c2770c07a475342f99cc2a3a23fbfa0c"
meta-toradex-tegra = "HEAD:8deaad62384fbe4f4079f62bb7fdfa70ef199236"
meta-jetson-tk1   = "HEAD:e8b87fe8da7c6fcffa37ab245f50082953cc1ee1"
meta-toradex-bsp-common = "HEAD:bb3fafea5a3094909c8d7fb3216c37210fcfc339"
meta-snappy       = "HEAD:f6df6a63756d9976bcccb5fefdbc64e5cc794c99"
meta-linaro-toolchain = "HEAD:5d2cb685217794293ea2bab18d7e62019c329d06"
meta-oe          
meta-efl         
meta-gpe         
meta-gnome       
meta-xfce        
meta-initramfs   
meta-systemd     
meta-networking  
meta-multimedia  
meta-python       = "HEAD:b40116cf457b88a2db14b86fda9627fb34d56ae6"
meta-lxde         = "HEAD:1bd36a4d0f7e1e9fdea9c4c991188bc1dc9da421"
meta-browser      = "HEAD:1569eeb9cc1b87632abbf35fbb05f4ac4eeb3987"
meta-qt4          = "HEAD:f389368dc86e745df14cab9eeb9a94bc02bd273e"
meta-qt5          = "HEAD:2c9f0e4eb0e9097f6f872ec1e1d81768a8ab5f1b"
meta-freescale-distro = "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390"
meta-toradex-demos = "HEAD:a08f1a3164e9ce16fca09f1f1c016b81eb1fcfaa"
meta              = "HEAD:93b7f83a4212409a55ddf568a34468d4f6ef2c06"
meta-virtualization = "morty:eb6b5129561eda9ea1f47e85ab9ed9e5a6b8f64c"
oe-meta-go        = "master:514b2a80a2a4235687e92fb28328bb3e7c2d6c74"
meta-mender-core  = "morty:ae53ebcabea1c243634bbd1dba7565088d8501af"


when I bitbake I get the following error:
ERROR: m4-native-1.4.17-r0 do_compile: oe_runmake failed
ERROR: m4-native-1.4.17-r0 do_compile: Function failed: do_compile (log file is located at /home/rama/repositories/oe-core/build/tmp-glibc/work/x86_64-linux/m4-native/1.4.17-r0/temp/log.do_compile.6300)
ERROR: Logfile of failure stored in: /home/rama/repositories/oe-core/build/tmp-glibc/work/x86_64-linux/m4-native/1.4.17-r0/temp/log.do_compile.6300
 and
ERROR: Task (/home/rama/repositories/oe-core/build/../layers/openembedded-core/meta/recipes-devtools/m4/m4-native_1.4.17.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 155 tasks of which 145 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
Waiting for 0 running tasks to finish:
Traceback (most recent call last):
  File ".git/hooks/pre-commit", line 36, in <module>
    sys.exit(hook_func())
  File ".git/hooks/pre-commit", line 12, in hook_func
    cmdline = '\x00'.join(psutil.Process(os.getppid()).cmdline)

Summary: 1 task failed:
  /home/rama/repositories/oe-core/build/../layers/openembedded-core/meta/recipes-devtools/m4/m4-native_1.4.17.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


What do I do now?

Meow


On Thu, Dec 14, 2017 at 8:22 PM, 'Drew Moseley' via Mender List mender.io <men...@lists.mender.io> wrote:
It’s likely that patch is conflicting with some of the changes made in meta-mender-core.  The ordering of the patches will be determined by the layer priority.  You’ll likely need to modify the patch if you want it to apply on top of a Mender-enabled image.  As mentioned in the other thread, we are not using meta-toradex which is evidently supplying this patch file.  Are you sure you need that rather than meta-toradex-nxp and meta-toradex-bsp-common?  I don’t know what that layer is, so I cannot make a recommendation.

Drew

Î

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

unread,
Dec 15, 2017, 7:49:50 AM12/15/17
to Mender List mender.io

Hi,

Additionally with my old setup, I get lots of errors. Again i have just cloned the pyro git today once again and I have the following here:

Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "ubuntu-14.04"
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    = "pyro:a75a2f4272226e924d8c9deb699a19ca9e606a5b"
meta-toradex-nxp  = "morty:c4f34b34bf34f44b974a7add623cafff17d880ad"
meta-toradex-bsp-common = "morty:bb3fafea5a3094909c8d7fb3216c37210fcfc339"
meta-freescale    = "pyro:06178400afbd641a6709473fd21d893dcd3cfbfa"
meta-freescale-3rdparty = "pyro:9613dbc02ca970122a01c935bc9e5789ced73a9d"
oe-meta-go        = "master:0712320950adf810fb324d49fba5d49ae19981b0"
meta-mender-core  = "pyro:302111e4a79e4844cad536fcc9475764eb254611"

I get this :


ERROR: m4-native-1.4.18-r0 do_compile: oe_runmake failed
ERROR: m4-native-1.4.18-r0 do_compile: Function failed: do_compile (log file is located at /home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/temp/log.do_compile.9159)
ERROR: Logfile of failure stored in: /home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/temp/log.do_compile.9159
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 8 infodir=/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/recipe-sysroot-native/usr/share/info
| make  all-recursive
| make[1]: Entering directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build'
| Making all in .
| make[2]: Entering directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build'
| make[2]: Nothing to be done for `all-am'.
| make[2]: Leaving directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build'
| Making all in examples
| make[2]: Entering directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build/examples'
| make[2]: Nothing to be done for `all'.
| make[2]: Leaving directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build/examples'
| Making all in lib
| make[2]: Entering directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build/lib'

and this:

| make[3]: *** [clean-temp.o] Error 1
| make[3]: *** Waiting for unfinished jobs....
| make[3]: Leaving directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build/lib'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build/lib'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build'
| make: *** [all] Error 2
| ERROR: Function failed: do_compile (log file is located at /home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/temp/log.do_compile.9159)
ERROR: Task (/home/rama/repositories/poky/meta/recipes-devtools/m4/m4-native_1.4.18.bb:do_compile) failed with exit code '1'

I seem to ge the same errrors on morty and pyro branches with 2 totally different environments? The one posted before is oe-core stup and this one is a pyro setup totally independant. I get this only when meta-mender-core is added.
Let me know if I am doing something wrong.

Drew Moseley

unread,
Dec 15, 2017, 11:55:52 AM12/15/17
to mender
What does  /home/rama/repositories/poky/build/tmp/work/x86_64-linux/m4-native/1.4.18-r0/temp/log.do_compile.9159 show?

Can you also post your belayers.conf and local.conf files?

Drew

Reply all
Reply to author
Forward
0 new messages