[yocto] gobject introspection needing pygobject (cross-compilation)

I've got a few packages in my image which need gobject introspection. (x86-64 host, ARM target) One is building fine, but the other - NetworkManager - is failing to generate the introspection data because it can't analyse the cross-compiled library. Apparently it uses pygobject in doing this, and t

Re: [yocto] GCC on ARM

On 2017-03-31 07:07, Khem Raj wrote: On 3/30/17 9:07 PM, Gary Thomas wrote: [slightly off-topic] I work with a number of embedded ARM devices, all with different processors, hence somewhat different tuning and build directories: Raspberry-Pi (1,2,3 - mostly 3): TUNE_FEATURES = "arm

Re: [yocto] GCC on ARM

On 3/30/17 9:07 PM, Gary Thomas wrote: > [slightly off-topic] > > I work with a number of embedded ARM devices, all with different > processors, hence somewhat different tuning and build directories: > Raspberry-Pi (1,2,3 - mostly 3): > TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4

[yocto] GCC on ARM

[slightly off-topic] I work with a number of embedded ARM devices, all with different processors, hence somewhat different tuning and build directories: Raspberry-Pi (1,2,3 - mostly 3): TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7" build dirs:

Re: [yocto] [meta-raspberrypi][morty][PATCH 0/3] Stable branch kernel updates

On Thu, Mar 30, 2017 at 07:47:07AM +0100, Paul Barker wrote: > On Tue, 14 Mar 2017 10:32:34 + > Paul Barker wrote: > > > This series contains backports of patches from Khem's latest combined pull > > request. I've boot tested a raspberrypi3 (4.4.y and 4.9.y kernels) and a > > raspberrypi (4.9.

[yocto] [patchwork][PATCH v2] parsemail.py: Improve find_series_for_mail

Patch Series that are sent as replies to other Series with different patch quantity are not appropriately detected as such, breaking the thread and causing missing revisions. This change improves the find_series_for_mail function to appropriately detect when a message is part of a thread by perfor

[yocto] [patchwork][PATCH] parsemail.py: Improve find_series_for_mail

Patch Series that are sent as replies to other Series with different patch quantity are not appropriately detected as such, breaking the thread and causing missing revisions. This change improves the find_series_for_mail function to appropriately detect when a message is part of a thread by perfor

Re: [yocto] Meaning of 'Support Level' column in https://wiki.yoctoproject.org/wiki/Releases

Hi Alain, On Friday, 31 March 2017 7:44:22 AM NZDT Alain Achkar wrote: > We are currently on Jethro and planning to upgrade to Krogoth (can't use > Morty yet, since Freescale/NXP hasn't released Morty yet). > > Just wondering what the meaning of the 'Support Level' column is, or if you > can poin

[yocto] Meaning of 'Support Level' column in https://wiki.yoctoproject.org/wiki/Releases

Hello! We are currently on Jethro and planning to upgrade to Krogoth (can't use Morty yet, since Freescale/NXP hasn't released Morty yet). Just wondering what the meaning of the 'Support Level' column is, or if you can point me to documentation about it. Thanks! -- _

Re: [yocto] [PATCH] i386 machine.cfg: Explicitly disable 64BIT

On Thu, 2017-03-30 at 11:14 -0600, Leonardo Sandoval wrote: > On Thu, 2017-03-30 at 09:56 -0700, Saul Wold wrote: > > > > Since we do not set the 64 bit flags, newer kernels seem to build > > 64bit > > config files by default. This is due to a hard-coded uname -m check > > that > > selects the KBU

Re: [yocto] [PATCH] i386 machine.cfg: Explicitly disable 64BIT

On Thu, 2017-03-30 at 09:56 -0700, Saul Wold wrote: > Since we do not set the 64 bit flags, newer kernels seem to build 64bit > config files by default. This is due to a hard-coded uname -m check that > selects the KBUILD_DEFCONFIG based on the host, not the cross target. > Saul, this is poky co

[yocto] [PATCH] i386 machine.cfg: Explicitly disable 64BIT

Since we do not set the 64 bit flags, newer kernels seem to build 64bit config files by default. This is due to a hard-coded uname -m check that selects the KBUILD_DEFCONFIG based on the host, not the cross target. Similar to e9ec769926b2378e63380bd7762ce7ce201af151 in the yocto-kernel-cache repo

Re: [yocto] arm-angstrom-linux-gnueabi-gcc: fatal error: no input files

On Thu, 2017-03-30 at 17:25 +0200, Yuvarajesh Valleru wrote: > Thank you for great help and suggestions. I will go through other > recipes and try it again. > Also, you can try the script 'yocto-layer' ('create' subcommand) to create a layer with a single recipe (the hello world one) Leo > Th

Re: [yocto] arm-angstrom-linux-gnueabi-gcc: fatal error: no input files

Thank you for great help and suggestions. I will go through other recipes and try it again. Thanks again. Am 30.03.2017 um 14:46 schrieb Fabien Lahoudere: Seems to be related to missing CFLAGS to compile. IMO you should look at how other recipe build qt4 apps. On Thu, 2017-03-30 at 14:38 +02

Re: [yocto] arm-angstrom-linux-gnueabi-gcc: fatal error: no input files

On 2017-03-30 14:46, Fabien Lahoudere wrote: Seems to be related to missing CFLAGS to compile. IMO you should look at how other recipe build qt4 apps. The primary problem is that between the time the info you are following (probably many years old now - Angstrom has been quite stale since 2015

Re: [yocto] arm-angstrom-linux-gnueabi-gcc: fatal error: no input files

Seems to be related to missing CFLAGS to compile. IMO you should look at how other recipe build qt4 apps. On Thu, 2017-03-30 at 14:38 +0200, Yuvarajesh Valleru wrote: > Thanks, It worked. But experienced another error. > > ERROR: helloworld-1.0-r0 do_compile: Function failed: do_compile (log  > f

Re: [yocto] arm-angstrom-linux-gnueabi-gcc: fatal error: no input files

Thanks, It worked. But experienced another error. ERROR: helloworld-1.0-r0 do_compile: Function failed: do_compile (log file is located at /home/cc/src/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/helloworld/1.0-r0/temp/log.do_compile.31394) ERROR: Logfile of failure stor

Re: [yocto] Compiling custom kernel

Hi, thank you for your answer. Looks like I got no missing dependencies and it compiled without problems. 2017-03-29 20:23 GMT+02:00 Bruce Ashfield : > On 2017-03-29 1:11 PM, Alvaro Garcia wrote: > >> Hi, I'm trying to compile a custom kernel (just custom config). >> I created a recipe called lin

Re: [yocto] Compiling custom kernel

Hi, that was exactly my problem. Finally the kernel was compiled with my config. I'm so happy now, thank you! 2017-03-29 19:32 GMT+02:00 Leonardo Sandoval < leonardo.sandoval.gonza...@linux.intel.com>: > On Wed, 2017-03-29 at 19:11 +0200, Alvaro Garcia wrote: > > Hi, I'm trying to compile a custo

Re: [yocto] arm-angstrom-linux-gnueabi-gcc: fatal error: no input files

Try do_compile() {   ${CC} ${S}/helloworld.cpp -o ${S}/helloworld } On Thu, 2017-03-30 at 12:43 +0200, Yuvarajesh Valleru wrote: > Here is the tree for my recipe and also attached the error. > > /home/cc/src/oe-core/build/../layers/meta-layer/recipes-hi/helloworld/ > ├── files > │ ├── h

[yocto] arm-angstrom-linux-gnueabi-gcc: fatal error: no input files

Here is the tree for my recipe and also attached the error. /home/cc/src/oe-core/build/../layers/meta-layer/recipes-hi/helloworld/ ├── files │ ├── helloworld.cpp │ └── helloworld.pro └── helloworld_1.0.bb 1 directory, 3 files ERROR: helloworld-1.0-r0 do_compile: Function failed: do_compile (log

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

Hi, On Thu, Mar 30, 2017 at 11:02:48AM +0200, Jaap de Jong wrote: > > On 30-03-17 10:57, Maxin B. John wrote: > >Hi, > > > >Thank you very much for these updates. Merged to master-next. > > > >Note: from now on, please send the patches using "git send-email" > >as mentioned in the README file. >

Re: [yocto] Parse error: unable to parse line and new error arm-linux-gnueabi-gcc : helloworld.cpp 'no such file or directory'

I think you should post a new mail. Add tree /home/cc/src/oe-core/build/../layers/meta-layer/recipes-hi/helloworld/ to your new mail. On Thu, 2017-03-30 at 12:11 +0200, Yuvarajesh Valleru wrote: > Thank you. By typing the code again the eroor solved. but an another error. > > Should i post in

Re: [yocto] Parse error: unable to parse line and new error arm-linux-gnueabi-gcc : helloworld.cpp 'no such file or directory'

Thank you. By typing the code again the eroor solved. but an another error. Should i post in new mail or here is ok. error: ERROR: helloworld-1.0-r0 do_compile: Function failed: do_compile (log file is located at /home/cc/src/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi

Re: [yocto] Parse error: unable to parse line

The line is parsed here. Did you copy paste the quote from a tutorial on internet? Sometime encoding lead to such issues. On Thu, 2017-03-30 at 11:00 +0200, Yuvarajesh Valleru wrote: > No, > Sorry. I haven't left it. The please find the file below: > SUMMARY = "hello world program" > HOMEPAGE = "h

Re: [yocto] Parse error: unable to parse line

Hi, Thank you and sorry. But i haven't miss the braces in the .bb file. Am 30.03.2017 um 10:57 schrieb Fabien Lahoudere: On Thu, 2017-03-30 at 10:14 +0200, Yuvarajesh Valleru wrote: Hi, I am new to yocto. I was building an example recipe 'helloworld' and have a parse error. but could not fi

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

On 30-03-17 10:57, Maxin B. John wrote: Hi, Thank you very much for these updates. Merged to master-next. Note: from now on, please send the patches using "git send-email" as mentioned in the README file. That was my intention (of course) but I'm having some issues with Thunderbird icw "git

Re: [yocto] Parse error: unable to parse line

No, Sorry. I haven't left it. The please find the file below: SUMMARY = "hello world program" HOMEPAGE = "http://www.yoctoproject.org/"; SECTION = "network" LICENSE = "CLOSED" inherit qt4e SRC_URI = " \ file://helloworld.pro \ file://helloworld.cpp \ " S = "

Re: [yocto] Parse error: unable to parse line

On Thu, 2017-03-30 at 10:14 +0200, Yuvarajesh Valleru wrote: > Hi, > > I am new to yocto. I was building an example recipe 'helloworld' and  > have a parse error. but could not find the solution > > here is the error: > > cc@cc:~/src/oe-core/build$ bitbake helloworld > Loading cache: 100% |#

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

Hi, Thank you very much for these updates. Merged to master-next. Note: from now on, please send the patches using "git send-email" as mentioned in the README file. On Thu, Mar 30, 2017 at 08:28:09AM +0200, Jaap de Jong wrote: > > From d20c60ce51a399541329bd5360e5489f537d630b Mon Sep 17 00:00

Re: [yocto] Parse error: unable to parse line

On 30 March 2017 at 09:14, Yuvarajesh Valleru wrote: > SUMMARY = "hello world program" > HOMEPAGE = "http://www.yoctoproject.org/"; > SECTION = "network" > LICENSE = "CLOSED" > inherit qt4e > > SRC_URI = " \ > file://helloworld.pro \ > file://helloworld.cpp \ > " > > S = "${WORKDIR}"

[yocto] Parse error: unable to parse line

Hi, I am new to yocto. I was building an example recipe 'helloworld' and have a parse error. but could not find the solution here is the error: cc@cc:~/src/oe-core/build$ bitbake helloworld Loading cache: 100% || Time: 0:00:01 Loaded 3468 entries

Re: [yocto] [meta-raspberrypi][morty][PATCH 0/3] Stable branch kernel updates

On Tue, 14 Mar 2017 10:32:34 + Paul Barker wrote: > This series contains backports of patches from Khem's latest combined pull > request. I've boot tested a raspberrypi3 (4.4.y and 4.9.y kernels) and a > raspberrypi (4.9.y kernel) using these patches and all looks good. > > Khem Raj (1): >