Re: [yocto] rocko cmake buld cstdlib:75:15: fatal error: stdlib.h: No such file or directory

2018-04-17 Thread Måns Zigher
Hi Dennis, This makes me a bot confused in cmake_do_configure we have -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 \ ${EXTRA_OECMAKE} \ -Wno-dev I would think that I am using this cmake_do_configure so then the -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 should already be called correct

Re: [yocto] [Yocto] Prelink compilation for ZCU102

2018-04-17 Thread Manjukumar Harthikote Matha
Hi Nicolas, Seems like there was a “fetcher failure”, can you make sure git proxy is set correctly for your network. If you are able to manually clone using the clone command found in the log.do_fetch of prelink recipe, then bitbake should also be able to clone without failures. Thanks, Manju

Re: [yocto] rocko cmake buld cstdlib:75:15: fatal error: stdlib.h: No such file or directory

2018-04-17 Thread Måns Zigher
Hi, I actually managed to locate the problem to the cmake project where it added include_directories(SYSTEM which then is translated into -isystem this call was not included when building in the SDK so that explained why this was only triggered when building with bitbake. Thanks for the tip I will

Re: [yocto] rocko cmake buld cstdlib:75:15: fatal error: stdlib.h: No such file or directory

2018-04-17 Thread Dennis Menschel
Hi Mans, Am 17.04.2018 um 13:15 schrieb Måns Zigher: > Hi all, > > Have anyone experienced this error message before? > > c++/7.3.0/cstdlib:75:15: fatal error: stdlib.h: No such file or > directory                        > |  #include_next                                           >

[yocto] Linux Files needed for PXE network boot

2018-04-17 Thread Raymond Yeung
I've a .hddimg image bootable from USB thumb drive. As part of the boot-up, I also could invoke "Serial Install" to transfer such an image to SSD, such that in the next round, I could boot from SSD instead. What are the files and where do I get them (relative to where I find .hddimg) from the

[yocto] Connecting to mysql/mariadb

2018-04-17 Thread Greg Wilson-Lindberg
I've got a Yocto system that I'm working on that has mysql/mariadb configured but I can't connect to it with MySQL Workbench from another machine. mariadb is running, the network connection is live, but when I try to connect using MySQL Workbench I get an immediate "connection refused" response.

Re: [yocto] compiling core-image-sato failure on 32 bits system

2018-04-17 Thread Burton, Ross
On 17 April 2018 at 15:03, Khem Raj wrote: > On Tue, Apr 17, 2018 at 3:13 AM, Burton, Ross wrote: >> If you've an i5 why are you running a 32-bit OS? Just so you're >> aware, it's practically impossible to build webkit on a 32-bit host >> because there just isn't enough memory available. >> > >

Re: [yocto] compiling core-image-sato failure on 32 bits system

2018-04-17 Thread Khem Raj
On Tue, Apr 17, 2018 at 3:13 AM, Burton, Ross wrote: > If you've an i5 why are you running a 32-bit OS? Just so you're > aware, it's practically impossible to build webkit on a 32-bit host > because there just isn't enough memory available. > you need 8G of RAM minimum or reduce your -j factor t

Re: [yocto] [Yocto] Prelink compilation for ZCU102

2018-04-17 Thread Mark Hatle
On 4/17/18 3:55 AM, Nicolas Salmin wrote: > Hello guys, > > Someone here have some information to build prelink recipe for ZCU102 board > because i'm not able to do it ... > > Hello guys, > > Someone here have some information to build prelink recipe for ZCU102 board > because i'm not able to do

[yocto] rocko cmake buld cstdlib:75:15: fatal error: stdlib.h: No such file or directory

2018-04-17 Thread Måns Zigher
Hi all, Have anyone experienced this error message before? c++/7.3.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory > > | #include_next > > > > |^~ > > I am not seeing this error when cross compiling using the sdk. I can see in the output that the -isy

Re: [yocto] compiling core-image-sato failure on 32 bits system

2018-04-17 Thread Burton, Ross
If you've an i5 why are you running a 32-bit OS? Just so you're aware, it's practically impossible to build webkit on a 32-bit host because there just isn't enough memory available. Ross On 17 April 2018 at 10:50, Stéphane Ancelot wrote: > > > Le 17/04/2018 à 09:08, Iván Castell a écrit : > > R

Re: [yocto] compiling core-image-sato failure on 32 bits system

2018-04-17 Thread Iván Castell
If dmesg message shows no crashes your problem seems not related with the CPU of your host (build) machine. You should investigate further about that "Segmentation Fault" ERROR message. What gcc version is installed in your host machine? Also, check /home/yocto/poky/build/tmp/work/i586-poky-linux/l

Re: [yocto] compiling core-image-sato failure on 32 bits system

2018-04-17 Thread Stéphane Ancelot
Le 17/04/2018 à 09:08, Iván Castell a écrit : Review "dmesg" output to see if there is some kernel crash in your host machine. Which CPU are you using to compile yocto (your host machine)?We also have been dealing with this kind of issues compiling with anAMD Ryzen 7 1700 Eight-Core Processor

[yocto] [Yocto] Prelink compilation for ZCU102

2018-04-17 Thread Nicolas Salmin
Hello guys, Someone here have some information to build prelink recipe for ZCU102 board because i'm not able to do it ... Hello guys, Someone here have some information to build prelink recipe for ZCU102 board because i'm not able to do it ... ERROR: prelink-1.0+gitAUTOINC+aa2985eefa-r0 do_unpa

[yocto] Can't able to locate sysroot folder

2018-04-17 Thread akshaya dalu
Hello, I am very much interested to work in yocto project . As a beginner I face some problems. Hope you give me a solution to my problem. * My basic need : * I want to run a sample hello world program in qemulator in eclipse IDE. *Work done so far by me : *I referred yocto documentation

[yocto] compiling core-image-sato failure on 32 bits system

2018-04-17 Thread Stéphane Ancelot
** *Hi,* * ** On my ubuntu bionic system 32 bits, compilation core-image-sato fails as follow; ** unfortunately nothing seems interesting in log*.*do_install. ** what can I do ? * Regards, Steph * ** Build Configuration: BB_VERSION = "1.36.0" BUILD_SYS = "i686-linux" NATIVELSBST