Re: [yocto] Fwd: Potential (?) systemd YOCTO problems

On Tue, Jun 04, 2019 at 11:34:15PM +0200, Zoran Stojsavljevic wrote: (I did not find it anywhere in the manuals, maybe I missed the paragraph - please, advice where it is?). This is where I found it previously: https://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#using-systemd-excl

[yocto] Fwd: Potential (?) systemd YOCTO problems

> I would have a look at the values of > DISTRO_FEATURES_BACKFILL_CONSIDERED as well as > VIRTUAL-RUNTIME_initscripts. > > My understanding is that if the former is set to > "sysvinit", it causes any redundant SysVinit > scripts to be removed, and further, that if the > latter is set to "", then al

Re: [yocto] Fwd: /usr/share/common-license package/recipeinfo contains GPLv3 info

Thank you khem raj for your input, I have already tried with INCOMPATIBLE_LICENSE = "GPLv3+ LGPLv3+ AGPLv3+" And this also INCOMPATIBLE_LICENSE = "GPLv3* LGPLv3* AGPLv3*" But no luck, still I can see same output rootfs/usr/share/common-license/package/libgcrypt-lic/recipeinfo LICENSE: GPLV2+

Re: [yocto] Fwd: /usr/share/common-license package/recipeinfo contains GPLv3 info

On 5/23/19 2:42 AM, virendra kumar thakur wrote: Hello team, I am trying to build yocto image without GPLv3 package, I have added below things in local.conf and enable meta-gplv2 layer. INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3. 0" in local.conf. Can you try adding GPLv3+ to INCOM

[yocto] Fwd: /usr/share/common-license package/recipeinfo contains GPLv3 info

Hello team, I am trying to build yocto image without GPLv3 package, I have added below things in local.conf and enable meta-gplv2 layer. INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3. 0" in local.conf. After verifying from package.manifest and license.manifest file in build/tmp/deploy/license/

[yocto] Fwd: bb-matrix.sh Script not working as expected

Mit freundlichen Grüßen / Best Regards, Dhanush Keshava Reddy Soppahalli Mob: +4915216144064 -- Forwarded message - From: Dhanush K.S Date: Tue, 7 May 2019 at 13:28 Subject: bb-matrix.sh Script not working as expected To: Yocto discussion list Hello, I'm trying to evaluate th

Re: [yocto] Fwd: Trimming BOOST libraries installed

On Thu, 28 Mar 2019 at 12:40, Gabriele Zampieri wrote: > So I just specify the dependencies in my recipes, and then remove > IMAGE_INSTALL_append = " boost". Am I right? Yes. Your recipe that uses boost just needs DEPENDS=boost as a build-dependency. The linkage will be examined and the approp

[yocto] Fwd: Trimming BOOST libraries installed

Forgot to include the mailing list -- Forwarded message - Da: Gabriele Zampieri Date: gio 28 mar 2019 alle ore 13:38 Subject: Re: [yocto] Trimming BOOST libraries installed To: Burton, Ross Thank you for the fast reply. So I just specify the dependencies in my recipes, and the

[yocto] Fwd: Re: THISDIR variable in another meta-layer

In componentB.bb I have function do_install: do_install () { install -m 0755 -d ${D}/usr/share cmake_do_install install -m 0755 ${THISDIR}/default/script.sh ${D}/usr/share } In componentB.bbapend I overwrite function in order to install other script instead: do_install () { install -m 0755 -d

Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules

Probably, I'm learning ;-) On Wed, 7 Nov 2018 at 12:59, Outback Dingo wrote: > couldnt this have been a udev_append.bb > > instead of writing your own my-rules > On Wed, Nov 7, 2018 at 6:46 PM Markus W wrote: > > > > This my bb file and than I have added the following to local.conf > IMAGE_INST

Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules

couldnt this have been a udev_append.bb instead of writing your own my-rules On Wed, Nov 7, 2018 at 6:46 PM Markus W wrote: > > This my bb file and than I have added the following to local.conf > IMAGE_INSTALL_append = " my-rules ...". > > SUMMARY = "My rules" > LICENSE = "CLOSED" > PR = "r1" >

Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules

This my bb file and than I have added the following to local.conf IMAGE_INSTALL_append = " my-rules ...". SUMMARY = "My rules" LICENSE = "CLOSED" PR = "r1" SRC_URI = "file://90-interfaces.rules" do_install[nostamp] = "1" do_unpack[nostamp] = "1" do_install () { install -d ${D}${sysconfdir}/

Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules

On Wed, Nov 7, 2018, 16:44 Markus W I have resolved this issue. My problem was that in my layer I have a > recipe-core and within that I had the following structure > udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on > the same level. > > By renaming udev/udev-extra-rules to my

Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules

I have resolved this issue. My problem was that in my layer I have a recipe-core and within that I had the following structure udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on the same level. By renaming udev/udev-extra-rules to my-udev/my-udev-extra-rules it suddenly worked.

Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules

On Tue, Nov 6, 2018 at 11:57 AM Markus W wrote: > > Hi! > > I want to append the rules in the > recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from > within my own recipe. I can´t figure out how to do that. > > I have tried to add those rules as separate rules file in a recipe i

[yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules

Hi! I want to append the rules in the recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from within my own recipe. I can´t figure out how to do that. I have tried to add those rules as separate rules file in a recipe in my own layer. After the build I can see that the rules file i

Re: [yocto] Fwd: preempt-rt for 4.14.71 fails to build

Check the list. It never came through. You need to be a subscriber and would have received a bounce message. I know that, since I got the bounce as the list admin :D Bruce On 2018-10-10 4:03 PM, Dimitris Tassopoulos wrote: I've already send this to that list a few days ago, but since I didn't

Re: [yocto] Fwd: preempt-rt for 4.14.71 fails to build

I've already send this to that list a few days ago, but since I didn't got any reply there I've also asked here in case that someone else shares the same experience. Dimitris On Wed, 10 Oct 2018, 21:48 Bruce Ashfield, wrote: > On 2018-10-10 2:18 PM, Dimitris Tassopoulos wrote: > > Hi all! > > >

Re: [yocto] Fwd: preempt-rt for 4.14.71 fails to build

On 2018-10-10 2:18 PM, Dimitris Tassopoulos wrote: Hi all! I've tried to build the latest preempt-rt kernel from the `v4.14/standard/preempt-rt/base` and it fails to build. These are the hashes I've used: This should go to the linux-yocto list, since that's where people interested in the li

[yocto] Fwd: preempt-rt for 4.14.71 fails to build

Hi all! I've tried to build the latest preempt-rt kernel from the `v4.14/standard/preempt-rt/base` and it fails to build. These are the hashes I've used: ``` LINUX_VERSION = "4.14.71" SRCREV_machine = "c37a14708f5b618602f84f83f902346e055824c3" SRCREV_meta = "1fb0b0379fb5883ce5af7485374e3f78ee4272

[yocto] Fwd: [OE-core] OpenEmbedded branded T-shirts and Polo shirts!

Go grab your next attire ! -- Forwarded message - From: Denys Dmytriyenko Date: Thu, Sep 27, 2018 at 5:15 PM Subject: Re: [OE-core] OpenEmbedded branded T-shirts and Polo shirts! To: , , Besides black and white OpenEmbedded T-shirts and Polos, the shop has also added blue ones!

Re: [yocto] Fwd: Unable to add a dev package to the Extended SDK

On Fri, Aug 24, 2018 at 5:08 AM ChenQi wrote: > I think using IMAGE_INSTALL_append = " curl", and then `bitbake > core-image-minimal -c populate_sdk_ext" is sufficient. > It was indeed all it was needed. Thanks! Gabriele -- ___ yocto mailing list yo

Re: [yocto] Fwd: Unable to add a dev package to the Extended SDK

I think using IMAGE_INSTALL_append = " curl", and then `bitbake core-image-minimal -c populate_sdk_ext" is sufficient. After this, you can develop against curl libs/headers inside the sdk. Best Regards, Chen Qi On 08/23/2018 04:38 PM, Gabriele Favalessa wrote: Hi! I'm attempting to add `curl-

[yocto] Fwd: Unable to add a dev package to the Extended SDK

Hi! I'm attempting to add `curl-dev` to an Extensible SDK for yocto (sumo release) with target machine qemuarm. On a fresh checkout I've added to `conf/local.conf` TOOLCHAIN_TARGET_TASK_append = " curl-dev" and then run `bitbake -c populate_sdk_ext core-image-minimal`. This is the error I ge

[yocto] Fwd: Doubts about image "equalness"

Hey Matthias, thanks for the response > it seems a non trivial task to generate an image out > of another image by hand. So much, that can get messed up (permissions, > owner...). I don't see it as that big of a problem. In our case it would end up mounting the production image and editing config

Re: [yocto] Fwd: Basehash value changed issue

On Mon, 2018-07-02 at 17:37 +0530, techi eth wrote: > I have not got success of building my first image so it happen's to > me always. I also tried deleting tmp,cache folder & re-build again > but problem persist. > Is it something to do with timestamps ? > > I do see below patch & applied changes

Re: [yocto] Fwd: Basehash value changed issue

i don't see any time usage in recipe however if this variable need's to exclude than could you please share me hint or reference of recipe to do the same. I tried below in recipe but no success. PR[vardepsxeclude]="DATETIME DATE TIME" On Mon, Jul 2, 2018 at 4:51 PM, Mike Looijmans wrote: > The

Re: [yocto] Fwd: Basehash value changed issue

The simplest (and probably preferred) way to fix would be to get rid of TIME usage from that recipe. Parsing the recipe twice should yield the same result and your trouble would be over. On 02-07-18 07:27, techi eth wrote: Hi, Can anybody give me hint over below issue. Thanks Kind rega

Re: [yocto] Fwd: Basehash value changed issue

I have not got success of building my first image so it happen's to me always. I also tried deleting tmp,cache folder & re-build again but problem persist. Is it something to do with timestamps ? I do see below patch & applied changes but problem persist. http://cgit.openembedded.org/openembedded-

Re: [yocto] Fwd: Basehash value changed issue

Does this happen always or only sometimes? If only sometimes you probably made changes to the recipe or dependent recipes while building. You cannot do that. On Mon, Jul 2, 2018 at 7:27 AM, techi eth wrote: > Hi, > > Can anybody give me hint over below issue. > > Thanks > > -- Forwarded m

[yocto] Fwd: Basehash value changed issue

Hi, Can anybody give me hint over below issue. Thanks -- Forwarded message -- From: techi eth Date: Thu, Jun 21, 2018 at 6:30 PM Subject: Basehash value changed issue To: yocto@yoctoproject.org Hi, I am facing issue with basehash value changed while building image on one of m

Re: [yocto] Fwd: image-mklibs.bbclass fails

I am currently upgrading a morty based rootfs to rocko, and today I found that the morty based poky layer had a patch which they sent upstream over one year ago. Author Peter Liu This is similar to what You suggested, and the fix works also in rocko. We will decide tomorrow how to proceed. Best

Re: [yocto] Fwd: image-mklibs.bbclass fails

On Mon, May 28, 2018 at 2:10 AM, Ulf Samuelsson wrote: > Checked out poky > git checkout -b rocko origin/rocko > export MACHINE=beaglebone > . ./oe-init-build-env > > Added to local.conf: > MKLIBS_OPTIMIZED_IMAGES_append = " core-image-minimal" > > Result: > > /core-image-minimal/1.0-r0/temp/run.m

Re: [yocto] Fwd: Yocto

I think you can effectively build your own image with QT, it seems to me thats what you are interested in. For that you would be able to create a new recipe which includes the core-image-minimal recipe and then adds the needed QT packages and packagegroups via CORE_IMAGE_EXTRA_INSTALL. On Fri, May

[yocto] Fwd: image-mklibs.bbclass fails

Checked out poky git checkout -b rocko origin/rocko export MACHINE=beaglebone . ./oe-init-build-env Added to local.conf: MKLIBS_OPTIMIZED_IMAGES_append = " core-image-minimal" Result: /core-image-minimal/1.0-r0/temp/run.mklibs_optimize_image.13363: line 133: i586-poky-linux-readelf: command not

[yocto] Fwd: Yocto

-- Forwarded message - From: Scott Rifenbark Date: Fri, May 25, 2018, 6:18 AM Subject: Fwd: Yocto To: Hi Nikhil, I am forwarding your email to the Yocto Project email group. Someone there can better help you with your questions. I take care of the Yocto manual set. Thanks, S

[yocto] Fwd: Yocto

Hi Nikhil, I am forwarding your email to the Yocto Project email group. Someone there can better help you with your questions. I take care of the Yocto manual set. Thanks, Scott Rifenbark -- Forwarded message - From: nikh kkvv Date: Fri, May 25, 2018, 6:03 AM Subject: Yocto To

[yocto] Fwd: Integrating Ixxat SocketCAN Drivers in image

Hi, I have to integrate Ixxat SocketCAN driver in the image which will run our system. The organisation of the files is the following Yocto/MyCompany/meta-myCompany/recipes-candriver/ixxat-socketcan This directory contains the file ixxat-socketcan.bb. The content of this file is

Re: [yocto] Fwd: How to make the os-release package work with local walltime instead of GMT?

Hi Davis, You can try to add this to conf/local.conf or redefine it in os-release.bb: BUILD_ID = "${@time.strftime('%Y-%m-%d %H:%M:%S',time.localtime())}" // Robert On 01/11/2018 12:55 PM, Davis Roman wrote: Hello, I'm trying to fullfill a requirement which states that I must have a file in

[yocto] Fwd: How to make the os-release package work with local walltime instead of GMT?

Hello, I'm trying to fullfill a requirement which states that I must have a file in my root filesystem which has the timestamp of when the rootfs was generated for traceability purposes. I've included the os-release package into my image recipe. However, when I cat /etc/os-release, I notice that

[yocto] Fwd: [meta-raspberrypi] linux kernel rt

On Thu, Dec 14, 2017 at 9:59 AM, Sherif Omran wrote: > do you use the bluetooth also? > > > > > schöne Grüße aus dem Bodensee :) > > Let's get back back to public.. Hallo Sherif, I have disabled WLAN and Bluetooth for my devices - so I cannot say something about that. Reason is that I play arou

[yocto] Fwd: kernel menuconfig with screen is not populating clearly

Hi ALL, When my oe_term is set to screen/tmux, the menuconfig for kernel,u-boot,.. is having some empty spaces. This is making distorted view. Please see the attachment. It is looking good with gnome and other terminals with ssh -x. Anything i need to do to get clear menuconfig without ssh -X ?

Re: [yocto] Fwd: do_configure error

On 28 September 2017 at 05:51, Khem Raj wrote: > On Sat, Sep 23, 2017 at 12:33 PM, Burton, Ross > wrote: > > On 23 September 2017 at 06:56, mohammed aqdam > > wrote: > >> > >> i'm getting the following error... > >> > >> root@pcz-ee207837-2:/u/my_poky/poky-2/poky/build# bitbake -k > >> rpi-test

Re: [yocto] Fwd: do_configure error

On Sat, Sep 23, 2017 at 12:33 PM, Burton, Ross wrote: > On 23 September 2017 at 06:56, mohammed aqdam > wrote: >> >> i'm getting the following error... >> >> root@pcz-ee207837-2:/u/my_poky/poky-2/poky/build# bitbake -k >> rpi-test-image > > > >> configure: error: you should not run config

Re: [yocto] Fwd: do_configure error

On 23 September 2017 at 06:56, mohammed aqdam wrote: > > i'm getting the following error... > > root@pcz-ee207837-2:/u/my_poky/poky-2/poky/build# bitbake -k rpi-test-image > configure: error: you should not run configure as root As it says, you're running as root. I thought we bailed e

[yocto] Fwd: do_configure error

-- Forwarded message -- From: "mohammed aqdam" Date: Sep 21, 2017 6:59 PM Subject: do_configure error To: "yocto" Cc: Hi all, i was trying to build rpi-test-image for my rpi3. i'm getting the following error... root@pcz-ee207837-2:/u/my_poky/poky-2/poky/build# bitbake -k rpi-te

Re: [yocto] Fwd: Best practices when for script recipes.

On Wed, Sep 13, 2017 at 1:06 PM, Einar Vading wrote: > Hi, > > I was just wondering if there is some best practice advice on how to > handle adding a single script from a recipe. > > If I have one or a few shell scripts with their own recipe. Do I make > a git and use the git from the recipe or do

[yocto] Fwd: Best practices when for script recipes.

Hi, I was just wondering if there is some best practice advice on how to handle adding a single script from a recipe. If I have one or a few shell scripts with their own recipe. Do I make a git and use the git from the recipe or do I just add the scripts to a files directory and install from ther

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

> For all future releases, forever? Committing to that would be foolish. Nothing is forever, you know this at the best. Seemed/seems that Canon Lake (supposed to be Core 7, now it is Core 9. or Core 10, or One only knows... You name it) supposed to be out in Q3 2016, but INTEL did not reach yield

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

On 24 August 2017 at 15:34, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > Do you agree to continue keeping DNF package (in > .../meta/recipe_devtools/) for handling of .rpm type of packages in the > future releases of YOCTO (it is, after all, much better and more mature > tool that

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

On 08/24/2017 05:34 PM, Zoran Stojsavljevic wrote: Do you agree to continue keeping DNF package (in .../meta/recipe_devtools/) for handling of .rpm type of packages in the future releases of YOCTO (it is, after all, much better and more mature tool that smartpm)? The smart to dnf transition

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

> No. Yocto is not an operating system, it's a toolset that can be used to build many wildly different operating systems. An rpm repo would > only be compatible with one of those OSes. YOCTO is a custom made distro for eLinuxes, on this I agree with you. At least, you should keep DNF (instead smar

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

On 24 August 2017 at 10:33, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > Hello Jussi, > > I would like to thank you very much for the useful reply. It was a bit different with me, but most boiled down as you said/explained (the difference are in client/server IP addresses, but ev

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

Hello Jussi, I would like to thank you very much for the useful reply. It was a bit different with me, but most boiled down as you said/explained (the difference are in client/server IP addresses, but everything else is almost the same - I guess, I do not have complete set of .rpms on my server si

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

On 23 August 2017 at 14:51, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > Hello Jussi, > > Let me start giving you all the hints. So you can see where I lead. You > made few mistakes, so DNF won't work as such/is (by default) in Pyro 2.3.1. > > I investigated a bit (I already wrote

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

Hello Jussi, Let me start giving you all the hints. So you can see where I lead. You made few mistakes, so DNF won't work as such/is (by default) in Pyro 2.3.1. I investigated a bit (I already wrote that I am quite familiar with DNF and its concepts). For the starters: Your DNF repo on Pyro 2.3.

Re: [yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

On 23 August 2017 at 09:56, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > Privet Aleks, > > Nezacem zlitsja/serditsja. Ja prosto ne znal cto u vas takaja politika. > > All Cool. Did not know that this is the policy, to have real names on > YOCTO list. I removed nobody from it, and

[yocto] Fwd: [DNF YOCTO clarifications] smart was replaced with dnf in Yocto 2.3

Privet Aleks, Nezacem zlitsja/serditsja. Ja prosto ne znal cto u vas takaja politika. All Cool. Did not know that this is the policy, to have real names on YOCTO list. I removed nobody from it, and added my real name and real @. I removed user nobody from the YOCTO @ list. The/Your answer is too

[yocto] Fwd: [meta-raspberrypi] Unified serial console device option

oops, forgot "reply all" -- Forwarded message -- From: Trevor Woerner Date: Wed, Apr 19, 2017 at 8:53 AM Subject: Re: [yocto] [meta-raspberrypi] Unified serial console device option To: Andrei Gherzan On Wed, Apr 19, 2017 at 7:28 AM, Andrei Gherzan wrote: > I've seen people r

Re: [yocto] Fwd: iMX6UL - QtQuick - QtQuick2DRenderer

Hi, one point I noticed directly, you should only use one "-", i.e. "-platform linuxfb" . Moreover, best check with "export QT_DEBUG_PLUGINS=1" that linuxfb is located and loaded correctly. Only if all of this works fine, you should start looking into the compile options. Cheers, Andreas On Th

[yocto] Fwd: cups 2.2.2 Backend filter not include serial port support.

Hello, I'm try to build cups 2.2.2. It is not included serial backend support. How to enable serial port backend support ? Thanks. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: iMX6UL - QtQuick - QtQuick2DRenderer

On Thu, 2017-04-06 at 10:35 +0200, Stefano Zuín wrote: > > > > Mensaje reenviado > Asunto: [yocto] iMX6UL - QtQuick - QtQuick2DRenderer > Fecha:Wed, 5 Apr 2017 13:29:13 +0200 > De: Stefano Zuín > Para: yocto@yoctoproject.org > > Hi all, > > I'm trying to run

[yocto] Fwd: iMX6UL - QtQuick - QtQuick2DRenderer

Mensaje reenviado Asunto: [yocto] iMX6UL - QtQuick - QtQuick2DRenderer Fecha: Wed, 5 Apr 2017 13:29:13 +0200 De: Stefano Zuín Para: yocto@yoctoproject.org Hi all, I'm trying to run a graphical Qt application based in QtQuick2 and QML (example calqtr) in my

Re: [yocto] Fwd: [meta-oracle-java][PATCH 1/6] oracle-jse.inc: Fix unattended downloading source

Hi, On Wed, Mar 29, 2017 at 09:03:15AM +0200, Jaap de Jong wrote: > --- > > recipes-devtools/oracle-java/oracle-jse.inc | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/recipes-devtools/oracle-java/oracle-jse.inc > b/recipes-devtools/oracle-java/oracle-jse.inc > index 8

[yocto] Fwd: [meta-oracle-java][PATCH 6/6] oracle-jse: Add sources package

--- recipes-devtools/oracle-java/oracle-jse.inc | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/recipes-devtools/oracle-java/oracle-jse.inc b/recipes-devtools/oracle-java/oracle-jse.inc index 37685cd..18ef411 100644 --- a/recipes-devtools/oracle-java/oracle-jse.inc +++ b

[yocto] Fwd: [meta-oracle-java][PATCH 5/6] Use update-alternatives

--- recipes-devtools/oracle-java/oracle-jse-jdk.inc | 14 ++ recipes-devtools/oracle-java/oracle-jse.inc | 12 ++-- 2 files changed, 24 insertions(+), 2 deletions(-) diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk.inc b/recipes-devtools/oracle-java/oracle-jse-j

[yocto] Fwd: [meta-oracle-java][PATCH 4/6] Use 'standarized' install path

--- recipes-devtools/oracle-java/oracle-jse-jdk.inc | 15 ++- recipes-devtools/oracle-java/oracle-jse.inc | 12 2 files changed, 14 insertions(+), 13 deletions(-) diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk.inc b/recipes-devtools/oracle-java/oracle-jse

[yocto] Fwd: [meta-oracle-java][PATCH 3/6] oracle-jse-ejre: Add recipe for arm softfloat jvm

--- .../oracle-jse-ejre-arm-sflt-client-headless.inc | 10 + .../oracle-java/oracle-jse-jre_1.8.0.bb| 24 +- 2 files changed, 24 insertions(+), 10 deletions(-) create mode 100644 recipes-devtools/oracle-java/oracle-jse-ejre-arm-sflt-client-headless.inc

[yocto] Fwd: [meta-oracle-java][PATCH 2/6] oracle-java: upgrade to 8u121

--- .../oracle-jse-ejre-arm-vfp-hflt-client-headless.inc | 11 ++- recipes-devtools/oracle-java/oracle-jse-ejre.inc | 14 +++--- recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.8.0.bb | 10 +- .../oracle-java/oracle-jse-jdk-x86-64_1.8.0.bb

[yocto] Fwd: [meta-oracle-java][PATCH 1/6] oracle-jse.inc: Fix unattended downloading source

--- recipes-devtools/oracle-java/oracle-jse.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-devtools/oracle-java/oracle-jse.inc b/recipes-devtools/oracle-java/oracle-jse.inc index 8cb0953..488bce2 100644 --- a/recipes-devtools/oracle-java/oracle-jse.inc +++ b/rec

Re: [yocto] Fwd: how to enable c++11 support in yocto

On 27 March 2017 at 05:58, Vadalasetti Sivanageswararao < vsivanag...@gmail.com> wrote: > cc1plus: warning: include location "/usr/local/include" is unsafe for > cross-compilation [-Wpoison-system-directories] > Your build is referring to host files so this is likely the problem. This is a bug i

[yocto] Fwd: how to enable c++11 support in yocto

-- Forwarded message -- From: Vadalasetti Sivanageswararao Date: Sun, Mar 26, 2017 at 9:26 PM Subject: Re: how to enable c++11 support in yocto To: Khem Raj Dear Yocto Team, when i compiling my c++ programs it is giving below error. please give me the solution for below error.

Re: [yocto] Fwd: error while compiling hello_2.7.bb

On 12/19/2016 02:42 PM, praveen vattipalli wrote: I have hello_2.7.bb file which contains as below vim hello_2.7.bb DESCRIPTION = "GNU Helloworld application" SECTION = "test" LICENSE = "BSD" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/BSD;md5=377

[yocto] Fwd: error while compiling hello_2.7.bb

Hi All, I have hello_2.7.bb file which contains as below vim hello_2.7.bb DESCRIPTION = "GNU Helloworld application" SECTION = "test" LICENSE = "BSD" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/BSD;md5= 3775480a712fc46a69647678acb234cb" SRC_DIR ?= "/home/rajesh/poky-krogoth-15.0.2/meta/recipe

[yocto] Fwd: Failed to build image, output error "ERROR: Worker process (11579) exited unexpectedly (-9), shutting down..."

Hi ALL: I am an software engineer in Askey. I have one question about building the apq-8053 device image. The main question is that I can not build well. Below is the error messages which show unexpected shutdown. I have studied from the web site and google and found the following links shows tha

Re: [yocto] Fwd: Changelog creation for a list of recipes

On 6/1/16 7:54 AM, Oleksandr Poznyak wrote: > Hi, > > I believe that it would be great to have a special variable that triggers > changelog creation for the specific recipe. I've had some requests from customers to automatically generate changelogs for both recipes and packages. I've not yet beg

[yocto] Fwd: Changelog creation for a list of recipes

Hi, I believe that it would be great to have a special variable that triggers changelog creation for the specific recipe. For example: PN = "my_recipe" SRC_URI = "git://${SOME_GIT_REPO};protocol=ssh" SRCREV = "${AUTOREV}" PV = "1+git${SRCPV}" CHANGELOG = "1" This should produce ${DEPLOY_DIR}/

Re: [yocto] [Fwd: gobject introspection release notes]

> Subject: Re: [yocto] [Fwd: gobject introspection release notes] > To: zhenhua@nxp.com; christrobri...@hotmail.com > CC: yocto@yoctoproject.org > From: alexander.kana...@linux.intel.com > Date: Wed, 27 Apr 2016 15:38:01 +0300 > > On 04/26/2016 11:05 AM, Zhenhua Luo wrote

Re: [yocto] [Fwd: gobject introspection release notes]

On 04/26/2016 11:05 AM, Zhenhua Luo wrote: Any ideas as to why "qemu-ppc64 crashes out immediately"? I can confirm the build ends in a segfault when I tried building gobject-introspection for the t1042d4rdb-64b machine. */[Luo Zhenhua-B19537] This is a gobject-introspection support issue of QEM

Re: [yocto] [Fwd: gobject introspection release notes]

Hello Chris, Please see my inline comments. Best Regards, Zhenhua From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Chris Trobridge Sent: Monday, April 25, 2016 11:01 PM To: yocto@yoctoproject.org Subject: Re: [yocto] [Fwd: gobject introspection

Re: [yocto] [Fwd: gobject introspection release notes]

Any ideas as to why "qemu-ppc64 crashes out immediately"? I can confirm the build ends in a segfault when I tried building gobject-introspection for the t1042d4rdb-64b machine. I did get one qemu crash recorded by Fedora but the actual crash dumps (appended) are for a PowerPC. That said, given

Re: [yocto] Fwd: Preventing rebuild of dependencies

On Thu, Apr 21, 2016 at 6:08 AM, Sassan Panahinejad wrote: > Hi, > > On several Yocto-based projects I've worked on, I've ended up accidentally > triggering rebuilds of large packages such as QT or Chromium. > > The example I keep running into at the moment is whenever I modify the > kernel config

[yocto] Fwd: Preventing rebuild of dependencies

Hi, On several Yocto-based projects I've worked on, I've ended up accidentally triggering rebuilds of large packages such as QT or Chromium. The example I keep running into at the moment is whenever I modify the kernel config, I trigger Chromium to rebuild next time I rebuild the image. This mean

[yocto] [Fwd: gobject introspection release notes]

Hello, here is the information about gobject introspection that should be placed to the release notes of the upcoming yocto release. 1. Introduction This Yocto release adds support for generating and packaging GObject introspection data. GObject introspection data is a description of the API pro

Re: [yocto] Fwd: OEDAM: New Location - Catamaran resort

We need the final headcount by next Monday. Food, breakfast, lunch and refreshments, will be provided. If you have special dietary needs such as vegetarian, gluten-free etc. please indicate so behind you name. We'll do the best to accommodate them. Rudi On Tuesday, March 29, 2016 12:57:23 PM P

[yocto] Fwd: OEDAM: New Location - Catamaran resort

OEDAM moved. Thanks Rudi and Jefro. Please add your name to the attendee list so Jefro can get the correct amount of food and coffee. He needs the number "soon". Philip Forwarded Message Subject: OEDAM: New Location - Catamaran resort Date: Mon, 28 Mar 2016 13:36:41 -0700 From:

[yocto] Fwd: Re: BeagleBone...bitbake -v core-image-sato stops

Forwarded Message Subject:Re: [yocto] BeagleBone...bitbake -v core-image-sato stops Date: Mon, 28 Dec 2015 10:09:09 +0100 From: Nico Mock To: yocto@yoctoproject.org On 28.12.2015 09:58, kaffeesurro...@posteo.de wrote: Sorry guys . I thought I was done

Re: [yocto] Fwd: Re: Python3 and Numpy

Hello, I'm still trying to get python3-numpy to compile. I have been inspecting log file for quite a while. One lead I got is that gcc have -L=/usr/lib in its arguments. I diff log.do_compile from python3-numpy and log.do_compile from python-numpy. I see no reference to /usr/lib in python-numpy

Re: [yocto] Fwd: Re: Python3 and Numpy

Here the full log: http://sprunge.us/SYCO?log Le 27/11/2015 19:36, Benoit Rapidel a écrit : Ok, thanks Numpy start to except ld can't find npymath and npysort. I checked with devshell, there is libnpymath.a and libnpysort.a within build/temp.linux-x86_64-3.4, which is used by ld to find libs

Re: [yocto] Fwd: Re: Python3 and Numpy

Ok, thanks Numpy start to except ld can't find npymath and npysort. I checked with devshell, there is libnpymath.a and libnpysort.a within build/temp.linux-x86_64-3.4, which is used by ld to find libs. Do you have any clues ? I'm trying to compile numpy 1.9.2 with python3. Thanks in advance

Re: [yocto] Fwd: Re: Python3 and Numpy

On 11/27/2015 06:39 PM, Benoit Rapidel wrote: I found one in meta. How do I update it ? I'm using poky jethro. Should a create a new one named python3-numpy or the same recipe should handle both python versions ? From what I can see, the standard approach is to create a separate recipe for pyt

[yocto] Fwd: Re: Python3 and Numpy

I found one in meta. How do I update it ? I'm using poky jethro. Should a create a new one named python3-numpy or the same recipe should handle both python versions ? B @Alex, sorry for that, reposting in the mailing list. Le 27/11/2015 16:19, Alexander Kanavin a écrit : On 11/27/2015 05:11 P

[yocto] Fwd: Welcome to the "Openembedded-architecture" mailing list (V2)

During OEDEM in Dublin we talked about creating a list for high level architecture discussions about the OpenEmbedded Build System. Bring your big ideas to the list, discuss them, and bring the resources to implement them. We did discuss list proliferation, filtering patches, etc and still decide

[yocto] Fwd: Welcome to the "Openemebdded-architecture" mailing list

During OEDEM in Dublin we talked about creating a list for high level architecture discussions about the OpenEmbedded Build System. Bring your big ideas to the list, discuss them, and bring the resources to implement them. We did discuss list proliferation, filtering patches, etc and still decide

[yocto] Fwd: With my layer, Systemd not invoking my application at startup

Hi All, I have created a layer (my first layer) and have build it with WindRiver media which uses Systemd for the startup services. As per my application need, I have to create a new user on the final image and change the owner permissions of certain files to the new user. Since I could not get

Re: [yocto] Fwd: With my layer, Systemd not invoking my application at startup

Thanks a lot Saul for your valuable inputs on my problem. I have tried inheriting from the useradd.bbclass and the USER add works with both approach i.e by inheriting from useradd.bb class or manually calling useradd. But my main problem 'wherein the systemd does not invoke my service during firs

Re: [yocto] Fwd: With my layer, Systemd not invoking my application at startup

On 06/30/2015 08:35 PM, Vipin Nair wrote: Hi All, I have created a layer (my first layer) and have build it with WindRiver media which uses Systemd for the startup services. As per my application need, I have to create a new user on the final image and change the owner permissions of certain f

[yocto] Fwd: With my layer, Systemd not invoking my application at startup

Hi All, I have created a layer (my first layer) and have build it with WindRiver media which uses Systemd for the startup services. As per my application need, I have to create a new user on the final image and change the owner permissions of certain files to the new user. Since I could not get

[yocto] Fwd: [OE-core] open source conference in Honduras needs Yocto Project/Openembedded/OpenHardware speaker

Speaking opportunity in Honduras. Contact Steve, not me. Philip Forwarded Message Subject: [OE-core] open source conference in Honduras needs Yocto Project/Openembedded/OpenHardware speaker Date: Tue, 2 Jun 2015 14:45:22 -0700 From: Stephen Arnold To: Patches and discussions

Re: [yocto] Fwd: dizzy 1.7 udev automount misbehaviour

Hi Yocto, For the record the issue is in current dizzy branch and occurs when using systemd and udev along with udev-extraconf mount scripts. By default, systemd-udevd.service has the option MountFlags=slave, which means that mounts are only seen by udevd process. This explains some weird behavior

  1   2   3   >