[yocto] (no subject)

[Stephen K Jolley]

All,



The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means
people can find them. They're being listed on the triage page under the
appropriate heading:



https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs



The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.



Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 309
unassigned or newcomer bugs.



We're hoping people may be able to spare some time now and again to help
out with these.  Bugs are split into two types, "true bugs" where things
don't work as they should and "enhancements" which are features we'd want
to add to the system.  There are also roughly four different "priority"
classes right now, “2.8”, “2.9’, "2.99" and "Future", the more
pressing/urgent issues being in "2.8" and then “2.9”.



Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com)
an e-mail with the bug number you would like and I will assign it to you
(please make sure you have a Bugzilla account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

-- 

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

*7867 SW Bayberry Dr., Beaverton, OR 97007*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[B, Karthik]

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

Re: [yocto] (no subject)

[Scott Rifenbark]

Hi,

Have you tried adding the feature through MACHINE_FEATURES variable? (
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#ref-features-machine
and
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#var-MACHINE_FEATURES
).

A developer can probably provide more detailed information Antonio.

Thanks,
Scott

On Tue, Jan 29, 2019 at 8:12 AM Antonio Santagiuliana <
santantonios...@gmail.com> wrote:

> Hi,
> I am missing the steps required to add to an image the support for an RTC
> plugged in to I2C1 interface, with autostart.
> is there a page with instructions ?
> thank you
> --
> ___
> 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] (no subject)

[Antonio Santagiuliana]

Hi,
I am missing the steps required to add to an image the support for an RTC
plugged in to I2C1 interface, with autostart.
is there a page with instructions ?
thank you
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Satya Sampangi]

Dear All,

How to run the task in the recipe file present in the custom layer,
*which executes all packages*, bypassing the task present in base
layers?

Thanks & Regards,

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

[yocto] (no subject)

[nishant poorswani]

Hi. I'm looking to write a recipe which installs the wheel file directly.
Any idea how to go about it.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Rahul jangra]

Hi team
I am facing the issue when creat deb base core-image-full-cmdline he
is getting this error but when I switch to rpm easily to built.
kindly help me.

 Executing 'cd /home/nsspl/rpi/build/tmp/deploy/deb/all;
PSEUDO_UNLOAD=1
/home/nsspl/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive
packages . > Packages;/home/nsspl/rpi/build/tmp/hosttools/gzip -fcn
Packages > Packages.gz;PSEUDO_UNLOAD=1
/home/nsspl/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive
release . >> Release' ...
NOTE: Executing 'cd
/home/nsspl/rpi/build/tmp/deploy/deb/cortexa7hf-neon-vfpv4;
PSEUDO_UNLOAD=1
/home/nsspl/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive
packages . > Packages;/home/nsspl/rpi/build/tmp/hosttools/gzip -fcn
Packages > Packages.gz;PSEUDO_UNLOAD=1
/home/nsspl/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive
release . >> Release' ...
NOTE: Executing 'cd /home/nsspl/rpi/build/tmp/deploy/deb/raspberrypi3;
PSEUDO_UNLOAD=1
/home/nsspl/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive
packages . > Packages;/home/nsspl/rpi/build/tmp/hosttools/gzip -fcn
Packages > Packages.gz;PSEUDO_UNLOAD=1
/home/nsspl/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive
release . >> Release' ...
NOTE: Installing the following packages: locale-base-en-us locale-base-en-gb
NOTE: Installing the following packages: dpkg hello-mender
psplash-raspberrypi packagegroup-core-full-cmdline apt run-postinsts
mender packagegroup-core-boot packagegroup-core-ssh-openssh
kernel-devicetree shadow kernel-image-4.14.37 base-passwd
ERROR: Unable to install packages. Command
'/home/nsspl/rpi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-full-cmdline/1.0-r0/recipe-sysroot-native/usr/bin/apt-get
 install --force-yes --allow-unauthenticated dpkg hello-mender
psplash-raspberrypi packagegroup-core-full-cmdline apt run-postinsts
mender packagegroup-core-boot packagegroup-core-ssh-openssh
kernel-devicetree shadow kernel-image-4.14.37 base-passwd' returned
100:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 packagegroup-core-full-cmdline : Depends:
packagegroup-core-full-cmdline-initscripts but it is not going to be
installed
E: Unable to correct problems, you have held broken packages.

Regards

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

Re: [yocto] (no subject)

[Андрей Кононов]

you right, when i take qt5 from morty branch everything builded ok

>Вторник, 30 мая 2017, 22:02 +03:00 от Petter Mabäcker < pet...@technux.se >:
>
>Hi,
>After a quick look, it seems like the problem is related to the Upgrade to Qt 
>5.8 that was done in pyro.
>commit: 333949a Upgrade to Qt 5.8 (in meta-qt5)
>The above mentioned commit causes 
>'./dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase/0014-Add-IMX-GPU-support.patch'
> (in meta-freescale) to fail. So this patch needs to be updated to match the 
>Qt 5.8 changes (that affects qmake.conf).
>BR Petter
> 
>Petter Mabäcker

Technux 
>www.technux.se
>
>2017-05-30 07:19 skrev Андрей Кононов:
>>i'm trying to build
>>bitbake fsl-image-multimedia-full -k
>>using  pyro repository and my image include QT5 library, but get error. The 
>>same configuration on  morty builded without errors
>>Parsing recipes: 100% 
>>||
>> Time: 0:19:36
>>Parsing of 2258 .bb files complete (0 cached, 2258 parsed). 3050 targets, 506 
>>skipped, 0 masked, 0 errors.
>>NOTE: Resolving any missing task queue dependencies
>>Build Configuration:
>>BB_VERSION = "1.34.0"
>>BUILD_SYS = "x86_64-linux"
>>NATIVELSBSTRING = "linuxmint-18.1"
>>TARGET_SYS = "arm-poky-linux-gnueabi"
>>MACHINE = "imx6qpsabreauto"
>>DISTRO = "poky"
>>DISTRO_VERSION = "2.3"
>>TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
>>TARGET_FPU = "hard"
>>meta 
>>meta-poky = "HEAD:31389f8b0088a8a83aa5e50f11359b39934e4640"
>>meta-oe 
>>meta-gnome 
>>meta-multimedia = "HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
>>meta-freescale = "HEAD:a65d13c315db447adda68b47faeb4c0afd0655b8"
>>meta-freescale-3rdparty = "HEAD:1f37698ac62945b6531a316ec1232af23cc6c050"
>>meta-freescale-distro = "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390"
>>meta-qt5 = "master:6605c48f3a900da26425ef31d83eb1c95d551531"
>>meta-ruby 
>>meta-networking 
>>meta-python 
>>meta-filesystems = "HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
>>Initialising tasks: 100% 
>>|#|
>> Time: 0:02:40
>>NOTE: Executing SetScene Tasks
>>NOTE: Executing RunQueue Tasks
>>ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Command Error: 'quilt 
>>--quiltrc 
>>/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/recipe-sysroot-native/etc/quiltrc
>> push' exited with 0 Output:
>>Applying patch 0014-Add-IMX-GPU-support.patch
>>patching file mkspecs/linux-oe-g++/qmake.conf
>>Hunk #1 FAILED at 39.
>>1 out of 1 hunk FAILED -- rejects in file mkspecs/linux-oe-g++/qmake.conf
>>Patch 0014-Add-IMX-GPU-support.patch does not apply (enforce with -f)
>>ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Function failed: 
>>patch_do_patch
>>ERROR: Logfile of failure stored in: 
>>/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/temp/log.do_patch.8895
>>ERROR: Task 
>>(/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch)
>> failed with exit code '1'
>>WARNING: ttf-arphic-uming-20080216-r6 do_populate_lic: ttf-arphic-uming: No 
>>generic license file exists for: Arphic-Public-License in any provider
>>NOTE: Tasks Summary: Attempted 5116 tasks of which 6 didn't need to be rerun 
>>and 1 failed.
>>Summary: 1 task failed:
>>/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch
>>Summary: There were 2 WARNING messages shown.
>>Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>>
>>-- 
>>Андрей Кононов
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] (no subject)

[Petter Mabäcker]

 

Hi, 

After a quick look, it seems like the problem is related to
the Upgrade to Qt 5.8 that was done in pyro. 

commit: 333949a Upgrade
to Qt 5.8 (in meta-qt5) 

The above mentioned commit causes
'./dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase/0014-Add-IMX-GPU-support.patch'
(in meta-freescale) to fail. So this patch needs to be updated to match
the Qt 5.8 changes (that affects qmake.conf). 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se

2017-05-30 07:19
skrev Андрей Кононов: 

> i'm trying to build
> bitbake
fsl-image-multimedia-full -k
> using PYRO repository and my image
include QT5 library, but get error. The same configuration on MORTY
builded without errors 
> 
> Parsing recipes: 100%
||
Time: 0:19:36
> Parsing of 2258 .bb files complete (0 cached, 2258
parsed). 3050 targets, 506 skipped, 0 masked, 0 errors.
> NOTE:
Resolving any missing task queue dependencies 
> 
> Build
Configuration:
> BB_VERSION = "1.34.0"
> BUILD_SYS = "x86_64-linux"
>
NATIVELSBSTRING = "linuxmint-18.1"
> TARGET_SYS =
"arm-poky-linux-gnueabi"
> MACHINE = "imx6qpsabreauto"
> DISTRO =
"poky"
> DISTRO_VERSION = "2.3"
> TUNE_FEATURES = "arm armv7a vfp thumb
neon callconvention-hard cortexa9"
> TARGET_FPU = "hard"
> meta 
>
meta-poky = "HEAD:31389f8b0088a8a83aa5e50f11359b39934e4640"
> meta-oe 
>
meta-gnome 
> meta-multimedia =
"HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
> meta-freescale =
"HEAD:a65d13c315db447adda68b47faeb4c0afd0655b8"
>
meta-freescale-3rdparty =
"HEAD:1f37698ac62945b6531a316ec1232af23cc6c050"
> meta-freescale-distro
= "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390"
> meta-qt5 =
"master:6605c48f3a900da26425ef31d83eb1c95d551531"
> meta-ruby 
>
meta-networking 
> meta-python 
> meta-filesystems =
"HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7" 
> 
> Initialising
tasks: 100%
|#|
Time: 0:02:40
> NOTE: Executing SetScene Tasks
> NOTE: Executing
RunQueue Tasks
> ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch:
Command Error: 'quilt --quiltrc
/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0 Output:
> Applying patch
0014-Add-IMX-GPU-support.patch
> patching file
mkspecs/linux-oe-g++/qmake.conf
> Hunk #1 FAILED at 39.
> 1 out of 1
hunk FAILED -- rejects in file mkspecs/linux-oe-g++/qmake.conf
> Patch
0014-Add-IMX-GPU-support.patch does not apply (enforce with -f)
> ERROR:
qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Function failed:
patch_do_patch
> ERROR: Logfile of failure stored in:
/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/temp/log.do_patch.8895
>
ERROR: Task
(/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch)
failed with exit code '1'
> WARNING: ttf-arphic-uming-20080216-r6
do_populate_lic: ttf-arphic-uming: No generic license file exists for:
Arphic-Public-License in any provider
> NOTE: Tasks Summary: Attempted
5116 tasks of which 6 didn't need to be rerun and 1 failed. 
> 
>
Summary: 1 task failed:
>
/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch
>
Summary: There were 2 WARNING messages shown.
> Summary: There were 2
ERROR messages shown, returning a non-zero exit code. 
> 
> -- 
> Андрей
Кононов
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Андрей Кононов]

i'm trying to build
bitbake fsl-image-multimedia-full -k
using  pyro repository and my image include QT5 library, but get error. The 
same configuration on  morty builded without errors
Parsing recipes: 100% 
||
 Time: 0:19:36
Parsing of 2258 .bb files complete (0 cached, 2258 parsed). 3050 targets, 506 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.34.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "linuxmint-18.1"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "imx6qpsabreauto"
DISTRO = "poky"
DISTRO_VERSION = "2.3"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU = "hard"
meta 
meta-poky = "HEAD:31389f8b0088a8a83aa5e50f11359b39934e4640"
meta-oe 
meta-gnome 
meta-multimedia = "HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
meta-freescale = "HEAD:a65d13c315db447adda68b47faeb4c0afd0655b8"
meta-freescale-3rdparty = "HEAD:1f37698ac62945b6531a316ec1232af23cc6c050"
meta-freescale-distro = "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390"
meta-qt5 = "master:6605c48f3a900da26425ef31d83eb1c95d551531"
meta-ruby 
meta-networking 
meta-python 
meta-filesystems = "HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
Initialising tasks: 100% 
|#|
 Time: 0:02:40
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Command Error: 'quilt 
--quiltrc 
/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/recipe-sysroot-native/etc/quiltrc
 push' exited with 0 Output:
Applying patch 0014-Add-IMX-GPU-support.patch
patching file mkspecs/linux-oe-g++/qmake.conf
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- rejects in file mkspecs/linux-oe-g++/qmake.conf
Patch 0014-Add-IMX-GPU-support.patch does not apply (enforce with -f)
ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Function failed: 
patch_do_patch
ERROR: Logfile of failure stored in: 
/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/temp/log.do_patch.8895
ERROR: Task 
(/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch)
 failed with exit code '1'
WARNING: ttf-arphic-uming-20080216-r6 do_populate_lic: ttf-arphic-uming: No 
generic license file exists for: Arphic-Public-License in any provider
NOTE: Tasks Summary: Attempted 5116 tasks of which 6 didn't need to be rerun 
and 1 failed.
Summary: 1 task failed:
/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

-- 
Андрей Кононов-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Suneetha Lakshmi G]

suneeth...@tataelxsi.co.in


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

[yocto] (no subject)

[Paulo Neves]

Hello Yocto list from time to time my builds are getting this error
and I can't understand why is this happening. Every package is in
local IO, only the sstate cache i think is in an NFS mount.

Can you hint me at why this error could come up in yocto do_rootfs?

ERROR: lfs-release-full-x86-64-build-pc-linux-gnu-1.0-r0 do_rootfs:
Unable to install packages. Command
'/workspace/builds/yoctobuild/tmp/sysroots/x86_64-linux/usr/bin/opkg
--volatile-cache -f
/workspace/builds/yoctobuild/tmp/work/x86_64_build_pc_linux_gnu-poky-linux/lfs-release-full-x86-64-build-pc-linux-gnu/1.0-r0/opkg.conf
-o 
/workspace/builds/yoctobuild/tmp/work/x86_64_build_pc_linux_gnu-poky-linux/lfs-release-full-x86-64-build-pc-linux-gnu/1.0-r0/rootfs
 --force_postinstall --prefer-arch-to-version   install run-postinsts
fullsysroot all-vcf-wmp' returned 255:
Collected errors:
 * opkg_install_pkg: Failed to download fullsysroot. Perhaps you need
to run 'opkg update'?
 * opkg_install: Cannot install package fullsysroot.
 Installing run-postinsts (1.0-r0) on root.



Best regards
Paulo Neves
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Rohit Jindal]

Please help.me adding support for JIT to openjdk 8 in arm architecture.

Immediate help is highly appreciated.

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

Re: [yocto] (no subject)

[Khem Raj]

On Mon, Jul 13, 2015 at 10:56 PM, Alvaro Martinez Tovar
alvaromartinezto...@yahoo.es wrote:
 Dear all,
 I am working with Qt5.5.0 and QtCreator 3.4.2 open source. On the hardware
 side I work with a i.MX6 sabre platform for smart devices.
 As a first aproach, after having created the image fsl-image-qt5 correctly
 (I think), I would like to run different examples by cross compiling and
 executing them on the SABRE platform. On my PC I run Ubuntu 14.04 LTS.
 When I compile all the examples to run on the Ubuntu PC, they all work
 properly (bluetooth, qtquick ...)
 However, when I try to cross-compile and run them on the SABRE platform, I
 get execution errors with some of them.
 When I try to run a bluetooth scanner, I get:
 ./btscanner: error while loading shared libraries: libQt5Bluetooth.so.5:
 cannot open shared object file: No such file or directory
 When I try to run a Qtquick example (dasboard), I get:
 Qt Warning: Could not find a location of the system's Compose files.
 Consider setting the QTCOMPOSE environment variable.
 Qt Warning: Could not find a location of the system's Compose files.
 Consider setting the QTCOMPOSE environment variable.
 QQmlApplicationEngine failed to load component
 qrc:/qml/dashboard.qml:45 module QtQuick.Extras is not installed
 qrc:/qml/dashboard.qml:43 module QtQuick.Controls is not installed
 qrc:/qml/dashboard.qml:44 module QtQuick.Controls.Styles is not installed
 qrc:/qml/dashboard.qml:45 module QtQuick.Extras is not installed
 qrc:/qml/dashboard.qml:43 module QtQuick.Controls is not installed
 qrc:/qml/dashboard.qml:44 module QtQuick.Controls.Styles is not installed
 qrc:/qml/dashboard.qml:45 module QtQuick.Extras is not installed
 qrc:/qml/dashboard.qml:43 module QtQuick.Controls is not installed
 qrc:/qml/dashboard.qml:44 module QtQuick.Controls.Styles is not installed

 Can you please give me any advice on what to do? I am stuck at this point.


you should use same version of qt that you are getting for meta-qt5
and 5.5 is not yet in there
the latest on master is 5.4

 thank you in advance!
 Regards

 --
 ___
 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] (no subject)

[Edward Vidal]

Hello All,Thanks to Ross Burton 
see the files https://github.com/develone/raspberrypi2_yocto.git

in recipe_myhdl folder.

Now have an rpm to install myhdl on a yocto build.
let me know if you have any questions.
  Edward Vidal Jr.
e-mail devel...@sbcglobal.net
915-595-1613-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Alvaro Martinez Tovar]

Dear all,I am working with Qt5.5.0 and QtCreator 3.4.2 open source. On the 
hardware side I work with a i.MX6 sabre platform for smart devices.As a first 
aproach, after having created the image fsl-image-qt5 correctly (I think), I 
would like to run different examples by cross compiling and executing them on 
the SABRE platform. On my PC I run Ubuntu 14.04 LTS.When I compile all the 
examples to run on the Ubuntu PC, they all work properly (bluetooth, qtquick 
...)However, when I try to cross-compile and run them on the SABRE platform, I 
get execution errors with some of them.When I try to run a bluetooth scanner, I 
get:./btscanner: error while loading shared libraries: libQt5Bluetooth.so.5: 
cannot open shared object file: No such file or directory When I try to run a 
Qtquick example (dasboard), I get:Qt Warning: Could not find a location of the 
system's Compose files. Consider setting the QTCOMPOSE environment variable.Qt 
Warning: Could not find a location of the system's Compose files. Consider 
setting the QTCOMPOSE environment variable.QQmlApplicationEngine failed to load 
componentqrc:/qml/dashboard.qml:45 module QtQuick.Extras is not 
installedqrc:/qml/dashboard.qml:43 module QtQuick.Controls is not 
installedqrc:/qml/dashboard.qml:44 module QtQuick.Controls.Styles is not 
installedqrc:/qml/dashboard.qml:45 module QtQuick.Extras is not 
installedqrc:/qml/dashboard.qml:43 module QtQuick.Controls is not 
installedqrc:/qml/dashboard.qml:44 module QtQuick.Controls.Styles is not 
installedqrc:/qml/dashboard.qml:45 module QtQuick.Extras is not 
installedqrc:/qml/dashboard.qml:43 module QtQuick.Controls is not 
installedqrc:/qml/dashboard.qml:44 module QtQuick.Controls.Styles is not 
installed Can you please give me any advice on what to do? I am stuck at this 
point. thank you in advance!Regards-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Rickard Bremer]

Hello,

Been encountering a new error during the day. The exact same configure did 
build one time before, but on the second build it started to crash.

Best Regards
Rickard

---
jenkins@yocto:~/workspace/thesis-build-yocto/build$ bitbake core-image-minimal
Loading cache: 100% 
|##| ETA:  
00:00:00
Loaded 2134 entries from dependency cache.
Parsing recipes: 100% 
|| Time: 
00:00:00
Parsing of 1651 .bb files complete (1649 cached, 2 parsed). 2135 targets, 49 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= 1.24.0
BUILD_SYS = x86_64-linux
NATIVELSBSTRING   = Ubuntu-14.04
TARGET_SYS= x86_64-poky-linux
MACHINE   = congatec-qa3-64
DISTRO= poky
DISTRO_VERSION= 1.7.1
TUNE_FEATURES = m64 corei7
TARGET_FPU= 
meta
meta-yocto
meta-yocto-bsp= dizzy:6e9632e9798d78587c9317554c5547ab3b53837c
meta-intel
meta-valleyisland
meta-tlk  = dizzy:c90fb613745cb31694144f6d2c240b4dda32ee58
meta-congatec-x86 = dizzy:095f6b1340c57252bcb1a42ab352dc2b4886b36e
meta-rb   = dizzy:6e9632e9798d78587c9317554c5547ab3b53837c
meta-oe
meta-python
meta-networking   = master:bb177c85a25d2b75583abe218396520c375f8f18

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Index creation command 
'/var/lib/jenkins/workspace/thesis-build-yocto/build/tmp/sysroots/x86_64-linux/usr/bin/createrepo
 --update -q 
/var/lib/jenkins/workspace/thesis-build-yocto/build/tmp/deploy/rpm/corei7_64' 
failed with return code 137:
Killed

ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/var/lib/jenkins/workspace/thesis-build-yocto/build/tmp/work/congatec_qa3_64-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.26390
ERROR: Task 7 
(/var/lib/jenkins/workspace/thesis-build-yocto/meta/recipes-core/images/core-image-minimal.bb,
 do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2453 tasks of which 2452 didn't need to be rerun 
and 1 failed.
No currently running tasks (1867 of 2455)

Summary: 1 task failed:
  
/var/lib/jenkins/workspace/thesis-build-yocto/meta/recipes-core/images/core-image-minimal.bb,
 do_rootfs
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


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

[yocto] (no subject)

[Raghavendra Kakarla]

Hi Yocto Team,


Now I am working on the yocto sdk generation.


I am generated the yocto SDK using the yocto sdk script bitbake 
core-image-minimal -c populate_sdk command. With this command I am able to 
generte the installation script file and .manifest file.


I run the installation script file. After running installation script file it 
propts that following message:


Extracting SDK...done
Setting it up...done
SDK has been successfully set up and is ready to be used.



After this i run the . /opt/poky/1.7/environment-setup-mips32rel-poky-linux 
and echo $PATH i got the correct path.


After this i built wrote a small example and try to build with the sdk 
generated toolchain by running following command:


mipsel-poky-linux-gcc test.c


but i got the following errors:

**

/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find crt1.o: No such file or directory
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find crti.o: No such file or directory
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find crtbegin.o: No such file or directory
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find -lgcc
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find -lgcc_s
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find -lc
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find -lgcc
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find -lgcc_s
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find crtend.o: No such file or directory
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld:
 cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status


***

Please help me to resolving this issue.


Thanks in advance.


Cheers,


Raghavendra Kakarla.


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

[yocto] (no subject)

[Debasmita Lohar]

Hello,
My yocto version is: 3.10.11-yocto-standard. I was trying to install git
1.8.1.2. While making git it is showing the following error:
Writing MYMETA.yml
GEN git-add--interactive
make[2]: *** No rule to make target `/usr/lib/perl/5.14.3/CORE/config.h',
needed by `perl.mak'.  Stop.
make[1]: *** [instlibdir] Error 2
make: *** [git-add--interactive] Error 2
I am unable to fix this. Any help regarding this will be highly appreciated.
Thank you.
Debasmita Lohar
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Fabrício Lélis]

Hi,

I have this problem:

Assuming /home/fabricio/qemuarm-sato is an nfs rootfs
Error: conflicting FSTYPE types [/home/fabricio/qemuarm-sato] and nfs

Anybody can help me?

Thanks in advance!

-- 
Fabrício Gutemberg Lélis de Melo
Master in Computer Science at UFCG
http://fabriciolelis.googlepages.com/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Modemtec Modemtec]

Hello,

I ran into an error during do_populate_sdk in meta-toolchain for machine
socfpga_cyclone5:

ERROR: packagegroup-cross-canadian-socfpga_cyclone5 not found in the base
feeds (i686-nativesdk noarch any all).
List packages for example:
binutils-cross-canadian-arm-2.24-r0@i686_nativesdk
binutils-cross-canadian-arm-dbg-2.24-r0@i686_nativesdk etc
ERROR: Function failed: do_populate_sdk
ERROR: Logfile of failure stored in:
/modemtec/linux/yocto-daisy/build-socfpga_cyclone5/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/meta-toolchain/1.0-r7/temp/log.do_populate_sdk.12635
ERROR: Task 7 (/modemtec/linux/yocto-daisy/meta/recipes-core/meta/
meta-toolchain.bb, do_populate_sdk) failed with exit code '1'

I tried to find an answer, but without success. I tried to compile
nativesdk-packagegroup-sdk-host and it was already compiled.

I was able to compile u-boot, kernel, kernel modules, dtb, rootfs and
everythink works quite well, but now I'm stuck with this and have no clue
how to solve this. If anyone knows how to make it working I would be very
glad.

Thank you very much

Lesek Franek ModemTec s.r.o.

Build Configuration:
BB_VERSION= 1.22.0
BUILD_SYS = i686-linux
NATIVELSBSTRING   = LinuxMint-17
TARGET_SYS= arm-poky-linux-gnueabi
MACHINE   = socfpga_cyclone5
DISTRO= poky
DISTRO_VERSION= 1.6.1
TUNE_FEATURES = armv7a vfp neon
TARGET_FPU= vfp-neon
meta
meta-yocto
meta-yocto-bsp= daisy:810dd79720d607f1a31e73ff5f0862928fe06eb2
meta-altera   =
angstrom-v2014.06-yocto1.6:cbf58fc9d7df88fcb6ec6db9aa109533bf180d5e
meta-socfpga_altera = master:1bd7bca0877adcced73acfb4c4522b02c9244917
meta-modemtec = master:e7316808ddc034bc3dcdedc8c1e0d2ab5ce3af22
meta-oe
meta-webserver= daisy:dca466c074c9a35bc0133e7e0d65cca0731e2acf
meta-qt5  = daisy:0137274b13a568718e441f8f1c611a653db9f2f7
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Kashyap Gada]

Hello Community,
This is my first question please excuse if I'm making a silly mistake. I am
just starting learning the yocto project to develop custom linux os. I was
following the few commands to download and setup poky on my build system
from the quick start guide at .

$ git clone http://git.yoctoproject.org/git/poky
 $ cd poky
 $ git checkout -b daisy origin/daisy
 $ source oe-init-build-env

Executing the last line gives me the following issue


kashyap@Kashyap-VAIO:/media/kashyap/3E0800DC08009555/yocto/poky$ ls

 bitbakemeta-selftest   oe-init-build-env scripts

 documentation  meta-skeleton   oe-init-build-env-memres

 LICENSEmeta-yocto  README

 meta   meta-yocto-bsp  README.hardware

 kashyap@Kashyap-VAIO:/media/kashyap/3E0800DC08009555/yocto/poky$ source
 oe-init-build-env

 bash:
 /media/kashyap/3E0800DC08009555/yocto/poky/scripts/oe-setup-builddir:
 Permission denied

 kashyap@Kashyap-VAIO:/media/kashyap/3E0800DC08009555/yocto/poky$



I tried searching over the internet about the possible issues but couldn't
figure out the problem here.
Anyone please help.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] (no subject)

[Flanagan, Elizabeth]

All,

With the failures we saw last night on the dylan point release, we're going to
ask folks to switch QA efforts to the dylan point release which should be
finished building shortly. The build appliance will be built out of
band in order to fix
some autobuilder build issues on it and then added to the rc2 area.

http://autobuilder.yoctoproject.org/pub/releases/dora-10.0.1.rc2

bitbake 1484905373ad717cedcaef37a0addde034ebdc60
eclipse-poky-juno 2fa1c58940141a3c547c8790b8a6832167e8eb66
eclipse-poky-kepler ad74249895f882a8f00bdeef7a0f7c18998cc43e
meta-fsl-arm c7cc5d5f451c9d12df9f11314f4a58ecc347b1f5
meta-fsl-ppc b5732aeadc9eb0de933f52d0949412e12f8486bd
meta-intel c86e39dd06571458c7dee6cf289d5b470c98f4bd
meta-minnow edf75553643face7a0dd5b16085d59a90eb4af8d
meta-qt3 4772424ab69908d4e3b9d6d4717ca889468e6acd
oecore d68c267f3387d7fe221d3c5653a66db8b1f78fd8
poky 7a0033cc4e1f590c5a936671f351a1b251e16726

-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] (no subject)

[Jack]

Anders Darander anders@... writes:

 
 
 Jack jackrubby2010@... wrote:
 Anders Darander anders at ... writes:
 
 Thanks Anders,
 
 But I have this problem not only for GPIOs, but also for other
 registers.
 
 Well, my comment about dereferencing physical addresses using *-only,
wasn't restricted to GPIO's only.
 It was regarding physical addresses in general... 
 
 Once again, I've not used this platform, this I'm not able to be too
specific. 
 
 For example, I tried to change DTW bits of PROCTL register in eSDH but
 I get
 Kernel access of bad area again. My simple code is here :
 
 int init_module(void)
 {
  
  // e500 Core View To Power Architecture CCSR: 0x0_FF70_
  
  volatile uint32_t * eSDH_PROCTL = (volatile uint32_t *)(0xFF72E028);
 
  *(eSDH_PROCTL) = 0x0002;
 
 I think that you should try to look at some code from the kernel that
accesses registers on your platform. For
 instance
http://lxr.free-electrons.com/source/sound/soc/fsl/p1022_ds.c?v=3.4 (this is
just a
 randomly chosen file that relates to P1022. 
 
 Have a look at how guts_phys is declared, as well as how guts later on is
both declared and initialized from
 guts_phys. 
 When the registers are actually read / written, this driver uses the
clrsetbits_XX. These functions then
 implements the actual reading and writing of the registers. 
 
 (Note again, I've just looked at this file and p1022 for a couple of
minutes). 
 
 Cheers, 
 Anders 
 

Thank you very much Anders for useful comments and replies,

I saw the link that you mentioned and I could write in pmuxcr register. So
writing to register problem almost has solved. But I have some problems yet.

I read fsl_guts.h in powerpc architecture and saw Global Utility Registers
like gpiocr as GPIO Control Register, gpindr as General-Purpose Input Data
Register and gpoutdr as General-Purpose Output Data Register. But in GPIO
registers in p1022 reference manual we have GPDIR register to set specify
GPIO direction and GPDAT register for GPIO data register. We have only one
register for data but fsl_guts.h defines two register for input an output data.
 

Does gpiocr work as GPDIR?

For GPDAT, which of the two registers I should use? gpindr or gpoutdr?

 
Thanks,

Best regards. 



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

Re: [yocto] (no subject)

[Anders Darander]

Jack jackrubby2...@gmail.com wrote:
Anders Darander anders@... writes:

Thanks Anders,

But I have this problem not only for GPIOs, but also for other
registers.

Well, my comment about dereferencing physical addresses using *-only, wasn't 
restricted to GPIO's only. It was regarding physical addresses in general... 

Once again, I've not used this platform, this I'm not able to be too specific. 

For example, I tried to change DTW bits of PROCTL register in eSDH but
I get
Kernel access of bad area again. My simple code is here :

int init_module(void)
{
   
   // e500 Core View To Power Architecture CCSR: 0x0_FF70_
   
   volatile uint32_t * eSDH_PROCTL = (volatile uint32_t *)(0xFF72E028);

   *(eSDH_PROCTL) = 0x0002;

I think that you should try to look at some code from the kernel that accesses 
registers on your platform. For instance 
http://lxr.free-electrons.com/source/sound/soc/fsl/p1022_ds.c?v=3.4 (this is 
just a randomly chosen file that relates to P1022. 

Have a look at how guts_phys is declared, as well as how guts later on is both 
declared and initialized from guts_phys. 
When the registers are actually read / written, this driver uses the 
clrsetbits_XX. These functions then implements the actual reading and writing 
of the registers. 

(Note again, I've just looked at this file and p1022 for a couple of minutes). 

Cheers, 
Anders 

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

Re: [yocto] (no subject)

[Jack]

Anders Darander anders@... writes:

 
 
 Jack jackrubby2010 at gmail.com wrote:
 Hi,
 I want to set/reset GPIO registers in freescale p1022 processor. I saw
 a
 hello-mod kernel module in yocto and I added it to my image and it
 worked.
 According to hello-mod kernel module, I created GPIO module like
 hello-mod.
 But it GPIO module failed when I run it in kernel level. I checked
 several
 times addresses of registers and it seems accurate. 
 My code is here :
 
 
 #include linux/module.h
 
 int init_module(void)
 {
  volatile uint32_t * Guts_Pmuxcr;
  volatile uint32_t * Gpio3_Gpdir;
  volatile uint32_t * Gpio3_Gpdat;
  
  // e500 Core View To Power Architecture CCSR: 0x0_FF70_
 
 // GUTS_PMUXCR:Alternate Function Signal Multiplex Control Register
  Guts_Pmuxcr = (volatile uint32_t *)(0xFF7E0060);
   
 // GPIO3_GPDIR: GPIO3 direction register
  Gpio3_Gpdir = (volatile uint32_t *)(0xFF70F200);
 
 // GPIO3_GPDAT: GPIO3 data register
  Gpio3_Gpdat = (volatile uint32_t *)(0xFF70F208); 
 
 You should generally a of trying to dereference physical addresses, or you
should explicitly declare them
 as such. 
 
 If suggest looking for some info on using GPIO on your CPU. Unfortunately,
I've not used the p1022, so I can't
 really help you. 
 
 http://linuxppc.10917.n7.nabble.com/Re-GPIO-IRQ-on-P1022-td59356.html
discusses some IRQ
 issues, though you should be able to use the codes as an example of the
GPIO framework and how to use it. 
 
 Cheers, 
 Anders 
 
 
  // Enable GPIO3[10]: IRQ_DEBUG1_GPIO FIELD [BIT 26] set to 1
  *(Guts_Pmuxcr) = 0x0010;
 
 
 
  // Set Direction for GPIO3[10] to Output: FIELD DR10 [BIT 10] set to
 '1'
  *(Gpio3_Gpdir) = 0x0020;
  
   
  // Set GPIO3[10] to '0': FIELD D10 [BIT 10] set to '0'
  *(Gpio3_Gpdat) = 0x;
  
  printk(Hello World!\n);
  return 0;
 }
 
 void cleanup_module(void)
 {
  printk(Goodbye Cruel World!\n);
 }
 
 MODULE_LICENSE(GPL);
 
 
 When I write insmod GPIO.ko in the terminal I get error these errors:
 
 Unable to handle kernel paging request for data at address 0xff7e0060
 faulting instruction address: 0xf107e05c
 Oops: Kernel access of bad area, sig: 11 [#1]
 ..
 .
 
 
 How can I solve this problem?
 
 
 ___
 yocto mailing list
 yocto at yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto
 

Thanks Anders,

But I have this problem not only for GPIOs, but also for other registers.
For example, I tried to change DTW bits of PROCTL register in eSDH but I get
Kernel access of bad area again. My simple code is here :

#include linux/module.h

int init_module(void)
{

// e500 Core View To Power Architecture CCSR: 0x0_FF70_

volatile uint32_t * eSDH_PROCTL = (volatile uint32_t *)(0xFF72E028);

*(eSDH_PROCTL) = 0x0002;

return 0;
}

void cleanup_module(void)
{
printk(Goodbye Cruel World!\n);
}

MODULE_LICENSE(GPL);

What should I do? Can you help me?




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

[yocto] (no subject)

[arun kumar]

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

[yocto] (no subject)

[Florin Cristian Dan]

Hello,
Ok, so in the last days, i've managest to bake my own sato-emenlow image,
and runed it on my machine wich is a PEB2739 (Intel Atom Z510 based).I'm
intrested now in developing some industrial applications, like different
types of masurement gauges.  Now i wonder if yocto project has suport for
java and how its done, as far as i am, i'have read that there would some
meta-java layer, but i'm not sure what to do further, where to get it, and
how the development proces would go.
 Can someone please give me some advices.

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

[yocto] (no subject)

[Ilya Dmitrichenko]

Hi,

I'm getting this on Ubuntu 10.04:

 bitbake core-image-minimal
[224/1821]
Pseudo is not present but is required, building this first before the main
build
Parsing recipes: 100%
|##|
Time: 00:01:12
Parsing of 1262 .bb files complete (0 cached, 1262 parsed). 1605 targets,
64 skipped, 6 masked, 0 errors.

Build Configuration:
BB_VERSION= 1.16.0
TARGET_ARCH   = arm
TARGET_OS = linux-gnueabi
MACHINE   = beaglebone
DISTRO= poky
DISTRO_VERSION= 1.3+snapshot-2012
TUNE_FEATURES = armv7a vfp neon cortexa8
TARGET_FPU= vfp-neon
meta
meta-yocto= master:78983e939ab17f02f8911c8b0d0e326b419856b9
meta-oe   = master:ae2926ef202541014cde7c91a9ff75ed8b4eb390
meta-ti   = master:53dcf7977a86714cbd27f919a473dac8f6f16434
meta-yocto-bsp= master:78983e939ab17f02f8911c8b0d0e326b419856b9

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 56 tasks of which 0 didn't need to be rerun
and all succeeded.
Loading cache: 100%
||
ETA:  00:00:00
Loaded 1606 entries from dependency cache.

Build Configuration:
BB_VERSION= 1.16.0
TARGET_ARCH   = arm
TARGET_OS = linux-gnueabi
MACHINE   = beaglebone
DISTRO= poky
DISTRO_VERSION= 1.3+snapshot-2012
TUNE_FEATURES = armv7a vfp neon cortexa8
TARGET_FPU= vfp-neon
meta
meta-yocto= master:78983e939ab17f02f8911c8b0d0e326b419856b9
meta-oe   = master:ae2926ef202541014cde7c91a9ff75ed8b4eb390
meta-ti   = master:53dcf7977a86714cbd27f919a473dac8f6f16434
meta-yocto-bsp= master:78983e939ab17f02f8911c8b0d0e326b419856b9

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 63 tasks of which 42 didn't need to be rerun
and all succeeded.
Loading cache: 100%
||
ETA:  00:00:00
Loaded 1606 entries from dependency cache.

Build Configuration:

[173/1821]
BB_VERSION= 1.16.0
TARGET_ARCH   = arm
TARGET_OS = linux-gnueabi
MACHINE   = beaglebone
DISTRO= poky
DISTRO_VERSION= 1.3+snapshot-2012
TUNE_FEATURES = armv7a vfp neon cortexa8
TARGET_FPU= vfp-neon
meta
meta-yocto= master:78983e939ab17f02f8911c8b0d0e326b419856b9
meta-oe   = master:ae2926ef202541014cde7c91a9ff75ed8b4eb390
meta-ti   = master:53dcf7977a86714cbd27f919a473dac8f6f16434
meta-yocto-bsp= master:78983e939ab17f02f8911c8b0d0e326b419856b9

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: Unpack failure for URL: '
http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.5.0-0.tar.xz'.
Unpack command PATH=/home/ilya/oe/poky/sc
ripts/native-intercept:/home/ilya/oe/poky/scripts:/mnt/build/poky//tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-linux:/mnt/build/poky//tmp/sysroots/x86_64-linux/usr/bin:/mnt/bu
ild/poky//tmp/sysroots/x86_64-linux/usr/sbin:/mnt/build/poky//tmp/sysroots/x86_64-linux/usr/bin:/mnt/build/poky//tmp/sysroots/x86_64-linux/sbin:/mnt/build/poky//tmp/sysroots/x86_64-
linux//bin:/home/ilya/oe/poky/scripts:/home/ilya/oe/poky/bitbake/bin/:/etc/rbenv/shims:/usr/local/rbenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
xz -dc /home/ilya/oe/poky/build/downloads/kconfig-frontends-3.5.0-0.tar.xz
| tar x --no-same-owner -f - failed with return value 2
ERROR: Logfile of failure stored in:
/mnt/build/poky//tmp/work/x86_64-linux/kconfig-frontends-native-3.5.0-r1/temp/log.do_unpack.894
Log data follows:
| DEBUG: Executing python function do_unpack
| DEBUG: Executing python function base_do_unpack
| NOTE: Unpacking
/home/ilya/oe/poky/build/downloads/kconfig-frontends-3.5.0-0.tar.xz to
/mnt/build/poky/tmp/work/x86_64-linux/kconfig-frontends-native-3.5.0-r1/
| xz: error while loading shared libraries: liblzma.so.5: cannot open
shared object file: No such file or directory
| tar: This does not look like a tar archive
| tar: Exiting with failure status due to previous errors
| DEBUG: Python function base_do_unpack finished
| DEBUG: Python function do_unpack finished
| ERROR: Function failed: Unpack failure for URL: '
http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.5.0-0.tar.xz'.
Unpack 

[yocto] (no subject)

[Bruce Ashfield]

Tom/Darren/Saul,

Not sure who wants to proxy these into meta-intel for me, 
so I've copied you all. Now that the recipe renames for
linux-yocto in the main repos, meta-intel needs to be updated
as well.

Patch 2 is for meta-yocto with the same change.

These are the referenes that I found (hopefully I didn't 
miss any) and fixed to the new naming convention. 

Note: I can't push to meta-intel-contrib, so I'm just sending
this as a patch.

Cheers,

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

[yocto] (no subject)

[Liping Ke]

From: Liping Ke liping...@intel.com

Subject: [PATCH 1/1] Resend:[Image-Creator]Make bitbake server type 
configurable (xmlrpc, none)

Add -t options in bitbake for configuring server type.

Signed-off-by: Liping Ke liping...@intel.com
---
 bitbake/bin/bitbake |   22 +-
 1 files changed, 17 insertions(+), 5 deletions(-)

diff --git a/bitbake/bin/bitbake b/bitbake/bin/bitbake
index 6d05289..2c45224 100755
--- a/bitbake/bin/bitbake
+++ b/bitbake/bin/bitbake
@@ -39,8 +39,6 @@ import bb.msg
 from bb import cooker
 from bb import ui
 from bb import server
-from bb.server import none
-#from bb.server import xmlrpc
 
 __version__ = 1.11.0
 logger = logging.getLogger(BitBake)
@@ -71,7 +69,7 @@ def get_ui(config):
 return getattr(module, interface).main
 except AttributeError:
 sys.exit(FATAL: Invalid user interface '%s' specified.\n
- Valid interfaces: depexp, goggle, ncurses, knotty 
[default]. % interface)
+ Valid interfaces: depexp, goggle, ncurses, hob, knotty 
[default]. % interface)
 
 
 # Display bitbake/OE warnings via the BitBake.Warnings logger, ignoring 
others
@@ -161,6 +159,9 @@ Default BBFILES are the .bb files in the current 
directory.)
 parser.add_option(-u, --ui, help = userinterface to use,
action = store, dest = ui)
 
+parser.add_option(-t, --servertype, help = choose which server to 
user, none or xmlrpc,
+   action = store, dest = servertype)
+
 parser.add_option(, --revisions-changed, help = Set the exit code 
depending on whether upstream floating revisions have changed or not,
action = store_true, dest = revisions_changed, default = 
False)
 
@@ -175,8 +176,19 @@ Default BBFILES are the .bb files in the current 
directory.)
 loghandler = event.LogHandler()
 logger.addHandler(loghandler)
 
-#server = bb.server.xmlrpc
-server = bb.server.none
+# Server type could be xmlrpc or none currently, if nothing is specified,
+# default server would be none
+if configuration.servertype:
+server_type = configuration.servertype
+else:
+server_type = 'none'
+
+try:
+module = __import__(bb.server, fromlist = [server_type])
+server = getattr(module, server_type)
+except AttributeError:
+sys.exit(FATAL: Invalid server type '%s' specified.\n
+ Valid interfaces: xmlrpc [default]. % servertype)
 
 # Save a logfile for cooker into the current working directory. When the
 # server is daemonized this logfile will be truncated.
-- 
1.7.0.4

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