[yocto] Cross compilation sysroot doesn't include libusb

2019-07-12 Thread Srinivasan, Usha
I will start with the caveat: this is my first time trying to cross compile for 
a target running a yocto bitbaked image. So I am surely not doing the right 
thing.

I have generated both a core-image-sato & core-image-sato-dev.  I am developing 
an application to run on my target machine.  My application uses libraries that 
in turn need libusb.so which doesn't exist in under the sysroot setup for cross 
compilation.  I have these in my local.conf and I do see

EXTRA_IMAGE_FEATURES ?= "debug-tweaks tools-testapps tools-sdk dev-pkgs"
CORE_IMAGE_EXTRA_INSTALL += "openssh glib-2.0 glibc glib-networking 
libusb-compat"

I do see that libusb-compat was generated:
./corei7-64-poky-linux/libusb-compat/1_0.1.5-r0/deploy-rpms/corei7_64/libusb-0.1-4-0.1.5-r0.corei7_64.rpm
./corei7-64-poky-linux/libusb-compat/1_0.1.5-r0/deploy-rpms/corei7_64/libusb-0.1-src-0.1.5-r0.corei7_64.rpm
./corei7-64-poky-linux/libusb-compat/1_0.1.5-r0/deploy-rpms/corei7_64/libusb-0.1-dev-0.1.5-r0.corei7_64.rpm
./corei7-64-poky-linux/libusb-compat/1_0.1.5-r0/deploy-rpms/corei7_64/libusb-0.1-dbg-0.1.5-r0.corei7_64.rpm

I tried bitbake meta-ide-support and used 
tmp/environment-setup-corei7-64-poky-linux to setup my build environment, but 
there is no libusb.so in the sysroot lib directory.

I tried bitbake meta-toolchain and installed the tool chain and used its  
/opt/poky/2.7/environment-setup-corei7-64-poky-linux, but again the 
opt/poky/2.7 sysroot directory  also does not include libusb.so.

What step am I missing?

Thanks in advance,
Usha


Intel Corporation
1110 American Parkway NE
Suite F-100, AMP1 10C-166b
Allentown, PA 18109-9151
484-245-9498

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Re: wic utility

2019-02-21 Thread Srinivasan, Raja
Sorry for the delay.

 

Yes. Simple things worked fine. I wanted to copy  a dir to a partition inside 
the sdcard image and that was not successful.

 

I ended up writing a utility to perform the function I needed. It is somewhat 
customized to our image but if anyone needs, I will be happy to share my 
findings. srini

 

From: Kevin Hao  
Sent: Thursday, January 24, 2019 1:46 AM
To: Srinivasan, Raja 
Cc: yocto@yoctoproject.org
Subject:  Re: [yocto] wic utility

 

On Wed, Jan 23, 2019 at 04:39:07PM +, Srinivasan, Raja wrote: 
> I am using wic 0.2.0 from the rocko build. 
> 
>  
> 
> wic cp file wifile:part/path 
> 
>  
> 
> appears to succeed (no errors reported). 
> 
>  
> 
> But when I perform wic ls I don’t find the file in the target. 
> 
>  
> 
> Are there any switches the I should be using? 

It seems that it works fine on the master branch. 
$ wic ls 
tmp/deploy/images/beaglebone-yocto/core-image-sato-beaglebone-yocto.wic:2 
debugfs 1.43.5 (04-Aug-2017) 
  2   40755 (2)  0  04096 23-Jan-2019 14:04 . 
  2   40755 (2)  0  04096 23-Jan-2019 14:04 .. 
 11   40700 (2)  0  0   16384 23-Jan-2019 14:04 lost+found 
 12   40755 (2)  0  04096 23-Jan-2019 13:56 lib 
456   40755 (2)  0  04096 23-Jan-2019 13:43 dev 
457   40555 (2)  0  04096 23-Jan-2019 13:43 proc 
458   40755 (2)  0  04096 23-Jan-2019 13:43 media 
459   40755 (2)  0  04096 23-Jan-2019 14:04 boot 
465   40755 (2)  0  04096 23-Jan-2019 14:03 mnt 
467   40755 (2)  0  04096 23-Jan-2019 13:57 usr 
   9582   40755 (2)  0  04096 23-Jan-2019 13:56 var 
   9639   40555 (2)  0  04096 23-Jan-2019 13:43 sys 
   9640   40755 (2)  0  04096 23-Jan-2019 14:04 etc 
  10373   40755 (2)  0  04096 23-Jan-2019 14:03 sbin 
  10437   40755 (2)  0  04096 23-Jan-2019 13:43 run 
  10438   41777 (2)  0  04096 23-Jan-2019 13:43 tmp 
  10439   40755 (2)  0  04096 23-Jan-2019 14:03 home 
  10441   40755 (2)  0  04096 23-Jan-2019 14:03 bin 
$ wic cp a.txt 
tmp/deploy/images/beaglebone-yocto/core-image-sato-beaglebone-yocto.wic:2 
$ wic ls 
tmp/deploy/images/beaglebone-yocto/core-image-sato-beaglebone-yocto.wic:2 
debugfs 1.43.5 (04-Aug-2017) 
  2   40755 (2)  0  04096 23-Jan-2019 14:04 . 
  2   40755 (2)  0  04096 23-Jan-2019 14:04 .. 
 11   40700 (2)  0  0   16384 23-Jan-2019 14:04 lost+found 
 12   40755 (2)  0  04096 23-Jan-2019 13:56 lib 
456   40755 (2)  0  04096 23-Jan-2019 13:43 dev 
457   40555 (2)  0  04096 23-Jan-2019 13:43 proc 
458   40755 (2)  0  04096 23-Jan-2019 13:43 media 
459   40755 (2)  0  04096 23-Jan-2019 14:04 boot 
465   40755 (2)  0  04096 23-Jan-2019 14:03 mnt 
467   40755 (2)  0  04096 23-Jan-2019 13:57 usr 
   9582   40755 (2)  0  04096 23-Jan-2019 13:56 var 
   9639   40555 (2)  0  04096 23-Jan-2019 13:43 sys 
   9640   40755 (2)  0  04096 23-Jan-2019 14:04 etc 
  10373   40755 (2)  0  04096 23-Jan-2019 14:03 sbin 
  10437   40755 (2)  0  04096 23-Jan-2019 13:43 run 
  10438   41777 (2)  0  04096 23-Jan-2019 13:43 tmp 
  10439   40755 (2)  0  04096 23-Jan-2019 14:03 home 
  10441   40755 (2)  0  04096 23-Jan-2019 14:03 bin 
  10514  100644 (1)  0  0   4 24-Jan-2019 14:23 a.txt 

There should be no change for the Disk.copy() function between rocko and master 
branch. Anyway could you have a try on the latest master branch? 

Thanks, 
Kevin 

> 
>  
> 
> Thanks for any pointers, srini 
> 
> 
> ━━━
>  
> 
> CONFIDENTIALITY NOTICE: This email message and any attachments are 
> confidential 
> and may be privileged and are meant to be read by the intended recipient 
> only. 
> If you are not the intended recipient, please notify sender immediately and 
> destroy all copies of this message and any attachments without reading or 
> disclosing their contents. Thank you 
> 
> 
> 

> -- 
> ___ 
> yocto mailing list 
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>  
> https://lists.yoctoproject.org/listinfo/yocto 

 


pgpUmC5h4GCPl.pgp
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Error in populating sdk using custom distro

2019-01-25 Thread srinivasan
Dear Yocto Experts,

I am seeing the below error, while building the sdk for my custom
distro, with some the freescale layers (meta-freescale,
meta-freescale-3rdparty.meta-freescale-distro, meta-fsl-bsp-release)
integrated into my custom distro, could anyone please help me with the
pointers that why am i seeing the below issue?

bitbake -c populate_sdk custom-debug-distro


Logs:
=

ERROR: qtwayland-5.11.3+gitAUTOINC+dccec9b282-r0 do_patch: Command
Error: 'quilt --quiltrc
/home/user/custombuild_test12/customos/build/tmp/work/aarch64-mx8mm-poky-linux/qtwayland/5.11.3+gitAUTOINC+dccec9b282-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0  Output:
Applying patch 0001-tst_client.cpp-Fix-no-opengl-build.patch
patching file tests/auto/client/client/tst_client.cpp
Hunk #1 succeeded at 107 (offset -7 lines).
Hunk #2 succeeded at 131 with fuzz 2 (offset -2 lines).
Hunk #3 FAILED at 172.
Hunk #4 succeeded at 560 (offset 125 lines).
Hunk #5 succeeded at 586 with fuzz 2 (offset 136 lines).
1 out of 5 hunks FAILED -- rejects in file
tests/auto/client/client/tst_client.cpp
Patch 0001-tst_client.cpp-Fix-no-opengl-build.patch does not apply
(enforce with -f)
ERROR: qtwayland-5.11.3+gitAUTOINC+dccec9b282-r0 do_patch: Function
failed: patch_do_patch
ERROR: Logfile of failure stored in:
/home/user/custombuild_test12/customos/build/tmp/work/aarch64-mx8mm-poky-linux/qtwayland/5.11.3+gitAUTOINC+dccec9b282-r0/temp/log.do_patch.82399
ERROR: Task 
(/home/user/custombuild_test12/customos/sources/meta-qt5/recipes-qt/qt5/qtwayland_git.bb:do_patch)
failed with exit code '1'
ERROR: qtwayland-native-5.11.3+gitAUTOINC+dccec9b282-r0 do_patch:
Command Error: 'quilt --quiltrc
/home/user/custombuild_test12/customos/build/tmp/work/x86_64-linux/qtwayland-native/5.11.3+gitAUTOINC+dccec9b282-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0  Output:
Applying patch 0001-tst_client.cpp-Fix-no-opengl-build.patch
patching file tests/auto/client/client/tst_client.cpp
Hunk #1 succeeded at 107 (offset -7 lines).
Hunk #2 succeeded at 131 with fuzz 2 (offset -2 lines).
Hunk #3 FAILED at 172.
Hunk #4 succeeded at 560 (offset 125 lines).
Hunk #5 succeeded at 586 with fuzz 2 (offset 136 lines).
1 out of 5 hunks FAILED -- rejects in file
tests/auto/client/client/tst_client.cpp
Patch 0001-tst_client.cpp-Fix-no-opengl-build.patch does not apply
(enforce with -f)
ERROR: qtwayland-native-5.11.3+gitAUTOINC+dccec9b282-r0 do_patch:
Function failed: patch_do_patch
ERROR: Logfile of failure stored in:
/home/user/custombuild_test12/customos/build/tmp/work/x86_64-linux/qtwayland-native/5.11.3+gitAUTOINC+dccec9b282-r0/temp/log.do_patch.82410
ERROR: Task 
(virtual:native:/home/user/custombuild_test12/customos/sources/meta-qt5/recipes-qt/qt5/qtwayland_git.bb:do_patch)
failed with exit code '1'

Thanks in advance
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] wic utility

2019-01-23 Thread Srinivasan, Raja
I am using wic 0.2.0 from the rocko build.

wic cp file wifile:part/path

appears to succeed (no errors reported).

But when I perform wic ls I don't find the file in the target.

Are there any switches the I should be using?

Thanks for any pointers, srini



CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Build error after changing PACKAGE_CLASSES to package_deb

2019-01-21 Thread srinivasan
Dear Yocto Experts Team,

I am seeing the below error after changing the package_classes from "rpm"
to "deb" as below, when I am trying to add freescale meta layers to my
custom yocto distribution

Could you please do the needful by providing some inputs in resolving the
below issue?

Logs:
WARNING: Host distribution "ubuntu-18.04" 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: 0:00:15
Parsing of 2304 .bb files complete (0 cached, 2304 parsed). 3210 targets,
385 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "ubuntu-18.04"
TARGET_SYS   = "aarch64-poky-linux"
MACHINE  = "imx8mmevk"
DISTRO   = "NativeOS-TRK"
DISTRO_VERSION   = "1.0.8"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta-traktor-imx8= "master:525bab5e576c2f0f1242cd1e6b546859c856441a"
meta-traktor = "sumo:b91788da6bd52485faa85bb19bc7a9a1ddf2ee5d"
meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
meta-nativeos= "sumo:8a14b16e4049051e29009e67afa63bfac5ddb26e"
meta-freescale   = "master:525bab5e576c2f0f1242cd1e6b546859c856441a"
meta
meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-bsp
meta-sdk = "master:525bab5e576c2f0f1242cd1e6b546859c856441a"

Initialising tasks: 100%
|##|
Time: 0:00:05
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: linux-imx-4.14.62-r0 do_package_write_deb: Error executing a python
function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:do_package_deb(d)
 0003:
File:
'/home/srinishanmugam/nibuild_test/nativeos/sources/poky/meta/classes/package_deb.bbclass',
lineno: 102, function: do_package_deb
 0098:
 0099:os.chdir(oldcwd)
 0100:
 0101:if error:
 *** 0102:raise error
 0103:}
 0104:do_package_deb[vardeps] += "deb_write_pkg"
 0105:do_package_deb[vardepsexclude] = "BB_NUMBER_THREADS"
 0106:
Exception: subprocess.CalledProcessError: Command
'PATH="/home/srinishanmugam/nibuild_test/nativeos/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/srinishanmugam/nibuild_test/nativeos/sources/poky/scripts:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/bin/aarch64-poky-linux:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot/usr/bin/crossscripts:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/sbin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/usr/bin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/sbin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/recipe-sysroot-native/bin:/home/srinishanmugam/nibuild_test/nativeos/sources/poky/bitbake/bin:/home/srinishanmugam/nibuild_test/nativeos/build/tmp/hosttools"
dpkg-deb -b
/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/packages-split/kernel-module-snd-usbmidi-lib-4.14.62-imx_4.14.62_1.0.0_beta+g1907fe4c3287
/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/deploy-debs/imx8mmevk'
returned non-zero exit status 2.

Subprocess output:
dpkg-deb: error: package name has characters that aren't lowercase
alphanums or '-+.'

ERROR: linux-imx-4.14.62-r0 do_package_write_deb: Function failed:
do_package_deb
ERROR: Logfile of failure stored in:
/home/srinishanmugam/nibuild_test/nativeos/build/tmp/work/imx8mmevk-poky-linux/linux-imx/4.14.62-r0/temp/log.do_package_write_deb.31568
ERROR: Task
(/home/srinishanmugam/nibuild_test/nativeos/sources/meta-fsl-bsp-release/imx/meta-bsp/recipes-kernel/linux/linux-imx_4.14.62.bb:do_package_write_deb)
failed with exit code '1'
NOTE: Tasks Summary: 

Re: [yocto] [meta-freescale] ERROR: Nothing PROVIDES 'virtual/libgles2'

2019-01-21 Thread srinivasan
imx8mmevk

On Fri, Jan 18, 2019 at 12:20 PM Daiane Angolini  wrote:
>
> On Fri, Jan 18, 2019 at 6:46 AM srinivasan  wrote:
> >
> > Dear Yocto Experts,
> >
> > I am seeing the below error when i am trying to integrate freescale
> > layers into my custom os?
>
> Which imx8 MACHINE are you trying?
>
> Daiane
> >
> > srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
> > bitbake -f -c clean custom-image-debug-imx8
> > WARNING: Host distribution "ubuntu-18.04" 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.
> > WARNING: 
> > /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb:
> > Unable to get checksum for libdrm SRC_URI entry drm-update-arm.patch:
> > file could not be found
> >   | ETA:  0:00:05
> > Parsing recipes: 100%
> > |#|
> > Time: 0:00:09
> > Parsing of 2275 .bb files complete (0 cached, 2275 parsed). 3177
> > targets, 382 skipped, 1 masked, 0 errors.
> > NOTE: Resolving any missing task queue dependencies
> > ERROR: Nothing PROVIDES 'virtual/libgles2' (but
> > /home/srinishanmugam/customBuild_test_rpi/customos/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb,
> > /home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/cairo/cairo_1.14.12.bb
> > DEPENDS on or otherwise requires it)
> > imx-gpu-viv PROVIDES virtual/libgles2 but was skipped: incompatible
> > with machine imx8mmevk (not in COMPATIBLE_MACHINE)
> > NOTE: Runtime target 'qtbase' is unbuildable, removing...
> > Missing or unbuildable dependency chain was: ['qtbase', 'virtual/libgles2']
> > ERROR: Required build target 'custom-image-debug-imx8' has no
> > buildable providers.
> > Missing or unbuildable dependency chain was:
> > ['custom-image-debug-imx8', 'qtbase', 'virtual/libgles2']
> >
> > Summary: There were 2 WARNING messages shown.
> > Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> >
> >
> > Could you anyone please provide me some inputs for resolving the above 
> > issue?
> >
> > Many Thanks in advance
> > --
> > ___
> > meta-freescale mailing list
> > meta-freesc...@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-freescale
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] ERROR: Nothing PROVIDES 'virtual/libgles2'

2019-01-21 Thread srinivasan
Dear Yocto Experts,

I am seeing the below error when i am trying to integrate freescale
layers into my custom os?

srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
bitbake -f -c clean custom-image-debug-imx8
WARNING: Host distribution "ubuntu-18.04" 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.
WARNING: 
/home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb:
Unable to get checksum for libdrm SRC_URI entry drm-update-arm.patch:
file could not be found
  | ETA:  0:00:05
Parsing recipes: 100%
|#|
Time: 0:00:09
Parsing of 2275 .bb files complete (0 cached, 2275 parsed). 3177
targets, 382 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'virtual/libgles2' (but
/home/srinishanmugam/customBuild_test_rpi/customos/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb,
/home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/cairo/cairo_1.14.12.bb
DEPENDS on or otherwise requires it)
imx-gpu-viv PROVIDES virtual/libgles2 but was skipped: incompatible
with machine imx8mmevk (not in COMPATIBLE_MACHINE)
NOTE: Runtime target 'qtbase' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['qtbase', 'virtual/libgles2']
ERROR: Required build target 'custom-image-debug-imx8' has no
buildable providers.
Missing or unbuildable dependency chain was:
['custom-image-debug-imx8', 'qtbase', 'virtual/libgles2']

Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


Could you anyone please provide me some inputs for resolving the above issue?

Many Thanks in advance
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-intel] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64

2019-01-21 Thread srinivasan
Thanks a ton Ross, your inputs really worked :)

On Tue, Jan 15, 2019 at 11:34 AM Burton, Ross  wrote:
>
> You'll have to not install either connman or network manager.
>
> Ross
>
> On Tue, 15 Jan 2019 at 05:18, srinivasan  wrote:
> >
> > Dear Yocto experts,
> >
> > I am seeing the below error when I am trying to integrate the
> > "fsl-image-validation-imx.bb" into my custom yocto build and trigger
> > the build using "bitbake custom-image-debug-imx8.bb", I somewhat feel
> > networkmanager is conflicting with conman, could you please let me
> > know how this issue can be resolved?
> >
> > I have attached the recipe files for your information
> >
> > Error:
> >
> > ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Could not invoke dnf.
> > Command 
> > '/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/recipe-sysroot-native/usr/bin/dnf
> > -y -c 
> > /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/dnf/dnf.conf
> > --setopt=reposdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/yum.repos.d
> > --repofrompath=oe-repo,/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
> > --installroot=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs
> > --setopt=logdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp
> > --nogpgcheck install alsa-server alsa-tools alsa-utils apt apt-repo
> > bash basicquick bc binutils binutils-symlinks bmap-tools-git
> > build-config bzip2 cmake coreutils crashme crda dfu-util diffutils dnf
> > dnsmasq ethtool file libfreetype6 gdb gdbserver gettext git
> > glibc-gconv-utf-32 gnupg libharfbuzz0 hidapi hostapd htop iperf3 iw
> > kernel-dev kernel-devsrc kernel-modules ldd libasound liberation-fonts
> > libfftw libfftwf libjack libjpeg62 libpng16-16 libtool libxerces-c
> > libsensors4 lmsensors-sensors lsof lttng-modules make memtester
> > merge-files nano networkmanager ni-isolcpus ninja openssl
> > packagegroup-base-extended packagegroup-core-boot
> > packagegroup-core-full-cmdline packagegroup-core-sdk
> > packagegroup-core-ssh-dropbear packagegroup-core-standalone-sdk-target
> > packagegroup-core-tools-debug packagegroup-core-tools-profile
> > packagegroup-core-tools-testapps packagegroup-fsl-optee-imx
> > packagegroup-fsl-tools-audio packagegroup-fsl-tools-gpu-external
> > packagegroup-tools-bluetooth pbzip2 pciutils perf pkgconfig procps
> > psplash python python-dbus python-modules python-pandas python-pip
> > python3 python3-dbus python3-misc python3-modules python3-pip
> > python3-psutil python3-robotframework python3-six qt3d qt3d-dev
> > qt3d-mkspecs qtbase qtbase-dev qtbase-mkspecs qtbase-plugins
> > qtbase-tools libqt5charts5 libqt5charts-dev libqt5charts-mkspecs
> > qtconnectivity-dev qtconnectivity-mkspecs qtdeclarative
> > qtdeclarative-dev qtdeclarative-mkspecs qtgraphicaleffects
> > qtgraphicaleffects-dev qtquickcontrols qtquickcontrols-dev
> > qtquickcontrols-qmlplugins qtquickcontrols2 qtquickcontrols2-dev
> > qtquickcontrols2-mkspecs libqt5svg5 libqt5svg-dev libqt5svg-mkspecs
> > rpm rt-tests rtirq run-postinsts screen ssh-keys-server strace stress
> > sysstat tar tmux trace-cmd ttf-bitstream-vera udev udev-automount
> > unzip usbreset usbutils util-linux valgrind wget wireless-tools
> > wpa-supplicant zip libz1 locale-base-en-us' returned 1:
> > Added oe-repo repo from
> > /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
> > Last metadata expiration check: 0:00:00 ago on Mon 14 Jan 2019 04:06:18 PM 
> > UTC.
> > Error:
> >  Problem: package connman-tools-1.35-r0.aarch64 requires connman, but
> > none of the providers can be installed
> >   - package packagegroup-core-tools-testapps-1.0-r2.imx8mmevk requires
> > connman-tools, but none of the providers can be installed
> >   - package networkmanager-1.10.6-r0.aarch64 conflicts with connman
> > provided by connman-1.35-r0.aarch64
> >   - conflicting requests
> > (try to add '--allowerasing' to command line to replace conflicting
> > packages or '--skip-broken' to skip uninstallable packages)
> >
> > ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Function failed: do_rootfs
> > ERROR: Logf

[yocto] Error: base-files/3.0.14-r89/temp/run.do_install.80432: Syntax error: Unterminated quoted string

2019-01-21 Thread srinivasan
Dear Yocto Experts,

I am trying to customize my vendor specific Yocto BSP's to my custom
OS.  I am facing the below error, could you please do the needful or
provide me some pointers from your end for solving this issue

Error:
$ bitbake fsl-image-validation-imx
WARNING: Host distribution "ubuntu-18.04" 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%
|###|
Time: 0:00:00
Loaded 3196 entries from dependency cache.
Parsing recipes: 100%
|#|
Time: 0:00:02
Parsing of 2298 .bb files complete (2284 cached, 14 parsed). 3202
targets, 398 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "aarch64-poky-linux"
MACHINE  = "imx8mmevk"
DISTRO   = "custom-TRK"
DISTRO_VERSION   = "${custom_DISTRO_VERSION}"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta-traktor-imx8= "sumo:4b25c1ee6896b5447f8502f13c28570341505360"
meta-traktor = "sumo:818be7ec4f768ba485e437dc26beb7bdc4b8120a"
meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
meta-custom= "sumo:d98452914e201d46a6b1360ca957d9b3e396b31f"
meta-freescale   = "HEAD:1deea6b4a2f83521ff247ea4743d09cc705ecd8e"
meta
meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-bsp
meta-sdk = "HEAD:1de93d3d5128b8422c23a87cb8b54149e2bfb942"

Initialising tasks: 100%
|##|
Time: 0:00:02
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: base-files-3.0.14-r89 do_install: Function failed: do_install
(log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Logfile of failure stored in:
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot',
'virtual:native:/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native', 'pseudo-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
176: 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
Syntax error: Unterminated quoted string
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_install (log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Task 
(/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1256 tasks of which 1204 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:
  
/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8$


Kindly do the needful,
Many Thanks in advance
-- 
___
yocto mailing list
yocto@yoctoproject.org

[yocto] ipv6

2019-01-18 Thread Srinivasan, Raja
All

I am using "rocko"

How can we turn off ipv6 altogether? We are not doing anything to startup ipv6. 
Still I see several lines in the logs which look like:

kernel: IPv6: wlan0: IPv6 duplicate address . detected
kernel[288]: IPv6: wlan0: IPv6 duplicate address ... detected

thanks, srini



CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[linux-yocto] ERROR: Nothing PROVIDES 'virtual/libgles2'

2019-01-18 Thread srinivasan
Dear Yocto Experts,

I am seeing the below error when i am trying to integrate freescale
layers into my custom os?

srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/customos/build_customosdistro_imx8$
bitbake -f -c clean custom-image-debug-imx8
WARNING: Host distribution "ubuntu-18.04" 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.
WARNING: 
/home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/drm/libdrm_2.4.91.bb:
Unable to get checksum for libdrm SRC_URI entry drm-update-arm.patch:
file could not be found
  | ETA:  0:00:05
Parsing recipes: 100%
|#|
Time: 0:00:09
Parsing of 2275 .bb files complete (0 cached, 2275 parsed). 3177
targets, 382 skipped, 1 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'virtual/libgles2' (but
/home/srinishanmugam/customBuild_test_rpi/customos/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb,
/home/srinishanmugam/customBuild_test_rpi/customos/sources/poky/meta/recipes-graphics/cairo/cairo_1.14.12.bb
DEPENDS on or otherwise requires it)
imx-gpu-viv PROVIDES virtual/libgles2 but was skipped: incompatible
with machine imx8mmevk (not in COMPATIBLE_MACHINE)
NOTE: Runtime target 'qtbase' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['qtbase', 'virtual/libgles2']
ERROR: Required build target 'custom-image-debug-imx8' has no
buildable providers.
Missing or unbuildable dependency chain was:
['custom-image-debug-imx8', 'qtbase', 'virtual/libgles2']

Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


Could you anyone please provide me some inputs for resolving the above issue?

Many Thanks in advance
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto


[linux-yocto] Error: base-files/3.0.14-r89/temp/run.do_install.80432: Syntax error: Unterminated quoted string

2019-01-16 Thread srinivasan
Dear Yocto Experts,

I am trying to customize my vendor specific Yocto BSP's to my custom
OS.  I am facing the below error, could you please do the needful or
provide me some pointers from your end for solving this issue

Error:
$ bitbake fsl-image-validation-imx
WARNING: Host distribution "ubuntu-18.04" 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%
|###|
Time: 0:00:00
Loaded 3196 entries from dependency cache.
Parsing recipes: 100%
|#|
Time: 0:00:02
Parsing of 2298 .bb files complete (2284 cached, 14 parsed). 3202
targets, 398 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "aarch64-poky-linux"
MACHINE  = "imx8mmevk"
DISTRO   = "custom-TRK"
DISTRO_VERSION   = "${custom_DISTRO_VERSION}"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta-traktor-imx8= "sumo:4b25c1ee6896b5447f8502f13c28570341505360"
meta-traktor = "sumo:818be7ec4f768ba485e437dc26beb7bdc4b8120a"
meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
meta-custom= "sumo:d98452914e201d46a6b1360ca957d9b3e396b31f"
meta-freescale   = "HEAD:1deea6b4a2f83521ff247ea4743d09cc705ecd8e"
meta
meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-bsp
meta-sdk = "HEAD:1de93d3d5128b8422c23a87cb8b54149e2bfb942"

Initialising tasks: 100%
|##|
Time: 0:00:02
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: base-files-3.0.14-r89 do_install: Function failed: do_install
(log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Logfile of failure stored in:
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot',
'virtual:native:/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native', 'pseudo-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
176: 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
Syntax error: Unterminated quoted string
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_install (log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Task 
(/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1256 tasks of which 1204 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:
  
/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8$


Kindly do the needful,
Many Thanks in advance
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org

[Yocto-bsp] Error: base-files/3.0.14-r89/temp/run.do_install.80432: Syntax error: Unterminated quoted string

2019-01-16 Thread srinivasan
Dear Yocto Experts,

I am trying to customize my vendor specific Yocto BSP's to my custom
OS.  I am facing the below error, could you please do the needful or
provide me some pointers from your end for solving this issue

Error:
$ bitbake fsl-image-validation-imx
WARNING: Host distribution "ubuntu-18.04" 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%
|###|
Time: 0:00:00
Loaded 3196 entries from dependency cache.
Parsing recipes: 100%
|#|
Time: 0:00:02
Parsing of 2298 .bb files complete (2284 cached, 14 parsed). 3202
targets, 398 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "aarch64-poky-linux"
MACHINE  = "imx8mmevk"
DISTRO   = "custom-TRK"
DISTRO_VERSION   = "${custom_DISTRO_VERSION}"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta-traktor-imx8= "sumo:4b25c1ee6896b5447f8502f13c28570341505360"
meta-traktor = "sumo:818be7ec4f768ba485e437dc26beb7bdc4b8120a"
meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
meta-custom= "sumo:d98452914e201d46a6b1360ca957d9b3e396b31f"
meta-freescale   = "HEAD:1deea6b4a2f83521ff247ea4743d09cc705ecd8e"
meta
meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-bsp
meta-sdk = "HEAD:1de93d3d5128b8422c23a87cb8b54149e2bfb942"

Initialising tasks: 100%
|##|
Time: 0:00:02
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: base-files-3.0.14-r89 do_install: Function failed: do_install
(log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Logfile of failure stored in:
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot',
'virtual:native:/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native', 'pseudo-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
176: 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
Syntax error: Unterminated quoted string
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_install (log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Task 
(/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1256 tasks of which 1204 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:
  
/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8$


Kindly do the needful,
Many Thanks in advance
-- 
___
yocto-bsp mailing list
yocto-bsp@yoctoproject.org

[yocto] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64

2019-01-15 Thread srinivasan
Dear Yocto experts,

I am seeing the below error when I am trying to integrate the
"fsl-image-validation-imx.bb" into my custom yocto build and trigger
the build using "bitbake custom-image-debug-imx8.bb", I somewhat feel
networkmanager is conflicting with conman, could you please let me
know how this issue can be resolved?

I have attached the recipe files for your information

Error:

ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Could not invoke dnf.
Command 
'/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/recipe-sysroot-native/usr/bin/dnf
-y -c 
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/dnf/dnf.conf
--setopt=reposdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/yum.repos.d
--repofrompath=oe-repo,/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
--installroot=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs
--setopt=logdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp
--nogpgcheck install alsa-server alsa-tools alsa-utils apt apt-repo
bash basicquick bc binutils binutils-symlinks bmap-tools-git
build-config bzip2 cmake coreutils crashme crda dfu-util diffutils dnf
dnsmasq ethtool file libfreetype6 gdb gdbserver gettext git
glibc-gconv-utf-32 gnupg libharfbuzz0 hidapi hostapd htop iperf3 iw
kernel-dev kernel-devsrc kernel-modules ldd libasound liberation-fonts
libfftw libfftwf libjack libjpeg62 libpng16-16 libtool libxerces-c
libsensors4 lmsensors-sensors lsof lttng-modules make memtester
merge-files nano networkmanager ni-isolcpus ninja openssl
packagegroup-base-extended packagegroup-core-boot
packagegroup-core-full-cmdline packagegroup-core-sdk
packagegroup-core-ssh-dropbear packagegroup-core-standalone-sdk-target
packagegroup-core-tools-debug packagegroup-core-tools-profile
packagegroup-core-tools-testapps packagegroup-fsl-optee-imx
packagegroup-fsl-tools-audio packagegroup-fsl-tools-gpu-external
packagegroup-tools-bluetooth pbzip2 pciutils perf pkgconfig procps
psplash python python-dbus python-modules python-pandas python-pip
python3 python3-dbus python3-misc python3-modules python3-pip
python3-psutil python3-robotframework python3-six qt3d qt3d-dev
qt3d-mkspecs qtbase qtbase-dev qtbase-mkspecs qtbase-plugins
qtbase-tools libqt5charts5 libqt5charts-dev libqt5charts-mkspecs
qtconnectivity-dev qtconnectivity-mkspecs qtdeclarative
qtdeclarative-dev qtdeclarative-mkspecs qtgraphicaleffects
qtgraphicaleffects-dev qtquickcontrols qtquickcontrols-dev
qtquickcontrols-qmlplugins qtquickcontrols2 qtquickcontrols2-dev
qtquickcontrols2-mkspecs libqt5svg5 libqt5svg-dev libqt5svg-mkspecs
rpm rt-tests rtirq run-postinsts screen ssh-keys-server strace stress
sysstat tar tmux trace-cmd ttf-bitstream-vera udev udev-automount
unzip usbreset usbutils util-linux valgrind wget wireless-tools
wpa-supplicant zip libz1 locale-base-en-us' returned 1:
Added oe-repo repo from
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Mon 14 Jan 2019 04:06:18 PM UTC.
Error:
 Problem: package connman-tools-1.35-r0.aarch64 requires connman, but
none of the providers can be installed
  - package packagegroup-core-tools-testapps-1.0-r2.imx8mmevk requires
connman-tools, but none of the providers can be installed
  - package networkmanager-1.10.6-r0.aarch64 conflicts with connman
provided by connman-1.35-r0.aarch64
  - conflicting requests
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages)

ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp/log.do_rootfs.56617
ERROR: Task 
(/home/user/test/os/sources/meta-custom-imx8/recipes-core/images/custom-image-debug-imx8.bb:do_rootfs)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 8016 tasks of which 7974 didn't need to
be rerun and 1 failed.

Many Thanks in advance,


fsl-image-validation-imx.bb
Description: Binary data


custom-image-debug-imx8.bb
Description: Binary data


custom-image-debug.bbclass
Description: Binary data
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[Yocto-bsp] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64

2019-01-14 Thread srinivasan
Dear Yocto experts,

I am seeing the below error when I am trying to integrate the
"fsl-image-validation-imx.bb" into my custom yocto build and trigger
the build using "bitbake custom-image-debug-imx8.bb", I somewhat feel
networkmanager is conflicting with conman, could you please let me
know how this issue can be resolved?

I have attached the recipe files for your information

Error:

ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Could not invoke dnf.
Command 
'/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/recipe-sysroot-native/usr/bin/dnf
-y -c 
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/dnf/dnf.conf
--setopt=reposdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/yum.repos.d
--repofrompath=oe-repo,/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
--installroot=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs
--setopt=logdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp
--nogpgcheck install alsa-server alsa-tools alsa-utils apt apt-repo
bash basicquick bc binutils binutils-symlinks bmap-tools-git
build-config bzip2 cmake coreutils crashme crda dfu-util diffutils dnf
dnsmasq ethtool file libfreetype6 gdb gdbserver gettext git
glibc-gconv-utf-32 gnupg libharfbuzz0 hidapi hostapd htop iperf3 iw
kernel-dev kernel-devsrc kernel-modules ldd libasound liberation-fonts
libfftw libfftwf libjack libjpeg62 libpng16-16 libtool libxerces-c
libsensors4 lmsensors-sensors lsof lttng-modules make memtester
merge-files nano networkmanager ni-isolcpus ninja openssl
packagegroup-base-extended packagegroup-core-boot
packagegroup-core-full-cmdline packagegroup-core-sdk
packagegroup-core-ssh-dropbear packagegroup-core-standalone-sdk-target
packagegroup-core-tools-debug packagegroup-core-tools-profile
packagegroup-core-tools-testapps packagegroup-fsl-optee-imx
packagegroup-fsl-tools-audio packagegroup-fsl-tools-gpu-external
packagegroup-tools-bluetooth pbzip2 pciutils perf pkgconfig procps
psplash python python-dbus python-modules python-pandas python-pip
python3 python3-dbus python3-misc python3-modules python3-pip
python3-psutil python3-robotframework python3-six qt3d qt3d-dev
qt3d-mkspecs qtbase qtbase-dev qtbase-mkspecs qtbase-plugins
qtbase-tools libqt5charts5 libqt5charts-dev libqt5charts-mkspecs
qtconnectivity-dev qtconnectivity-mkspecs qtdeclarative
qtdeclarative-dev qtdeclarative-mkspecs qtgraphicaleffects
qtgraphicaleffects-dev qtquickcontrols qtquickcontrols-dev
qtquickcontrols-qmlplugins qtquickcontrols2 qtquickcontrols2-dev
qtquickcontrols2-mkspecs libqt5svg5 libqt5svg-dev libqt5svg-mkspecs
rpm rt-tests rtirq run-postinsts screen ssh-keys-server strace stress
sysstat tar tmux trace-cmd ttf-bitstream-vera udev udev-automount
unzip usbreset usbutils util-linux valgrind wget wireless-tools
wpa-supplicant zip libz1 locale-base-en-us' returned 1:
Added oe-repo repo from
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Mon 14 Jan 2019 04:06:18 PM UTC.
Error:
 Problem: package connman-tools-1.35-r0.aarch64 requires connman, but
none of the providers can be installed
  - package packagegroup-core-tools-testapps-1.0-r2.imx8mmevk requires
connman-tools, but none of the providers can be installed
  - package networkmanager-1.10.6-r0.aarch64 conflicts with connman
provided by connman-1.35-r0.aarch64
  - conflicting requests
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages)

ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp/log.do_rootfs.56617
ERROR: Task 
(/home/user/test/os/sources/meta-custom-imx8/recipes-core/images/custom-image-debug-imx8.bb:do_rootfs)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 8016 tasks of which 7974 didn't need to
be rerun and 1 failed.

Many Thanks in advance,


fsl-image-validation-imx.bb
Description: Binary data


custom-image-debug-imx8.bb
Description: Binary data


custom-image-debug.bbclass
Description: Binary data
-- 
___
yocto-bsp mailing list
yocto-bsp@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto-bsp


[linux-yocto] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64

2019-01-14 Thread srinivasan
Dear Yocto experts,

I am seeing the below error when I am trying to integrate the
"fsl-image-validation-imx.bb" into my custom yocto build and trigger
the build using "bitbake custom-image-debug-imx8.bb", I somewhat feel
networkmanager is conflicting with conman, could you please let me
know how this issue can be resolved?

I have attached the recipe files for your information

Error:

ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Could not invoke dnf.
Command 
'/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/recipe-sysroot-native/usr/bin/dnf
-y -c 
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/dnf/dnf.conf
--setopt=reposdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/yum.repos.d
--repofrompath=oe-repo,/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
--installroot=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs
--setopt=logdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp
--nogpgcheck install alsa-server alsa-tools alsa-utils apt apt-repo
bash basicquick bc binutils binutils-symlinks bmap-tools-git
build-config bzip2 cmake coreutils crashme crda dfu-util diffutils dnf
dnsmasq ethtool file libfreetype6 gdb gdbserver gettext git
glibc-gconv-utf-32 gnupg libharfbuzz0 hidapi hostapd htop iperf3 iw
kernel-dev kernel-devsrc kernel-modules ldd libasound liberation-fonts
libfftw libfftwf libjack libjpeg62 libpng16-16 libtool libxerces-c
libsensors4 lmsensors-sensors lsof lttng-modules make memtester
merge-files nano networkmanager ni-isolcpus ninja openssl
packagegroup-base-extended packagegroup-core-boot
packagegroup-core-full-cmdline packagegroup-core-sdk
packagegroup-core-ssh-dropbear packagegroup-core-standalone-sdk-target
packagegroup-core-tools-debug packagegroup-core-tools-profile
packagegroup-core-tools-testapps packagegroup-fsl-optee-imx
packagegroup-fsl-tools-audio packagegroup-fsl-tools-gpu-external
packagegroup-tools-bluetooth pbzip2 pciutils perf pkgconfig procps
psplash python python-dbus python-modules python-pandas python-pip
python3 python3-dbus python3-misc python3-modules python3-pip
python3-psutil python3-robotframework python3-six qt3d qt3d-dev
qt3d-mkspecs qtbase qtbase-dev qtbase-mkspecs qtbase-plugins
qtbase-tools libqt5charts5 libqt5charts-dev libqt5charts-mkspecs
qtconnectivity-dev qtconnectivity-mkspecs qtdeclarative
qtdeclarative-dev qtdeclarative-mkspecs qtgraphicaleffects
qtgraphicaleffects-dev qtquickcontrols qtquickcontrols-dev
qtquickcontrols-qmlplugins qtquickcontrols2 qtquickcontrols2-dev
qtquickcontrols2-mkspecs libqt5svg5 libqt5svg-dev libqt5svg-mkspecs
rpm rt-tests rtirq run-postinsts screen ssh-keys-server strace stress
sysstat tar tmux trace-cmd ttf-bitstream-vera udev udev-automount
unzip usbreset usbutils util-linux valgrind wget wireless-tools
wpa-supplicant zip libz1 locale-base-en-us' returned 1:
Added oe-repo repo from
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Mon 14 Jan 2019 04:06:18 PM UTC.
Error:
 Problem: package connman-tools-1.35-r0.aarch64 requires connman, but
none of the providers can be installed
  - package packagegroup-core-tools-testapps-1.0-r2.imx8mmevk requires
connman-tools, but none of the providers can be installed
  - package networkmanager-1.10.6-r0.aarch64 conflicts with connman
provided by connman-1.35-r0.aarch64
  - conflicting requests
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages)

ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in:
/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp/log.do_rootfs.56617
ERROR: Task 
(/home/user/test/os/sources/meta-custom-imx8/recipes-core/images/custom-image-debug-imx8.bb:do_rootfs)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 8016 tasks of which 7974 didn't need to
be rerun and 1 failed.

Many Thanks in advance,


fsl-image-validation-imx.bb
Description: Binary data


custom-image-debug-imx8.bb
Description: Binary data


custom-image-debug.bbclass
Description: Binary data
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto


[Yocto-bsp] Error : fsl-image-qt5-validation-imx-imx8mmevk-20181219210506.rootfs.ext4’: No such file or directory in imx-4.14.78-1.0.0_ga.xml in imx-linux-sumo branch

2018-12-19 Thread srinivasan
Dear yocto project experts,

As all our yocto bsps for other hardware platforms support are
developed on yocto sumo version, (And I was able to do the build setup
for imx-linux-rocko ie., yocto rocko version), but now I need to do
for sumo version as this is followed and maintained unique for all our
hardware platfroms, In fact I see for imx-linux-sumo support also
exists, when I try to do this yocto sumo version of build setup using
the below command, I am seeing the below issue, Could you please do
the needful in resolving the below issue


And also, I see there is support for imx yocto bsps for sumo version
ie., in the below link:

imx-manifest - i.MX Release Manifest


$repo init -u https://source.codeaurora.org/external/imx/imx-manifest
-b imx-linux-sumo -m imx-4.14.78-1.0.0_ga.xml

$repo sync

$ DISTRO=fsl-imx-wayland MACHINE=imx8mmevk source fsl-setup-release.sh
-b build-wayland

Build directory is build-wayland

Welcome to Freescale Community BSP

The Yocto Project has extensive documentation about OE including a
reference manual which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/

You can now run 'bitbake '

Common targets are:
core-image-minimal
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support

Your configuration files at build-wayland have not been touched.
BSPDIR=
BUILD_DIR=.
meta-freescale directory found
srinivasan@srinivasan-UX305UA:/media/srinivasan/appu/imx8_sumo/imx-yocto-bsp/build-wayland$
bitbake fsl-image-qt5-validation-imx
NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: You have included the meta-gnome layer, but 'x11' has not
been enabled in your DISTRO_FEATURES. Some bbappend files may not take
effect. See the meta-gnome README for details on enabling meta-gnome
support.
WARNING: Host distribution "ubuntu-14.04" 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%
|#|
Time: 0:00:01
Loaded 3463 entries from dependency cache.
Parsing recipes: 100%
|###|
Time: 0:00:01
Parsing of 2548 .bb files complete (2547 cached, 1 parsed). 3464
targets, 453 skipped, 7 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Multiple providers are available for runtime ptpd (ptpd, ptpd-qoriq)
Consider defining a PREFERRED_RPROVIDER entry to match ptpd
NOTE: Multiple providers are available for runtime ptpd-dev (ptpd, ptpd-qoriq)
Consider defining a PREFERRED_RPROVIDER entry to match ptpd-dev

Build Configuration:
BB_VERSION = "1.38.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-14.04"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "imx8mmevk"
DISTRO = "fsl-imx-wayland"
DISTRO_VERSION = "4.14-sumo"
TUNE_FEATURES = "aarch64"
TARGET_FPU = ""
meta
meta-poky = "HEAD:64a257fa22126c4a40ff7e03424a404e360ebe1e"
meta-oe
meta-multimedia = "HEAD:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966"
meta-freescale = "HEAD:407c6cf408969445031a492e2d25e0e2749582ea"
meta-freescale-3rdparty = "HEAD:88a29631809d1af0df618245430db29f2a7012b5"
meta-freescale-distro = "HEAD:f7e2216e93aff14ac32728a13637a48df436b7f4"
meta-bsp
meta-sdk = "HEAD:9867dae67c158e0820bf226bd18b792623e99b25"
meta-browser = "HEAD:75640e14e325479c076b6272b646be7a239c18aa"
meta-gnome
meta-networking
meta-python
meta-filesystems = "HEAD:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966"
meta-qt5 = "HEAD:d4e7f73d04e8448d326b6f89908701e304e37d65"

Initialising tasks: 100%
||
Time: 0:00:07
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: fsl-image-qt5-validation-imx-1.0-r0 do_image_sdcard: Function
failed: do_image_sdcard (log file is located at
/media/srinivasan/appu/imx8_sumo/imx-yocto-bsp/build-wayland/tmp/work/imx8mmevk-poky-linux/fsl-image-qt5-validation-imx/1.0-r0/temp/log.do_image_sdcard.20472)
ERROR: Logfile of failure stored in:
/media/srinivasan/appu/imx8_sumo/imx-yocto-bsp/build-wayland/tmp/work/imx8mmevk-poky-linux/fsl-image-qt5-validation-imx/1.0-r0/temp/log.do_image_sdcard.20472
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: 1717331.20 = 1321024 * 1.30
| DEBUG: 1717331.20 = max(1717331.20, 65536)[1717331.20] + 1
| DEBUG: 1717332.00 = int(1717331.20)
| DEBUG: 1720320 = aligned(

[linux-yocto] Error : fsl-image-qt5-validation-imx-imx8mmevk-20181219210506.rootfs.ext4’: No such file or directory in imx-4.14.78-1.0.0_ga.xml in imx-linux-sumo branch

2018-12-19 Thread srinivasan
Dear yocto project experts,

As all our yocto bsps for other hardware platforms support are
developed on yocto sumo version, (And I was able to do the build setup
for imx-linux-rocko ie., yocto rocko version), but now I need to do
for sumo version as this is followed and maintained unique for all our
hardware platfroms, In fact I see for imx-linux-sumo support also
exists, when I try to do this yocto sumo version of build setup using
the below command, I am seeing the below issue, Could you please do
the needful in resolving the below issue


And also, I see there is support for imx yocto bsps for sumo version
ie., in the below link:

imx-manifest - i.MX Release Manifest


$repo init -u https://source.codeaurora.org/external/imx/imx-manifest
-b imx-linux-sumo -m imx-4.14.78-1.0.0_ga.xml

$repo sync

$ DISTRO=fsl-imx-wayland MACHINE=imx8mmevk source fsl-setup-release.sh
-b build-wayland

Build directory is build-wayland

Welcome to Freescale Community BSP

The Yocto Project has extensive documentation about OE including a
reference manual which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/

You can now run 'bitbake '

Common targets are:
core-image-minimal
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support

Your configuration files at build-wayland have not been touched.
BSPDIR=
BUILD_DIR=.
meta-freescale directory found
srinivasan@srinivasan-UX305UA:/media/srinivasan/appu/imx8_sumo/imx-yocto-bsp/build-wayland$
bitbake fsl-image-qt5-validation-imx
NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: You have included the meta-gnome layer, but 'x11' has not
been enabled in your DISTRO_FEATURES. Some bbappend files may not take
effect. See the meta-gnome README for details on enabling meta-gnome
support.
WARNING: Host distribution "ubuntu-14.04" 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%
|#|
Time: 0:00:01
Loaded 3463 entries from dependency cache.
Parsing recipes: 100%
|###|
Time: 0:00:01
Parsing of 2548 .bb files complete (2547 cached, 1 parsed). 3464
targets, 453 skipped, 7 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Multiple providers are available for runtime ptpd (ptpd, ptpd-qoriq)
Consider defining a PREFERRED_RPROVIDER entry to match ptpd
NOTE: Multiple providers are available for runtime ptpd-dev (ptpd, ptpd-qoriq)
Consider defining a PREFERRED_RPROVIDER entry to match ptpd-dev

Build Configuration:
BB_VERSION = "1.38.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-14.04"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "imx8mmevk"
DISTRO = "fsl-imx-wayland"
DISTRO_VERSION = "4.14-sumo"
TUNE_FEATURES = "aarch64"
TARGET_FPU = ""
meta
meta-poky = "HEAD:64a257fa22126c4a40ff7e03424a404e360ebe1e"
meta-oe
meta-multimedia = "HEAD:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966"
meta-freescale = "HEAD:407c6cf408969445031a492e2d25e0e2749582ea"
meta-freescale-3rdparty = "HEAD:88a29631809d1af0df618245430db29f2a7012b5"
meta-freescale-distro = "HEAD:f7e2216e93aff14ac32728a13637a48df436b7f4"
meta-bsp
meta-sdk = "HEAD:9867dae67c158e0820bf226bd18b792623e99b25"
meta-browser = "HEAD:75640e14e325479c076b6272b646be7a239c18aa"
meta-gnome
meta-networking
meta-python
meta-filesystems = "HEAD:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966"
meta-qt5 = "HEAD:d4e7f73d04e8448d326b6f89908701e304e37d65"

Initialising tasks: 100%
||
Time: 0:00:07
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: fsl-image-qt5-validation-imx-1.0-r0 do_image_sdcard: Function
failed: do_image_sdcard (log file is located at
/media/srinivasan/appu/imx8_sumo/imx-yocto-bsp/build-wayland/tmp/work/imx8mmevk-poky-linux/fsl-image-qt5-validation-imx/1.0-r0/temp/log.do_image_sdcard.20472)
ERROR: Logfile of failure stored in:
/media/srinivasan/appu/imx8_sumo/imx-yocto-bsp/build-wayland/tmp/work/imx8mmevk-poky-linux/fsl-image-qt5-validation-imx/1.0-r0/temp/log.do_image_sdcard.20472
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: 1717331.20 = 1321024 * 1.30
| DEBUG: 1717331.20 = max(1717331.20, 65536)[1717331.20] + 1
| DEBUG: 1717332.00 = int(1717331.20)
| DEBUG: 1720320 = aligned(

[Yocto-bsp] Error fatal: manifest 'imx-4.9.123-2.3.0-8mm_ga.xml' not available in imx-linux-sumo

2018-12-18 Thread srinivasan
Dear Yocto experts,

As all our yocto bsps for other hardware platforms support are
developed on yocto sumo version, (And I was able to do the build setup
for imx-linux-rocko ie., yocto rocko version), but now I need to do
for sumo version as this is followed and maintained unique for all our
hardware platfroms, In fact I see for imx-linux-sumo support also
exists, when I try to do this yocto sumo version of build setup using
the below command, I am seeing the below issue, Could you please do
the needful in resolving the below issue

https://source.codeaurora.org/external/imx/imx-manifest/tree/?id=871811381ee8d9af3cc309c572ed527e89afb0e0=imx-linux-sumo

yocto sumo version Error:

$ repo init -u https://source.codeaurora.org/external/imx/imx-manifest
-b imx-linux-sumo -m imx-4.9.123-2.3.0-8mm_ga.xml
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
remote: Counting objects: 1, done
remote: Finding sources: 100% (5/5)
remote: Total 5 (delta 1), reused 5 (delta 1)
Unpacking objects: 100% (5/5), done.
>From https://gerrit.googlesource.com/git-repo
   d26146d..6e53844  master -> origin/master
 * [new tag] v1.13.0-> v1.13.0
Get https://source.codeaurora.org/external/imx/imx-manifest
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   161  100   1610 0247  0 --:--:-- --:--:-- --:--:--   247
  0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0
curl: (22) The requested URL returned error: 403
Server does not provide clone.bundle; ignoring.
remote: Counting objects: 361, done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 361 (delta 3), reused 0 (delta 0)
Receiving objects: 100% (361/361), 89.40 KiB | 693.00 KiB/s, done.
Resolving deltas: 100% (213/213), done.
>From https://source.codeaurora.org/external/imx/imx-manifest
 * [new branch]  imx-android-oreo -> origin/imx-android-oreo
 * [new branch]  imx-android-pie  -> origin/imx-android-pie
 * [new branch]  imx-linux-morty  -> origin/imx-linux-morty
 * [new branch]  imx-linux-rocko  -> origin/imx-linux-rocko
 * [new branch]  imx-linux-sumo   -> origin/imx-linux-sumo
 * [new branch]  master   -> origin/master
 * [new tag] rel_imx_4.9.51_8qm_beta1 -> rel_imx_4.9.51_8qm_beta1
fatal: manifest 'imx-4.9.123-2.3.0-8mm_ga.xml' not available
fatal: manifest imx-4.9.123-2.3.0-8mm_ga.xml not found

Kindly do the needful
Many Thanks in advance
-- 
___
yocto-bsp mailing list
yocto-bsp@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto-bsp


[linux-yocto] Error fatal: manifest 'imx-4.9.123-2.3.0-8mm_ga.xml' not available in imx-linux-sumo

2018-12-18 Thread srinivasan
Dear Yocto experts,

As all our yocto bsps for other hardware platforms support are
developed on yocto sumo version, (And I was able to do the build setup
for imx-linux-rocko ie., yocto rocko version), but now I need to do
for sumo version as this is followed and maintained unique for all our
hardware platfroms, In fact I see for imx-linux-sumo support also
exists, when I try to do this yocto sumo version of build setup using
the below command, I am seeing the below issue, Could you please do
the needful in resolving the below issue

https://source.codeaurora.org/external/imx/imx-manifest/tree/?id=871811381ee8d9af3cc309c572ed527e89afb0e0=imx-linux-sumo

yocto sumo version Error:

$ repo init -u https://source.codeaurora.org/external/imx/imx-manifest
-b imx-linux-sumo -m imx-4.9.123-2.3.0-8mm_ga.xml
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
remote: Counting objects: 1, done
remote: Finding sources: 100% (5/5)
remote: Total 5 (delta 1), reused 5 (delta 1)
Unpacking objects: 100% (5/5), done.
>From https://gerrit.googlesource.com/git-repo
   d26146d..6e53844  master -> origin/master
 * [new tag] v1.13.0-> v1.13.0
Get https://source.codeaurora.org/external/imx/imx-manifest
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100   161  100   1610 0247  0 --:--:-- --:--:-- --:--:--   247
  0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0
curl: (22) The requested URL returned error: 403
Server does not provide clone.bundle; ignoring.
remote: Counting objects: 361, done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 361 (delta 3), reused 0 (delta 0)
Receiving objects: 100% (361/361), 89.40 KiB | 693.00 KiB/s, done.
Resolving deltas: 100% (213/213), done.
>From https://source.codeaurora.org/external/imx/imx-manifest
 * [new branch]  imx-android-oreo -> origin/imx-android-oreo
 * [new branch]  imx-android-pie  -> origin/imx-android-pie
 * [new branch]  imx-linux-morty  -> origin/imx-linux-morty
 * [new branch]  imx-linux-rocko  -> origin/imx-linux-rocko
 * [new branch]  imx-linux-sumo   -> origin/imx-linux-sumo
 * [new branch]  master   -> origin/master
 * [new tag] rel_imx_4.9.51_8qm_beta1 -> rel_imx_4.9.51_8qm_beta1
fatal: manifest 'imx-4.9.123-2.3.0-8mm_ga.xml' not available
fatal: manifest imx-4.9.123-2.3.0-8mm_ga.xml not found

Kindly do the needful
Many Thanks in advance
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto


[yocto] include in the image mtd-utils-ubifs

2018-11-20 Thread Srinivasan, Raja
All

I am trying to include the ubi-utils (ubiformat etc in my image.

I included mtd-utils in CORE_IMAGE_EXTRA_INSTALL which appears to result in 
building the system.

Except these are not included in my image.

I was told to include the package mtd-utils-ubifs to the list of packages. Not 
clear how I could do this. Anyone can point me in the right direction?

Thanks, srini



CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [Yocto-bsp] [poky] Yocto kernel compilation issues

2018-09-04 Thread srinivasan
"inherit kernel" doesn't allow to add new kernels for the very first to
yocto build system for example adding the below kernel



*- The kernel used would be the Linux-rt-devel v4.14.39 from the git repo
in https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/
<https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/>*

Because I tried adding the above new kernel for the first time using
"inherit kernel", and ended with number of issues

And I hope, "inherit kernel" works only for yocto based linux kernels that
is already available.

Could you please guide me if my understanding is wrong w.r.t the above?

On Wed, Sep 5, 2018 at 8:21 AM Paul Eggleton 
wrote:

> On Wednesday, 5 September 2018 1:44:22 PM NZST srinivasan wrote:
> > Adding the "DEPENDS += "xz-native bc-native" in the "linux-srini_4.14.bb
> "
> > did the trick
>
> FYI the main issue with your kernel recipe is it does not "inherit kernel"
> which takes care of this (and many other things) for you. I guess you
> based
> your recipe on linux-dummy.bb, but that recipe is special and shouldn't
> be
> used as a template for a real kernel.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
>
>
-- 
___
yocto-bsp mailing list
yocto-bsp@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto-bsp


Re: [linux-yocto] [poky] Yocto kernel compilation issues

2018-09-04 Thread srinivasan
"inherit kernel" doesn't allow to add new kernels for the very first to
yocto build system for example adding the below kernel



*- The kernel used would be the Linux-rt-devel v4.14.39 from the git repo
in https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/
<https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/>*

Because I tried adding the above new kernel for the first time using
"inherit kernel", and ended with number of issues

And I hope, "inherit kernel" works only for yocto based linux kernels that
is already available.

Could you please guide me if my understanding is wrong w.r.t the above?

On Wed, Sep 5, 2018 at 8:21 AM Paul Eggleton 
wrote:

> On Wednesday, 5 September 2018 1:44:22 PM NZST srinivasan wrote:
> > Adding the "DEPENDS += "xz-native bc-native" in the "linux-srini_4.14.bb
> "
> > did the trick
>
> FYI the main issue with your kernel recipe is it does not "inherit kernel"
> which takes care of this (and many other things) for you. I guess you
> based
> your recipe on linux-dummy.bb, but that recipe is special and shouldn't
> be
> used as a template for a real kernel.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
>
>
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto


Re: [linux-yocto] [poky] Yocto kernel compilation issues

2018-09-04 Thread srinivasan
Adding the "DEPENDS += "xz-native bc-native" in the "linux-srini_4.14.bb"
did the trick

Many many thanks for all your support :)

On Wed 5 Sep, 2018, 7:12 AM Khem Raj,  wrote:

> in your local.conf add
>
> HOSTTOOLS += "bc"
>
> see if that helps
>
> On Tue, Sep 4, 2018 at 5:33 PM srinivasan 
> wrote:
>
>>
>> srinivasan 
>> 5:55 AM (4 minutes ago)
>> to *yocto-infrastructure*
>> After changing from "*do_compile_ () {*" to "*do_compile() {*", in the
>> attached recipe file, Compilation started but got stuck  "*/bin/sh: 1:
>> bc: not found*
>>
>> *make[1]: *** [include/generated/timeconst.h] Error 127*
>> *make: *** [prepare0] Error 2*
>> *make: *** Waiting for unfinished jobs"*
>>
>> *Even I tried installing "*sudo apt-get install bc"* but still the same
>> issue as above, Kindly do the needful in resolving the above issue as am
>> stuck with the same issue from past 4 days*
>>
>> *And I am even able to build kernel independently before integrating into
>> yocto project*
>>
>> *References:*
>>
>> *1. Ubuntu version used 14.04*
>>
>> *2. Poky Distro version*
>>
>> DISTRO = "poky"
>> DISTRO_NAME = "Poky (Yocto Project Reference Distro)"
>> DISTRO_VERSION = "2.5+snapshot-${DATE}"
>>
>> *3.Logs:*
>>
>> NOTE: linux-srini-4.14-r1 do_prepare_recipe_sysroot: Direct dependencies
>> are
>> ['/home/srinivasan/yocto_session_ws_2/poky/meta/recipes-devtools/libtool/libtool-native_2.4.6.bb:do_populate_sysroot',
>> 'virtual:native:/home/srinivasan/yocto_session_ws_2/poky/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_populate_sysroot',
>> 'virtual:native:/home/srinivasan/yocto_session_ws_2/poky/meta/recipes-devtools/autoconf/autoconf_2.69.bb:do_populate_sysroot',
>> 'virtual:native:/home/srinivasan/yocto_session_ws_2/poky/meta/recipes-devtools/automake/automake_1.16.1.bb:
>> do_populate_sysroot']
>> NOTE: linux-srini-4.14-r1 do_prepare_recipe_sysroot: Installed into
>> sysroot: ['libtool-native', 'gnu-config-native', 'autoconf-native',
>> 'automake-native', 'texinfo-dummy-native', 'quilt-native', 'm4-native']
>> + cd
>> /home/srinivasan/yocto_session_ws_2/build/tmp/work/i586-poky-linux/linux-srini/4.14-r1/git
>>
>> NOTE: linux-srini-4.14-r1 do_compile: make -j 4 mrproper
>> + oe_runmake mrproper
>> + oe_runmake_call mrproper
>> + bbnote make -j 4 mrproper
>> + [ -p
>> /home/srinivasan/yocto_session_ws_2/build/tmp/work/i586-poky-linux/linux-srini/4.14-r1/temp/fifo.7174
>> ]
>> + printf %b\0 bbnote make -j 4 mrproper
>> + make -j 4 mrproper
>>
>>   CLEAN   .config
>>
>> + oe_runmake defconfig
>> + oe_runmake_call defconfig
>> + bbnote make -j 4 defconfig
>>
>> NOTE: linux-srini-4.14-r1 do_compile: make -j 4 defconfig
>> + [ -p
>> /home/srinivasan/yocto_session_ws_2/build/tmp/work/i586-poky-linux/linux-srini/4.14-r1/temp/fifo.7174
>> ]
>> + printf %b\0 bbnote make -j 4 defconfig
>> + make -j 4 defconfig
>>
>>   HOSTCC  scripts/basic/fixdep
>>
>>   HOSTCC  scripts/kconfig/conf.o
>>
>>   SHIPPED scripts/kconfig/zconf.tab.c
>>
>>   SHIPPED scripts/kconfig/zconf.lex.c
>>
>>   HOSTCC  scripts/kconfig/zconf.tab.o
>>
>>   HOSTLD  scripts/kconfig/conf
>>
>> *** Default configuration is based on 'x86_64_defconfig'
>>
>> #
>> # configuration written to .config
>> #
>>
>> + oe_runmake
>> + oe_runmake_call
>> + bbnote make -j 4
>> + [ -p
>> NOTE: linux-srini-4.14-r1 do_compile: make -j 4
>>  
>> /home/srinivasan/yocto_session_ws_2/build/tmp/work/i586-poky-linux/linux-srini/4.14-r1/temp/fifo.7174
>> ]
>> + printf %b\0 bbnote make -j 4
>> + make -j 4
>>
>> scripts/kconfig/conf  --silentoldconfig Kconfig
>>
>>   SYSTBL
>> arch/x86/entry/syscalls/../../include/generated/asm/syscalls_32.h
>>
>>   SYSHDR
>> arch/x86/entry/syscalls/../../include/generated/asm/unistd_32_ia32.h
>>
>>   SYSHDR
>> arch/x86/entry/syscalls/../../include/generated/asm/unistd_64_x32.h
>>
>>   CHK include/config/kernel.release
>>
>>   SYSTBL
>> arch/x86/entry/syscalls/../../include/generated/asm/syscalls_64.h
>>
>>   SYSHDR
>> arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_32.h
>>
>>   SYSHDR
>> arch/x86/entry/syscalls/../../include/generated/uapi/asm/unistd_64.h
>>
>>   SYSHDR
>> arch/x86/entry/s

[yocto] Disable cert validation

2018-08-28 Thread Srinivasan, Raja
All

I have a situation where our device (yocto - Jethro) is failing to validate a 
certificate.

12520 EAP-TLS failed SSL/TLS handshake because the client rejected the ISE 
local-certificate.

I would like to disable the cert validation. Is there an nmcli command (or some 
other way) that I could disable?

Thanks, srini






CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] uBoot, kernel and device tree files

2018-08-09 Thread Srinivasan, Raja
Mathieu

Appreciate the suggestion. Will give it a shot. Thanks, srini

-Original Message-
From: Mathieu Alexandre-Tétreault [mailto:alexandr...@amotus.ca]
Sent: Thursday, August 9, 2018 8:45 AM
To: Srinivasan, Raja ; yocto@yoctoproject.org
Subject: RE: uBoot, kernel and device tree files

Hello Srini,

I think what you are looking for is the fitimage, it will allow you to bundle 
the kernel and devicetree together in a single file and it also allows you add 
a signature.

This process is well integrated in yocto, from what I remember activating the 
fitimage is relatively easy:
   - in your machine.conf
   - declare KERNEL_CLASSES += "kernel-fitimage" and KERNEL_IMAGETYPE = 
"fitimage"
   - in your u-boot defconfig (configs/yourboard_defconfig
   - enable CONFIG_FIT=y
   - in your config include/configs/your_board.h change the script to boot your 
fitimage

I hope this helps,

Regards,

Mathieu

> -Message d'origine-
> De : yocto-boun...@yoctoproject.org 
> De la part de Srinivasan, Raja Envoyé : August 8, 2018 2:51 PM À :
> yocto@yoctoproject.org Objet : [yocto] uBoot, kernel and device tree
> files
>
> All
>
>
>
> We are using rocko.on variscite var-som-mx6.
>
> In order to increase the security of our system (during a system
> upgrade), we are looking to merge uImage (kernel image) and the device
> tree file into 1 file. Currently these are 2 different files and are
> worried that a file copy operation might get aborted.
>
> My research so far indicates mkuboot can be used to merge these. but
> having trouble making this work.
>
> Need some ideas.
>
>
>
> Any pointers appreciated. srini
>
>
>
>
>
>
> 
>
>
> CONFIDENTIALITY NOTICE: This email message and any attachments are
> confidential and may be privileged and are meant to be read by the
> intended recipient only. If you are not the intended recipient, please
> notify sender immediately and destroy all copies of this message and
> any attachments without reading or disclosing their contents. Thank
> you
>
>
>




CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] uBoot, kernel and device tree files

2018-08-09 Thread Srinivasan, Raja
Appreciate the suggestions. I will try them out. thanks, srini

-Original Message-
From: Michal Vokáč [mailto:michal.vo...@ysoft.com]
Sent: Thursday, August 9, 2018 4:41 AM
To: Srinivasan, Raja 
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] uBoot, kernel and device tree files

Hi Srini,

On 8.8.2018 20:51, Srinivasan, Raja wrote:
> All
>
> We are using rocko.on variscite var-som-mx6.
>
> In order to increase the security of our system (during a system upgrade), we 
> are looking to merge uImage (kernel image) and the device tree file into 1 
> file. Currently these are 2 different files and are worried that a file copy 
> operation might get aborted.

I understand that what you want to achive by combining the files is 
"relyability" and not "security". Those are totaly different things.

> My research so far indicates mkuboot can be used to merge these. but having 
> trouble making this work.
>
> Need some ideas.
>
> Any pointers appreciated. srini

I am aware of at least two options to combine kernel images and device tree 
files.

Option 1) Append DTB directly to the kernel image

This is the simplest option. Just use cat to concatenate the files and enable 
the CONFIG_ARM_APPENDED_DTB kernel option.
Read the help for the option, it is quite informative.

In this case you do not need to change anything in your boot loader.
Just load and boot the combined image as usual and kernel will do the rest.

Option 2) Use FIT images

I strongly recommend this option over the first one.
FIT images are something like containers that can contain multiple kernel 
images, multiple device tree blobs, multiple initram file systems.
Part of the FIT image then describes what combinations of those files can be 
used to boot.

If your concern is not just reliability but also security than FIT images are 
also better. You can put hashes/signatures of all the files into the 
description of the files and use the hashes in the bootloader to verify the 
images (I never used that.)

In this option you need to change your boot command.

Hope this helps,
Michal




CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] uBoot, kernel and device tree files

2018-08-08 Thread Srinivasan, Raja
All

We are using rocko.on variscite var-som-mx6.

In order to increase the security of our system (during a system upgrade), we 
are looking to merge uImage (kernel image) and the device tree file into 1 
file. Currently these are 2 different files and are worried that a file copy 
operation might get aborted.

My research so far indicates mkuboot can be used to merge these. but having 
trouble making this work.

Need some ideas.

Any pointers appreciated. srini





CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] rdiff and rdiff-backup

2018-04-25 Thread Srinivasan, Raja
Would like to know if anyone is using rdiff-backup in a yocto system. Does it 
work well. (We are using Jethro). Please share any experiences you may have.

Thanks, srini





CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you

Disclaimer

The information contained in this communication from the sender is 
confidential. It is intended solely for use by the recipient and others 
authorized to receive it. If you are not the recipient, you are hereby notified 
that any disclosure, copying, distribution or taking action in relation of the 
contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been 
automatically archived by Mimecast Ltd, an innovator in Software as a Service 
(SaaS) for business. Providing a safer and more useful place for your human 
generated data. Specializing in; Security, archiving and compliance. To find 
out more visit the Mimecast website.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] adding other languages to yocto build

2018-04-01 Thread Srinivasan, Raja
Thanks a bunch. srini

-Original Message-
From: Philip Balister [mailto:phi...@balister.org]
Sent: Sunday, April 1, 2018 1:09 PM
To: Srinivasan, Raja <rsriniva...@abiomed.com>; yocto@yoctoproject.org
Subject: Re: [yocto] adding other languages to yocto build

On 03/30/2018 07:42 AM, Srinivasan, Raja wrote:
> friends,
>
> ?
>
> anyone using ada, objective c, c#, swift or any other such languages.
> if so can you point me to a recipe. my interest is in the order
> listed. looking for an alternative to C/C++

I searched the layer index[1] for "ada" and found

https://github.com/Lucretia/meta-ada

Be warned, the last commit is five years old, but hopefully it helps answer 
some of your questions.

Philip

[1] http://layers.openembedded.org

>
>
> TIA
>
> srini
>
> 
>
> CONFIDENTIALITY NOTICE: This email message and any attachments are
> confidential and may be privileged and are meant to be read by the
> intended recipient only. If you are not the intended recipient, please
> notify sender immediately and destroy all copies of this message and
> any attachments without reading or disclosing their contents. Thank
> you
>
> Disclaimer
>
> The information contained in this communication from the sender is 
> confidential. It is intended solely for use by the recipient and others 
> authorized to receive it. If you are not the recipient, you are hereby 
> notified that any disclosure, copying, distribution or taking action in 
> relation of the contents of this information is strictly prohibited and may 
> be unlawful.
>
> This email has been scanned for viruses and malware, and may have been 
> automatically archived by Mimecast Ltd, an innovator in Software as a Service 
> (SaaS) for business. Providing a safer and more useful place for your human 
> generated data. Specializing in; Security, archiving and compliance. To find 
> out more visit the Mimecast website.
>
>
>




CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you

Disclaimer

The information contained in this communication from the sender is 
confidential. It is intended solely for use by the recipient and others 
authorized to receive it. If you are not the recipient, you are hereby notified 
that any disclosure, copying, distribution or taking action in relation of the 
contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been 
automatically archived by Mimecast Ltd, an innovator in Software as a Service 
(SaaS) for business. Providing a safer and more useful place for your human 
generated data. Specializing in; Security, archiving and compliance. To find 
out more visit the Mimecast website.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] adding other languages to yocto build

2018-03-30 Thread Srinivasan, Raja
friends,

?

anyone using ada, objective c, c#, swift or any other such languages. if so can 
you point me to a recipe. my interest is in the order listed. looking for an 
alternative to C/C++


TIA

srini



CONFIDENTIALITY NOTICE: This email message and any attachments are confidential 
and may be privileged and are meant to be read by the intended recipient only. 
If you are not the intended recipient, please notify sender immediately and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you

Disclaimer

The information contained in this communication from the sender is 
confidential. It is intended solely for use by the recipient and others 
authorized to receive it. If you are not the recipient, you are hereby notified 
that any disclosure, copying, distribution or taking action in relation of the 
contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been 
automatically archived by Mimecast Ltd, an innovator in Software as a Service 
(SaaS) for business. Providing a safer and more useful place for your human 
generated data. Specializing in; Security, archiving and compliance. To find 
out more visit the Mimecast website.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

2017-12-08 Thread Gunasekaran Srinivasan
Ross,

Fresh build also didn't solve the issue. Is there anything I could try?

Thanks,
Guna

On Fri, Dec 8, 2017 at 4:20 PM, Gunasekaran Srinivasan <
gunaseka...@solitontech.com> wrote:

> Ross,
>
> Oh!
> I tried adding DISTRO_FEATURE, still the same issue. I will clean the
> build and run once I again.
>
> Thanks,
> Guna
>
> On Fri, Dec 8, 2017 at 4:17 PM, Burton, Ross <ross.bur...@intel.com>
> wrote:
>
>> core-image-sato will refuse to build long before matchbox-desktop if x11
>> is disabled.
>>
>> Ross
>>
>> On 8 December 2017 at 10:46, Gunasekaran Srinivasan <
>> gunaseka...@solitontech.com> wrote:
>>
>>> I will check that. Shouldn't core-image-sato recipecome with x11
>>> enabled?
>>>
>>> Thanks,
>>> Guna
>>>
>>> On Fri, Dec 8, 2017 at 4:11 PM, Burton, Ross <ross.bur...@intel.com>
>>> wrote:
>>>
>>>> I'm surprised it go that far as libx11 should have refused to build if
>>>> X was disabled.  To enable X:
>>>>
>>>> DISTRO_FEATURES_append = " x11"
>>>>
>>>> Ross
>>>>
>>>> On 8 December 2017 at 10:40, Gunasekaran Srinivasan <
>>>> gunaseka...@solitontech.com> wrote:
>>>>
>>>>> No. I haven't. If it's disabled by default. Can you tell how to enable
>>>>> in conf/local.conf file?
>>>>>
>>>>> Thanks,
>>>>> Guna
>>>>>
>>>>> On Fri, Dec 8, 2017 at 3:54 PM, Burton, Ross <ross.bur...@intel.com>
>>>>> wrote:
>>>>>
>>>>>> gdk-x11 is part of the gtk+3 recipe, which is a dependency of
>>>>>> matchbox-desktop.  matchbox-desktop needs X11, so has your BSP disabled 
>>>>>> X11?
>>>>>>
>>>>>> Ross
>>>>>>
>>>>>> On 8 December 2017 at 03:02, Gunasekaran Srinivasan <
>>>>>> gunaseka...@solitontech.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I am trying to build core-image-sato image with poky 2.2.2. I am
>>>>>>> getting following error in matchbox-panel recipe
>>>>>>>
>>>>>>> 
>>>>>>> ..
>>>>>>>  checking what language compliance flags to pass to the C compiler...
>>>>>>> | checking for arm-poky-linux-gnueabi-pkg-config... no
>>>>>>> | checking for pkg-config... fsl-community-bsp/matc
>>>>>>> hbox/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
>>>>>>> | checking pkg-config is at least version 0.9.0... yes
>>>>>>> | checking for MATCHBOX_PANEL... no
>>>>>>> | configure: error: Package requirements (glib-2.0
>>>>>>> |   gmodule-export-2.0
>>>>>>> |   x11
>>>>>>> |   gdk-x11-3.0
>>>>>>> |   gtk+-3.0) were not met:
>>>>>>> |
>>>>>>> | No package 'gdk-x11-3.0' found
>>>>>>> |
>>>>>>> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
>>>>>>> | installed software in a non-standard prefix.
>>>>>>> |
>>>>>>> | Alternatively, you may set the environment variables
>>>>>>> MATCHBOX_PANEL_CFLAGS
>>>>>>> | and MATCHBOX_PANEL_LIBS to avoid the need to call pkg-config.
>>>>>>> | See the pkg-config man page for more details.
>>>>>>> | WARNING: exit code 1 from a shell command.
>>>>>>> | ERROR: Function failed: do_configure (log file is located at
>>>>>>> /fsl-community-bsp/matchbox/tmp/work/cortexa9hf-neon-p
>>>>>>> oky-linux-gnueabi/matchbox-panel-2/2.11-r0/temp/log.do_confi
>>>>>>> gure.27179)
>>>>>>> ERROR: Task (/fsl-community-bsp/sour
>>>>>>> ces/poky/meta/recipes-sato/matchbox-panel-2/matchbox-panel-2
>>>>>>> _2.11.bb:do_configure) failed with exit code '1'
>>>>>>> NOTE: Tasks Summary: Attempted 2607 tasks of which 0 didn't need to
>>>>>>> be rerun and 1 failed.
>>>>>>>
>>>>>>> Summary: 1 task failed:
>>>>>>>   /fsl-community-bsp/sources/poky/meta/recipes-sato/matc
>>>>>>> hbox-panel-2/matchbox-panel-2_2.11.bb:do_configure
>>>>>>>
>>>>>>> Is there a recipe for gdk-x11 in yocto?
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Guna
>>>>>>>
>>>>>>> --
>>>>>>> ___
>>>>>>> yocto mailing list
>>>>>>> yocto@yoctoproject.org
>>>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

2017-12-08 Thread Gunasekaran Srinivasan
Ross,

Oh!
I tried adding DISTRO_FEATURE, still the same issue. I will clean the build
and run once I again.

Thanks,
Guna

On Fri, Dec 8, 2017 at 4:17 PM, Burton, Ross <ross.bur...@intel.com> wrote:

> core-image-sato will refuse to build long before matchbox-desktop if x11
> is disabled.
>
> Ross
>
> On 8 December 2017 at 10:46, Gunasekaran Srinivasan <
> gunaseka...@solitontech.com> wrote:
>
>> I will check that. Shouldn't core-image-sato recipecome with x11 enabled?
>>
>> Thanks,
>> Guna
>>
>> On Fri, Dec 8, 2017 at 4:11 PM, Burton, Ross <ross.bur...@intel.com>
>> wrote:
>>
>>> I'm surprised it go that far as libx11 should have refused to build if X
>>> was disabled.  To enable X:
>>>
>>> DISTRO_FEATURES_append = " x11"
>>>
>>> Ross
>>>
>>> On 8 December 2017 at 10:40, Gunasekaran Srinivasan <
>>> gunaseka...@solitontech.com> wrote:
>>>
>>>> No. I haven't. If it's disabled by default. Can you tell how to enable
>>>> in conf/local.conf file?
>>>>
>>>> Thanks,
>>>> Guna
>>>>
>>>> On Fri, Dec 8, 2017 at 3:54 PM, Burton, Ross <ross.bur...@intel.com>
>>>> wrote:
>>>>
>>>>> gdk-x11 is part of the gtk+3 recipe, which is a dependency of
>>>>> matchbox-desktop.  matchbox-desktop needs X11, so has your BSP disabled 
>>>>> X11?
>>>>>
>>>>> Ross
>>>>>
>>>>> On 8 December 2017 at 03:02, Gunasekaran Srinivasan <
>>>>> gunaseka...@solitontech.com> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I am trying to build core-image-sato image with poky 2.2.2. I am
>>>>>> getting following error in matchbox-panel recipe
>>>>>>
>>>>>> 
>>>>>> ..
>>>>>>  checking what language compliance flags to pass to the C compiler...
>>>>>> | checking for arm-poky-linux-gnueabi-pkg-config... no
>>>>>> | checking for pkg-config... fsl-community-bsp/matc
>>>>>> hbox/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
>>>>>> | checking pkg-config is at least version 0.9.0... yes
>>>>>> | checking for MATCHBOX_PANEL... no
>>>>>> | configure: error: Package requirements (glib-2.0
>>>>>> |   gmodule-export-2.0
>>>>>> |   x11
>>>>>> |   gdk-x11-3.0
>>>>>> |   gtk+-3.0) were not met:
>>>>>> |
>>>>>> | No package 'gdk-x11-3.0' found
>>>>>> |
>>>>>> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
>>>>>> | installed software in a non-standard prefix.
>>>>>> |
>>>>>> | Alternatively, you may set the environment variables
>>>>>> MATCHBOX_PANEL_CFLAGS
>>>>>> | and MATCHBOX_PANEL_LIBS to avoid the need to call pkg-config.
>>>>>> | See the pkg-config man page for more details.
>>>>>> | WARNING: exit code 1 from a shell command.
>>>>>> | ERROR: Function failed: do_configure (log file is located at
>>>>>> /fsl-community-bsp/matchbox/tmp/work/cortexa9hf-neon-p
>>>>>> oky-linux-gnueabi/matchbox-panel-2/2.11-r0/temp/log.do_confi
>>>>>> gure.27179)
>>>>>> ERROR: Task (/fsl-community-bsp/sour
>>>>>> ces/poky/meta/recipes-sato/matchbox-panel-2/matchbox-panel-2_2.11.bb:do_configure)
>>>>>> failed with exit code '1'
>>>>>> NOTE: Tasks Summary: Attempted 2607 tasks of which 0 didn't need to
>>>>>> be rerun and 1 failed.
>>>>>>
>>>>>> Summary: 1 task failed:
>>>>>>   /fsl-community-bsp/sources/poky/meta/recipes-sato/matc
>>>>>> hbox-panel-2/matchbox-panel-2_2.11.bb:do_configure
>>>>>>
>>>>>> Is there a recipe for gdk-x11 in yocto?
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Guna
>>>>>>
>>>>>> --
>>>>>> ___
>>>>>> yocto mailing list
>>>>>> yocto@yoctoproject.org
>>>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

2017-12-08 Thread Gunasekaran Srinivasan
I will check that. Shouldn't core-image-sato recipecome with x11 enabled?

Thanks,
Guna

On Fri, Dec 8, 2017 at 4:11 PM, Burton, Ross <ross.bur...@intel.com> wrote:

> I'm surprised it go that far as libx11 should have refused to build if X
> was disabled.  To enable X:
>
> DISTRO_FEATURES_append = " x11"
>
> Ross
>
> On 8 December 2017 at 10:40, Gunasekaran Srinivasan <
> gunaseka...@solitontech.com> wrote:
>
>> No. I haven't. If it's disabled by default. Can you tell how to enable in
>> conf/local.conf file?
>>
>> Thanks,
>> Guna
>>
>> On Fri, Dec 8, 2017 at 3:54 PM, Burton, Ross <ross.bur...@intel.com>
>> wrote:
>>
>>> gdk-x11 is part of the gtk+3 recipe, which is a dependency of
>>> matchbox-desktop.  matchbox-desktop needs X11, so has your BSP disabled X11?
>>>
>>> Ross
>>>
>>> On 8 December 2017 at 03:02, Gunasekaran Srinivasan <
>>> gunaseka...@solitontech.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I am trying to build core-image-sato image with poky 2.2.2. I am
>>>> getting following error in matchbox-panel recipe
>>>>
>>>> 
>>>> ..
>>>>  checking what language compliance flags to pass to the C compiler...
>>>> | checking for arm-poky-linux-gnueabi-pkg-config... no
>>>> | checking for pkg-config... fsl-community-bsp/matc
>>>> hbox/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
>>>> | checking pkg-config is at least version 0.9.0... yes
>>>> | checking for MATCHBOX_PANEL... no
>>>> | configure: error: Package requirements (glib-2.0
>>>> |   gmodule-export-2.0
>>>> |   x11
>>>> |   gdk-x11-3.0
>>>> |   gtk+-3.0) were not met:
>>>> |
>>>> | No package 'gdk-x11-3.0' found
>>>> |
>>>> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
>>>> | installed software in a non-standard prefix.
>>>> |
>>>> | Alternatively, you may set the environment variables
>>>> MATCHBOX_PANEL_CFLAGS
>>>> | and MATCHBOX_PANEL_LIBS to avoid the need to call pkg-config.
>>>> | See the pkg-config man page for more details.
>>>> | WARNING: exit code 1 from a shell command.
>>>> | ERROR: Function failed: do_configure (log file is located at
>>>> /fsl-community-bsp/matchbox/tmp/work/cortexa9hf-neon-p
>>>> oky-linux-gnueabi/matchbox-panel-2/2.11-r0/temp/log.do_configure.27179)
>>>> ERROR: Task (/fsl-community-bsp/sour
>>>> ces/poky/meta/recipes-sato/matchbox-panel-2/matchbox-panel-2_2.11.bb:do_configure)
>>>> failed with exit code '1'
>>>> NOTE: Tasks Summary: Attempted 2607 tasks of which 0 didn't need to be
>>>> rerun and 1 failed.
>>>>
>>>> Summary: 1 task failed:
>>>>   /fsl-community-bsp/sources/poky/meta/recipes-sato/matc
>>>> hbox-panel-2/matchbox-panel-2_2.11.bb:do_configure
>>>>
>>>> Is there a recipe for gdk-x11 in yocto?
>>>>
>>>>
>>>> Thanks,
>>>> Guna
>>>>
>>>> --
>>>> ___
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>>
>>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

2017-12-08 Thread Gunasekaran Srinivasan
No. I haven't. If it's disabled by default. Can you tell how to enable in
conf/local.conf file?

Thanks,
Guna

On Fri, Dec 8, 2017 at 3:54 PM, Burton, Ross <ross.bur...@intel.com> wrote:

> gdk-x11 is part of the gtk+3 recipe, which is a dependency of
> matchbox-desktop.  matchbox-desktop needs X11, so has your BSP disabled X11?
>
> Ross
>
> On 8 December 2017 at 03:02, Gunasekaran Srinivasan <
> gunaseka...@solitontech.com> wrote:
>
>> Hi all,
>>
>> I am trying to build core-image-sato image with poky 2.2.2. I am getting
>> following error in matchbox-panel recipe
>>
>> 
>> ..
>>  checking what language compliance flags to pass to the C compiler...
>> | checking for arm-poky-linux-gnueabi-pkg-config... no
>> | checking for pkg-config... fsl-community-bsp/matc
>> hbox/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
>> | checking pkg-config is at least version 0.9.0... yes
>> | checking for MATCHBOX_PANEL... no
>> | configure: error: Package requirements (glib-2.0
>> |   gmodule-export-2.0
>> |   x11
>> |   gdk-x11-3.0
>> |   gtk+-3.0) were not met:
>> |
>> | No package 'gdk-x11-3.0' found
>> |
>> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> | installed software in a non-standard prefix.
>> |
>> | Alternatively, you may set the environment variables
>> MATCHBOX_PANEL_CFLAGS
>> | and MATCHBOX_PANEL_LIBS to avoid the need to call pkg-config.
>> | See the pkg-config man page for more details.
>> | WARNING: exit code 1 from a shell command.
>> | ERROR: Function failed: do_configure (log file is located at
>> /fsl-community-bsp/matchbox/tmp/work/cortexa9hf-neon-p
>> oky-linux-gnueabi/matchbox-panel-2/2.11-r0/temp/log.do_configure.27179)
>> ERROR: Task (/fsl-community-bsp/sources/poky/meta/recipes-sato/mat
>> chbox-panel-2/matchbox-panel-2_2.11.bb:do_configure) failed with exit
>> code '1'
>> NOTE: Tasks Summary: Attempted 2607 tasks of which 0 didn't need to be
>> rerun and 1 failed.
>>
>> Summary: 1 task failed:
>>   /fsl-community-bsp/sources/poky/meta/recipes-sato/matc
>> hbox-panel-2/matchbox-panel-2_2.11.bb:do_configure
>>
>> Is there a recipe for gdk-x11 in yocto?
>>
>>
>> Thanks,
>> Guna
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

2017-12-08 Thread Gunasekaran Srinivasan
Hi all,

I am trying to build core-image-sato image with poky 2.2.2. I am getting
following error in matchbox-panel recipe

..
 checking what language compliance flags to pass to the C compiler...
| checking for arm-poky-linux-gnueabi-pkg-config... no
| checking for pkg-config...
fsl-community-bsp/matchbox/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
| checking pkg-config is at least version 0.9.0... yes
| checking for MATCHBOX_PANEL... no
| configure: error: Package requirements (glib-2.0
|   gmodule-export-2.0
|   x11
|   gdk-x11-3.0
|   gtk+-3.0) were not met:
|
| No package 'gdk-x11-3.0' found
|
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
|
| Alternatively, you may set the environment variables MATCHBOX_PANEL_CFLAGS
| and MATCHBOX_PANEL_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at
/fsl-community-bsp/matchbox/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/matchbox-panel-2/2.11-r0/temp/log.do_configure.27179)
ERROR: Task
(/fsl-community-bsp/sources/poky/meta/recipes-sato/matchbox-panel-2/matchbox-panel-2_2.11.bb:do_configure)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 2607 tasks of which 0 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

/fsl-community-bsp/sources/poky/meta/recipes-sato/matchbox-panel-2/matchbox-panel-2_2.11.bb:
do_configure

Is there a recipe for gdk-x11 in yocto?


Thanks,
Guna
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Morty Branch: Error in building core-image-sato | matchbox-panel recipe

2017-12-07 Thread Gunasekaran Srinivasan
Hi all,

I am trying to build core-image-sato image with poky 2.2.2. I am getting
following error in matchbox-panel recipe


..
 checking what language compliance flags to pass to the C compiler...
| checking for arm-poky-linux-gnueabi-pkg-config... no
| checking for pkg-config... fsl-community-bsp/
matchbox/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
| checking pkg-config is at least version 0.9.0... yes
| checking for MATCHBOX_PANEL... no
| configure: error: Package requirements (glib-2.0
|   gmodule-export-2.0
|   x11
|   gdk-x11-3.0
|   gtk+-3.0) were not met:
|
| No package 'gdk-x11-3.0' found
|
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
|
| Alternatively, you may set the environment variables MATCHBOX_PANEL_CFLAGS
| and MATCHBOX_PANEL_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at
/fsl-community-bsp/matchbox/tmp/work/cortexa9hf-
neon-poky-linux-gnueabi/matchbox-panel-2/2.11-r0/temp/
log.do_configure.27179)
ERROR: Task (/fsl-community-bsp/sources/poky/meta/recipes-
sato/matchbox-panel-2/matchbox-panel-2_2.11.bb:do_configure) failed with
exit code '1'
NOTE: Tasks Summary: Attempted 2607 tasks of which 0 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
  /fsl-community-bsp/sources/poky/meta/recipes-sato/matchbox-panel-2/
matchbox-panel-2_2.11.bb:do_configure

Is there a recipe for gdk-x11 in yocto?


Thanks,
Guna
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Debug custom recipe configuration

2015-12-16 Thread Srinivasan Srivatsan
Hi,

I am working with Yocto and Bitbake to add a recipe which executes a python
script for configuration.

Am currently using the "*bitbake  -c configure*" to configure
the recipe. There is a configuration issue which am looking into for which
I need to add pdb.set_trace() when the configuration is run through
bitbake. I ran the python script configuration locally without using
bitbake, and it seems to work. If I add set_trace(), I see that the bitbake
program bypasses the pdb prompt during the run. Is there a way to have the
bitbake stop at that point in the program and give me access to the pdb
prompt ? Any other alternative way to debug this issue is appreciated.

Regards
Srinivasan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto