[yocto] Missing or unbuildable dependency chain

2017-03-16 Thread ravikiran j
Hi everybody, I am trying to change the packagegroup from packagegroup-core-base to packagegroup-core-extende in core-image-minimal-xfce recipe file in meta-xfce layer. But i am getting following errors. ERROR: Nothing RPROVIDES 'dnsmasq' (but /home/kamama-yocto/yocto/poky/meta-openembedded/meta

Re: [yocto] any YP machines or functionality that still require uImage creation?

2017-03-16 Thread Denys Dmytriyenko
On Thu, Mar 16, 2017 at 06:58:17AM -0400, Robert P. J. Day wrote: > > i just noticed that the machine config file for mpc8315e-rdb still > lists "uImage" as the default image type: > > KERNEL_IMAGETYPE = "uImage" > IMAGE_BOOT_FILES ?= "u-boot.bin uImage uImage-mpc8315erdb.dtb;dtb" > > is there

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Patrick Ohly
On Thu, 2017-03-16 at 10:48 +, Jack Mitchell wrote: > An issue with not having separate recipes is going to cause problems > with OTA package updates. I currently have a node package that I > maintain for a client and it's so big (excess of 30,000 files with all > deps) that we have to have

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Mark Hatle
On 3/16/17 5:35 AM, Alexander Kanavin wrote: > On 03/16/2017 11:30 AM, Paul Barker wrote: >> Staying with NPM as the example, say we have a tree of 1000 >> dependencies for a top-level application recipe. I understand that >> generating and then parsing 1000 recipes will bloat things and slow >> do

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Mark Hatle
On 3/16/17 4:30 AM, Paul Barker wrote: > On Thu, 16 Mar 2017 09:17:57 +0100 > Josef Holzmayr wrote: > >> I'll give it a shot and try to sum up the current state of affairs in >> this discussion. In accordance to the "Package managers all the way >> down"-presentation, I'm gonna use the term LPM

[yocto] Selinux recipes related error when executing bitbake

2017-03-16 Thread Pello Heriz
Hi all, I'm using Yocto master branch and I'm not able to compile a xen minimal image. I have experimented different errors, the last one is the next one: pello@pello-VirtualBox:/opt/yocto_GE/yocto_master_v2/poky/build$ bitbake xen-image-minimal Loading cache: 100% |#

[yocto] [qa-tools][PATCH] full-test-cycle-wrapper: Correct qemu-auto variables

2017-03-16 Thread jose . perez . carranza
From: Jose Perez Carranza Update variables for creating test runs for qemu ato component Signed-off-by: Jose Perez Carranza --- scripts/full-test-cycle-wrapper.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/full-test-cycle-wrapper.sh b/scripts/full-test-cyc

Re: [yocto] Selinux recipes related error when executing bitbake

2017-03-16 Thread Burton, Ross
On 16 March 2017 at 15:21, Mark Hatle wrote: > It looks like the upstream (oe-core) findutils is at a different version, > so the > bbappend has nothing to point to. > > We've not yet upreved selinux to current master. > > Patches welcome... > If you send a patch, please use a wildcard bbappend,

Re: [yocto] Selinux recipes related error when executing bitbake

2017-03-16 Thread Mark Hatle
On 3/16/17 3:31 AM, Pello Heriz wrote: > Hi all, > > I'm using Yocto master branch and I'm not able to compile a xen minimal > image. I > have experimented different errors, the last one is the next one: > > pello@pello-VirtualBox:/opt/yocto_GE/yocto_master_v2/poky/build$ bitbake > xen-image-min

[yocto] Random failure

2017-03-16 Thread Gary Thomas
NATIVELSBSTRING = "universal" TARGET_SYS= "arm-amltd-linux-gnueabi" MACHINE = "teton-p7621" DISTRO= "amltd" DISTRO_VERSION= "2.2+snapshot-20170316" TUNE_FEATURES

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Alexander Kanavin
By the way, Javascript developers do recognize that they have a framework problem. (source: http://thiswas.notinventedhe.re/on/2015-05-21 ) Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Alexander Kanavin
On 03/16/2017 12:48 PM, Jack Mitchell wrote: An issue with not having separate recipes is going to cause problems with OTA package updates. I currently have a node package that I maintain for a client and it's so big (excess of 30,000 files with all deps) that we have to have a special update pr

[yocto] [PATCH] meta-yocto-bsp: Remove superfluous OVERRIDES in machine conf files

2017-03-16 Thread Robert P. J. Day
In machine configuration files, there is no need to use OVERRIDES that match the precise machine being defined, so remove them for clarity and consistency from these lines in those respective files: PREFERRED_VERSION_linux-yocto_genericx86-64 ?= "4.10%" PREFERRED_VERSION_linux-yocto_genericx8

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Jack Mitchell
On 16/03/17 10:35, Alexander Kanavin wrote: On 03/16/2017 11:30 AM, Paul Barker wrote: Staying with NPM as the example, say we have a tree of 1000 dependencies for a top-level application recipe. I understand that generating and then parsing 1000 recipes will bloat things and slow down the build

[yocto] any YP machines or functionality that still require uImage creation?

2017-03-16 Thread Robert P. J. Day
i just noticed that the machine config file for mpc8315e-rdb still lists "uImage" as the default image type: KERNEL_IMAGETYPE = "uImage" IMAGE_BOOT_FILES ?= "u-boot.bin uImage uImage-mpc8315erdb.dtb;dtb" is there anything about that target that still *requires* uImage creation, as opposed to z

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Alexander Kanavin
On 03/16/2017 11:30 AM, Paul Barker wrote: Staying with NPM as the example, say we have a tree of 1000 dependencies for a top-level application recipe. I understand that generating and then parsing 1000 recipes will bloat things and slow down the build. However, we do need some way to apply patch

Re: [yocto] [Openembedded-architecture] Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Alexander Kanavin
On 03/13/2017 07:51 PM, Bruce, Henry wrote: I agree that leveraging the likes of 'npm install' will make life simpler but the problem with these operations is that they span a range of bitbake tasks. The reason we wrote an npm fetcher was to limit network access to the fetch task. This works in

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Alexander Kanavin
On 03/16/2017 10:17 AM, Josef Holzmayr wrote: - locking down specific versions of packages and their dependencies for reproductible builds. Thanks for summarizing! I have just one comment: at least initially, locking down specific versions has to be optional. We certainly can try our best, b

Re: [yocto] [meta-raspberrypi][PATCH 1/1] Remove orphan bbappend

2017-03-16 Thread Paul Barker
On Wed, 15 Mar 2017 21:18:44 +0100 Fabien Lahoudere wrote: > gstreamer1.0-omx_1.2.0.bb and gstreamer1.0-omx_git.bb have been removed > from poky on master branch, so related bbappend should be removed. > > Signed-off-by: Fabien Lahoudere > --- > .../gstreamer/gstreamer1.0-omx_1.2.0.bbappend

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Paul Barker
On Thu, 16 Mar 2017 09:17:57 +0100 Josef Holzmayr wrote: > I'll give it a shot and try to sum up the current state of affairs in > this discussion. In accordance to the "Package managers all the way > down"-presentation, I'm gonna use the term LPM (for language package > manager) for now on. >

Re: [yocto] Yocto Jetro / ls1046 : SDK with toolchains for both 32 and 64 bits

2017-03-16 Thread ARVIS Vincent
Hi >I didn't meet the same problem with you, here is my stdout log: >$ . > /opt/poky/2.0.3/environment-setup-armv7a-vfp-neon-pokymllib32-linux-gnueabi >$ $CC > -bash: arm-pokymllib32-linux-gnueabi-gcc: command not found We are on the jetro 2.0.0 and should evolved to the 2.0.3. If

Re: [yocto] ERROR: core-image-minimal-xfce-1.0-r0 do_rootfs:

2017-03-16 Thread ravikiran j
Sorry i forgot to add yocto list while replying. what about above error , how we can solve that problem ? On Thu, Mar 16, 2017 at 12:29 PM, Josef Holzmayr < holzm...@rsi-elektrotechnik.de> wrote: > Again, please keep your responses on the list! > > On 16.03.2017 07:52, ravikiran j wrote: > >>

Re: [yocto] [Openembedded-architecture] Sum up - Proposal: dealing with language-specific build tools/dependency management tools

2017-03-16 Thread Josef Holzmayr
I'll give it a shot and try to sum up the current state of affairs in this discussion. In accordance to the "Package managers all the way down"-presentation, I'm gonna use the term LPM (for language package manager) for now on. *Requirements* - repeatable and verifyable licensing of all depend

Re: [yocto] ERROR: core-image-minimal-xfce-1.0-r0 do_rootfs:

2017-03-16 Thread Josef Holzmayr
Again, please keep your responses on the list! On 16.03.2017 07:52, ravikiran j wrote: Suppose if i want to install some packages from debian or ubuntu repositories, how can i achieve that using rpm or ipk based distribution ? In short, not at all. This is not how things are meant to be.