Wednesday, 2020-02-19

*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC00:01
*** tolszak_ <tolszak_!> has quit IRC00:02
*** goliath <goliath!> has quit IRC00:03
*** gabrbedd <gabrbedd!> has quit IRC00:03
RPkanavin_home: ^^^00:05
RPnot sure if anyone has insight into what cflags.SH is doing :/00:05
* RP -> Zzzz00:05
*** gabrbedd <gabrbedd!> has joined #yocto00:06
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC00:07
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto00:08
*** vineela <vineela!~vtummala@> has quit IRC00:12
*** dreyna_ <dreyna_!> has quit IRC00:16
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC00:34
*** agust <agust!> has quit IRC00:48
*** leon-anavi <leon-anavi!~Leon@> has quit IRC01:13
*** armpit <armpit!~armpit@> has quit IRC01:57
*** kpo <kpo!> has quit IRC02:05
*** kpo <kpo!> has joined #yocto02:06
*** dreyna <dreyna!> has joined #yocto02:08
*** palate <palate!> has quit IRC02:31
*** palate <palate!> has joined #yocto02:32
yoctiNew news from stackoverflow: How to build debug libraries for Qt in Yocto SDK? <>02:42
*** wbn_ is now known as wbn02:42
*** wbn <wbn!~badegg@2607:5300:60:2ca::1> has joined #yocto02:43
*** JaMa <JaMa!~martin@> has quit IRC03:00
*** dqx <dqx!~dqx@unaffiliated/dqx> has quit IRC04:05
*** mccc <mccc!> has joined #yocto04:05
*** dqx <dqx!~dqx@unaffiliated/dqx> has joined #yocto04:07
*** Klox <Klox!> has joined #yocto04:23
*** dreyna <dreyna!> has quit IRC04:42
*** vmeson <vmeson!> has quit IRC04:57
*** vmeson <vmeson!> has joined #yocto04:57
*** armpit <armpit!~armpit@2601:202:4180:a5c0:103:47a6:6829:8136> has joined #yocto05:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC05:17
*** Klox <Klox!> has quit IRC05:42
*** Klox <Klox!> has joined #yocto05:49
*** jobroe <jobroe!~manjaro-u@> has joined #yocto06:05
*** pohly <pohly!> has joined #yocto06:20
*** hyper_dave <hyper_dave!~quassel@> has quit IRC06:26
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto06:27
*** hyper_dave <hyper_dave!~quassel@> has quit IRC06:30
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto06:32
*** kaspter <kaspter!~Instantbi@> has quit IRC06:34
*** kaspter <kaspter!~Instantbi@> has joined #yocto06:35
*** Klox <Klox!> has quit IRC06:40
*** hyper_dave <hyper_dave!~quassel@> has quit IRC06:41
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto06:42
*** moustafa <moustafa!c533555d@> has joined #yocto06:51
*** [Sno] <[Sno]!> has quit IRC06:51
*** guerinoni <guerinoni!> has joined #yocto07:07
*** frsc <frsc!> has joined #yocto07:11
*** TobSnyder <TobSnyder!> has joined #yocto07:18
*** opennandra <opennandra!> has joined #yocto07:23
*** OnkelUlla <OnkelUlla!> has quit IRC07:26
*** OnkelUlla <OnkelUlla!> has joined #yocto07:26
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has quit IRC07:26
*** shoragan <shoragan!> has joined #yocto07:27
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto07:27
*** [Sno] <[Sno]!~sno@> has joined #yocto07:33
*** wallthar <wallthar!c34bb392@> has joined #yocto07:34
*** agust <agust!> has joined #yocto07:36
*** m1ster_r0b0t <m1ster_r0b0t!> has quit IRC07:48
*** orzen <orzen!> has quit IRC07:48
*** vmeson <vmeson!> has quit IRC07:50
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto07:53
*** zeddii <zeddii!> has quit IRC07:54
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto07:54
*** paulg <paulg!> has quit IRC07:54
*** mckoan|away is now known as mckoan07:58
*** fl0v0 <fl0v0!~fvo@> has joined #yocto08:01
*** goliath <goliath!> has joined #yocto08:03
*** yacar_ <yacar_!> has joined #yocto08:05
*** orzen <orzen!> has joined #yocto08:05
*** stwcx <stwcx!~stwcx@2604:880:a:6::c9c> has quit IRC08:07
*** locutus_ <locutus_!~LocutusOf@> has joined #yocto08:08
*** locutus_ <locutus_!~LocutusOf@> has joined #yocto08:08
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC08:10
*** jobroe <jobroe!~manjaro-u@> has quit IRC08:11
*** jobroe <jobroe!~manjaro-u@> has joined #yocto08:12
*** locutus__ <locutus__!~LocutusOf@> has joined #yocto08:23
*** perdmann <perdmann!a5e14925@gateway/web/cgi-irc/> has quit IRC08:25
*** locutus_ <locutus_!~LocutusOf@> has quit IRC08:26
*** orzen <orzen!> has quit IRC08:27
LetoThe2ndkanavin_home: i can donate an ec2 instance for some hours or days in case of emergency.08:27
*** locutus_ <locutus_!~LocutusOf@> has joined #yocto08:31
*** locutus__ <locutus__!~LocutusOf@> has quit IRC08:32
*** nohit <nohit!sid334887@gateway/web/> has quit IRC08:34
*** zeddii <zeddii!> has joined #yocto08:34
*** tardyp <tardyp!sid45259@gateway/web/> has quit IRC08:35
*** rsalveti <rsalveti!sid117878@gateway/web/> has quit IRC08:35
*** tardyp <tardyp!sid45259@gateway/web/> has joined #yocto08:37
*** ric96 <ric96!sid234506@gateway/web/> has quit IRC08:37
*** freeuser <freeuser!c5ee3deb@> has joined #yocto08:37
*** khem <khem!~khem@unaffiliated/khem> has quit IRC08:37
*** lfa <lfa!~lfa@> has joined #yocto08:37
*** nohit <nohit!sid334887@gateway/web/> has joined #yocto08:37
*** rsalveti <rsalveti!sid117878@gateway/web/> has joined #yocto08:37
freeuserhello, I have a question about yocto and SDK. If I add a library ( called LIB for example ) to my image, it will be generated automaticaly with the SDK ? or I should add it manualy to SDK before bitbake it ?08:37
*** ric96 <ric96!sid234506@gateway/web/> has joined #yocto08:38
*** yann <yann!> has joined #yocto08:38
*** locutus_ <locutus_!~LocutusOf@> has quit IRC08:40
LetoThe2ndfreeuser: if something is in the image, it is automatically also included in the sdk08:42
*** Bunio_FH <Bunio_FH!> has joined #yocto08:43
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto08:43
*** goliath <goliath!> has quit IRC08:43
freeuserLetoThe2nd okey, than, if I want to use this SDK to compile a program which needs this LIB , should I add the include directorie path and the .LIB path to the configuration of my project ? Or just use the SDK ? I am confused about that because SDK contains all the headers and the libraries of LIB08:44
freeuseras I guess08:45
LetoThe2ndfreeuser: "jsut use the sdk"08:45
LetoThe2ndthat exactly what the environment setup script of the sdk is for, getting all the paths and flags right08:45
qschulzfreeuser: and if that does not work, most likely your cmake/makefile/whatever buildsystem you're using is messing with the flags and you should fix this and not yocto :)08:45
LetoThe2ndyour project on the other hand is supposed to properly handle such08:46
LetoThe2ndqschulz: dang you were faster08:46
LetoThe2ndfreeuser: and, for reasons unknown, this is almost the thing that i'll be talking about tonight in the live coding session :)08:46
*** dexterlb <dexterlb!> has quit IRC08:46
LetoThe2ndif i happen to have overtime i can even look at the sdk. yet there is already an episode that explains in-target vs. sdk vs. esdk, so be sure to watch it.08:47
freeuserLetoThe2nd qschulz okey thank you very much08:48
*** dexterlb <dexterlb!> has joined #yocto08:49
*** wallthar <wallthar!c34bb392@> has quit IRC08:49
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto08:51
*** yann <yann!> has quit IRC08:52
*** locutus_ <locutus_!~LocutusOf@2001:b07:5d32:c012:804e:5376:3822:b356> has joined #yocto08:56
freeuserLetoThe2nd thanks09:07
freeuserqschulz as you have mentioned, when I try to use SDK withoud specifying the path of includes and libraries, CMake project can not find the headers I need09:08
*** alessioigor <alessioigor!25a1a2d7@> has joined #yocto09:11
yoctiNew news from stackoverflow: simlink in eSDK sysroot points to a non existent path <>09:13
LetoThe2ndfreeuser: the sdk comes with the env setup script for a reason.09:15
freeuserLetoThe2nd I have sourced the env setup script on the machine which holding the sdk. And I added than the path of the SDK without adding the includes and lib paths09:17
LetoThe2ndfreeuser: i don't think thats right.09:18
LetoThe2ndfreeuser: you have source it not somewhere, but in the very shell session that you want to build in.09:18
freeuserLetoThe2nd My SDK is located on my machine A. I use the path of this SDK on my machine B. So I need to source it on my machine B instead of A ?09:20
*** tolszak_ <tolszak_!> has joined #yocto09:20
LetoThe2ndyou have to source it in the exact session that you want to build in, no matter where it runs.09:21
LetoThe2ndand if you have diverging pathes to the install location, then you are doomed anyways.09:22
freeuserLetoThe2nd I will make a try09:22
LetoThe2ndin general i'd say, the sdk is meant to be install and used on the same instance (for instance being any kind of linux environment)09:22
*** goliath <goliath!~goliath@> has joined #yocto09:23
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto09:24
*** gabrielssanches <gabrielssanches!51d83be2@> has joined #yocto09:25
*** stwcx <stwcx!~stwcx@> has joined #yocto09:26
*** gabrielssanches <gabrielssanches!51d83be2@> has quit IRC09:27
*** paulg <paulg!> has joined #yocto09:29
*** locutus_ <locutus_!~LocutusOf@2001:b07:5d32:c012:804e:5376:3822:b356> has quit IRC09:30
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@2001:b07:5d32:c012:804e:5376:3822:b356> has joined #yocto09:30
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto09:30
*** gabrielssanches <gabrielssanches!~gasa@> has joined #yocto09:32
*** alessioigor <alessioigor!25a1a2d7@> has quit IRC09:34
*** tomeccles <tomeccles!~tomeccles@> has joined #yocto09:36
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:41
yoctiNew news from stackoverflow: modemmanager gsm registration timeout <>09:43
*** freeuser <freeuser!c5ee3deb@> has quit IRC09:46
*** florian_kc is now known as florian09:52
*** NiksDev <NiksDev!~NiksDev@> has quit IRC09:58
*** NiksDev <NiksDev!~NiksDev@> has joined #yocto09:59
*** meego <meego!~meego@2001:41d0:fe7e:c800:34bd:eefb:2e34:bec6> has joined #yocto10:05
meegohas anyone kept tabs on which companies have cancelled their participation to Embedded World ? From what i can tell, ARM, Digikey and Arrow have cancelled already.10:07
*** JaMa <JaMa!~martin@> has joined #yocto10:09
mckoanmeego: AFAIK aldo ST, Xilinx and Atmel/Microchip10:11
*** orzen <orzen!> has joined #yocto10:12
yoctiNew news from stackoverflow: My CMake project using SDK can't find boost library <>10:13
JaMais git:// still supposed to be updated?10:24
JaMahalstead: hi, pulling from git:// and git:// gives different master branch now, is something broken or is there some expected delay/caching involved?10:27
JaMathe one is 82 commits newer10:28
halsteadJaMa: the domain is out of date and pointed at the wrong servers. I'll get that changed.10:29
*** guerinoni <guerinoni!> has quit IRC10:35
meegomckoan: perfect link, thanks. So NPXP & Renesas too… :/10:47
meego(typo: NPXP => NXP)10:48
JaMahalstead: thanks, I'll switch to new domain (I guess I've created this checkout very long time ago :))10:53
*** moustafa <moustafa!c533555d@> has quit IRC10:58
*** Gintaro <Gintaro!~gintaro@2a00:8080:10:148:9017:2cff:fe26:adf0> has quit IRC11:06
*** Gintaro <Gintaro!~gintaro@2a00:8080:10:148:9017:2cff:fe26:adf0> has joined #yocto11:10
*** dv|2 <dv|2!~dv@> has joined #yocto11:10
dv|2I have strange error trying to build SDK: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/disk2/build.24/tmp/work/tppg2-tps-linux-gnueabi/img-sp-tssz/1.0-r1/sdk/image/opt/tps/2.7-20200219/sysroots/x86_64-tpssdk-linux/usr/lib/locale11:15
*** luneff <luneff!~yury@> has joined #yocto11:15
*** berton <berton!~berton@> has joined #yocto11:46
*** berton <berton!~berton@> has quit IRC11:49
*** berton <berton!~berton@> has joined #yocto11:50
*** bachp <bachp!bachpmatri@gateway/shell/> has quit IRC11:51
*** bachp <bachp!bachpmatri@gateway/shell/> has joined #yocto11:55
*** yacar_ <yacar_!> has quit IRC12:01
*** Zajc <Zajc!> has quit IRC12:03
*** Zajc <Zajc!> has joined #yocto12:06
*** dev1990 <dev1990!> has joined #yocto12:17
*** OnkelUlla <OnkelUlla!> has quit IRC12:19
*** OnkelUlla <OnkelUlla!> has joined #yocto12:19
*** yacar_ <yacar_!> has joined #yocto12:19
*** dev1990 <dev1990!> has quit IRC12:23
*** fbre <fbre!91fdde45@> has joined #yocto12:23
fbreHi, my yocto user space program calls uint8_t* data = (uint8_t*)mmap((void*)0, desired_total_data_size, PROT_READ | PROT_WRITE, MAP_PRIVATE | MAP_ANONYMOUS | MAP_HUGETLB | MAP_HUGE_2MB, -1, 0);  and I get a null pointer as valid memory address. Is this a known issue? AFAIK mmap should only return null pointers if I set the MAP_FIXED flag.12:25
*** PinkSnake <PinkSnake!51ff1123@> has joined #yocto12:27
PinkSnakeHi all, i'm stuck on samba config (Checking for system pyldb-util.cpython-37m-aarch64-linux-gnu (>=1.5.6 <=1.5.999)  : not found) and I don't understand the issue :S any help ? :)12:28
*** tgamblin <tgamblin!> has quit IRC12:32
*** fbre <fbre!91fdde45@> has quit IRC12:32
*** fbre <fbre!91fdde45@> has joined #yocto12:37
*** PinkSnake <PinkSnake!51ff1123@> has quit IRC12:38
*** PinkSnake <PinkSnake!51ff1123@> has joined #yocto12:40
mckoanfbre: perhaps OT12:50
LetoThe2ndits at least not exactly yocto inself. but if somebody happens to know :)12:55
fbreI just thought it's a known issue within the yocto distro or something12:57
LetoThe2ndfbre: i highly doubt that its caused by the distro in itself, rather than maybe some kernel config or security measurement that you added.12:58
*** fbre <fbre!91fdde45@> has quit IRC13:01
*** fbre <fbre!91fdde45@> has joined #yocto13:02
tlwoernerarmpit: is there a non-zero chance of a patch being applied to 2.4-rocko or 2.3-pyro?13:12
*** hyper_dave <hyper_dave!~quassel@> has quit IRC13:14
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto13:16
*** vmeson <vmeson!~rmacleod@> has joined #yocto13:17
*** hyper_dave <hyper_dave!~quassel@> has quit IRC13:21
*** hyper_dave <hyper_dave!~quassel@> has joined #yocto13:24
*** tgamblin <tgamblin!~tgamblin@> has joined #yocto13:24
zeddiiRP: fixed that on target module issue.  build 929 looks better. what (if any) were the known failures ?13:30
RPzeddii: no idea at this point13:35
*** yann <yann!> has joined #yocto13:36
*** yann <yann!> has quit IRC13:46
*** opennandra <opennandra!> has quit IRC13:48
RPzeddii: suspect we just need to retest13:58
zeddiiI started a second build to see what I get without my changes.13:58
RPzeddii: that looks like master, couldn't you just compare with last nights build?13:59
RPzeddii: master should be ok?13:59
zeddiiI had meant to push one fix, but yah, I see that it is just master now. I’ll stop that build and find one of the others to check.14:00
*** banoli <banoli!~cpastore@> has quit IRC14:01
*** maudat <maudat!~moda@> has joined #yocto14:07
zeddiiI can never figure out where to pull the settings out of those builds, is there a tab that I'm not clicking that I should to see the machine and other conf values ? or should I be cloning a config repo ?14:09
*** stephano <stephano!> has joined #yocto14:13
RPzeddii: look at the stdio log14:14
RPJPEW: that last perl determinism thing looks like a makefile race in the end :/14:15
RPzeddii: I want to improve the autobuilder output but until the current day to day issues get sorted I don't have the bandwidth :/14:19
*** ericch <ericch!> has joined #yocto14:27
*** comptroller <comptroller!> has quit IRC14:28
*** comptroller <comptroller!> has joined #yocto14:31
JPEWRP: Ugh, perl14:37
RPJPEW: yes, I've filed it upstream14:39
RPJPEW: nice to understand it at least14:39
sveinseWhat is the correct ownership for installed files with in yocto recipes? 0.0 ?14:40
RPsveinse: usually, yes14:40
sveinseIs do_install running under a UID=0-ish environment? Thus allow me to use $USER as the UID to use?14:42
RPsveinse: its running under pseudo which fakes a root like environment14:46
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC14:52
*** yann <yann!> has joined #yocto14:53
sveinseRP: Do you have to do anything special to enable pseudo on install or is it enabled by default? If I run 'id' in do_install() I get "uid=0(root) gid=0(root) groups=0(root)" which is as expected, yet a "mkdir -p" on the next line produces dirs with my user uid and gid. Any ideas what I can do?14:54
qschulzWhat's that AUH mail on the ML?14:57
*** jobroe <jobroe!~manjaro-u@> has quit IRC14:57
*** PinkSnake <PinkSnake!51ff1123@> has quit IRC14:58
RPsveinse: in the do_install try a "ls -la" and see what that says?14:59
RPsveinse: obviously it can't really make things owned by root so you have to check under the fake environment14:59
RPqschulz: Automated Update Helper15:00
qschulzRP: yes, but what's the purpose of this mail?15:04
qschulzIs there anything to be done? Was anything done? E.g. is this something which updates recipes if upstream's been updated and test a build? In which case success are actual commits made and pushed somewhere? the fails have to be investigated yes, no? I understand this is useful to you/maintainers but it feels very "out-of-the-blue" and out of context for me, basic user :)15:06
sveinseRP: ah yes, of course, sorry I should of thouht of that. Thanks.15:08
*** fbre <fbre!91fdde45@> has quit IRC15:09
zeddiiRP: potentially stupid question, but can the testimage run be made to use slirp via some setting I'm not seeing ? my local multilib test image effort is failing at tap creation.15:13
* zeddii cracks open the class15:14
* zeddii finds TEST_RUNQEMUPARAMS15:17
RPqschulz: the listed maintainers get email with the output of the system which they're meant to do something with15:18
RPqschulz: that mailing list gets a summary of what happened15:18
*** luneff <luneff!~yury@> has quit IRC15:18
qschulzRP:  could a little bit more context be added at the top of the mail so that everyone has your answer? Also, why not post what the maintainers receive in that mail as well? Package upgrades could be a beginner task right? I guess some patches could be more or less straightforward?15:20
qschulzRP: thanks for the answer btw15:20
RPqschulz: yes we could add something to it. Patches welcome or a bug to do that(maybe with proposed text)15:20
zeddiicrap. I can't run the multlib test on my builders.15:20
RPqschulz: typically we've not spammed the list with the patches but perhaps we should15:21
zeddiino X installed and there probably won't be. hmmm.15:21
* zeddii tries nographic on the qemu params15:21
RPzeddii: we don't use slirp by default since its a major pain for various reasons. People have tried to make it work, I'm unaware of anyone who succeeded15:21
zeddiiI only use slirp :D15:21
* zeddii loathes tuns and taps15:22
RPwe've gotten a long way using them on the autobuilder15:22
zeddiibut yah. doesn't look like slirp will work for the run, it just failed to get an ip. that rules out my builders for now. I'll have to ponder.15:23
*** goliath <goliath!~goliath@> has quit IRC15:23
* RP gives marka a stern stare15:26
*** banoli <banoli!~cpastore@> has joined #yocto15:28
qschulzRP: is there any link to gstreamer ML/github for the setcap patch? (I see it's upstream-status = pending but missing a URL somewhere)15:32
fraywe all give marka stern stares..15:32
RPfray: he broke the build ;-)15:32
frayok, and even more stern stare then15:32
RPqschulz: Pending means we need to submit so its not there15:32
qschulzRP: /me facepalms15:33
RPqschulz: I'd love someone with better meson knowledge or better upstream knowledge to submit it...15:40
LetoThe2ndlive coding session about to start in 20 minutes! :-)15:40
qschulzRP: none here unfortunately :(15:40
RPqschulz: That patch is the sum of my meson experience ;-)15:43
qschulz(I meant, *I* don't have any knowledge in that)15:45
RPqschulz: right, I'm just meaning it isn't hard to pick up...15:47
qschulzOh, I smell good stuff in Mark's mail. I'll read tomorrow morning with a fresh and rested brain.15:48
*** guerinoni <guerinoni!> has joined #yocto15:52
*** TobSnyder <TobSnyder!> has quit IRC15:53
LetoThe2ndlive coding session about to start in 5 minutes! :-)15:55
LetoThe2ndqschulz: thx.15:56
sveinseWhat can I do if I get install error on a image. "Package packagegroup-product-base required crda, but none not the providers can be installed", yet crda is built and is available. How can I debug this?15:56
qschulzsveinse: there usually is a bit more messages i think15:57
sveinseqschulz: Only solution proposals removing my package groups (which I need)15:57
mcfrisksveinse: check that packagegroup is not mixing recipe and binary package names. DEPENDS is for recipe names, RDEPENDS is for binary package names.15:58
paulbarkersveinse: I've ran into this recently, the error messages from opkg aren't always very helpful. What distro and branch are you using?15:58
sveinsepaulbarker: zeus, but custom distro overlay on poky16:00
paulbarkerIf it's the same as I saw on thud with Arago distro, the root cause is wireless-regdb and wireless-regdb-static conflicting16:00
sveinseI assume there is a dependency missing or conflicting that I need to hunt down somehow16:01
sveinsepaulbarker: right, I'll check that, thanks16:01
paulbarkercrda depends on wireless-regdb16:01
qschulzLetoThe2nd: o/16:01
*** gasa <gasa!~gasa@> has joined #yocto16:02
sveinsepaulbarker: in my system wireless-redb RPROVIDES wireless-regdb-static it seems16:04
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC16:05
*** gabrielssanches <gabrielssanches!~gasa@> has quit IRC16:06
sveinsepaulbarker: but you're right: I removed crdb from my top-level packagegroup and now it installs. In the resulting image I've got wireless-regdb-static, so something pulls that in. Thanks!16:07
paulbarkerI guess crda isn't needed any more with recent kernels but tbh I've not looked into it too deeply16:09
paulbarkersveinse: looks like they still conflict on master:
markafray: RP: unfortunately I deserved the stares16:11
markaI will try to make up for it16:12
*** rcw <rcw!~rcw@> has joined #yocto16:14
*** Bunio_FH <Bunio_FH!> has quit IRC16:16
*** vineela <vineela!vtummala@nat/intel/x-dlzcsghrgukjsjul> has joined #yocto16:16
*** OnkelUlla <OnkelUlla!> has quit IRC16:27
RPmarka: its all too easily done16:27
*** JaMa <JaMa!~martin@> has quit IRC16:29
*** frsc <frsc!> has quit IRC16:31
* zeddii hands marka a paper bag16:33
zeddiiRP: looks like I misread that multilib failure. I didn't realize it was running more than one multlib test. bugger. I couldnt' even make the simple one work.16:34
RPzeddii: most of the builds run a succession of different tests16:35
RPzeddii: it should print the config for each one16:35
zeddiiyah, I noticed that after doing the first one. the error implies it is the last one that blew up. which I think may be my old friend mips6416:35
RPzeddii: thinking about it I think I can make this output easier to use16:36
zeddiiah yes. 6c is mips 64. I'll try that here, and then ping our mips64 friends if it isn't obvious.16:37
markazeddii: the paper bag got wet and now I am trapped16:37
zeddiibetter than plastic, you'll survive (and the eco warriors won't come for you).16:37
*** goliath <goliath!> has joined #yocto16:37
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC16:40
qschulzLetoThe2nd: o/16:43
mckoanqschulz: LOL16:44
khemRP: I was looking at latest binutils patch from you on nativesdk relocation, this code has changed upstream16:45
*** guerinoni <guerinoni!> has quit IRC16:45
khemRP: see;a=commit;h=ef8f08ca13f6c111cc549a3e13be5c5e2d95ca8216:46
*** yacar_ <yacar_!> has quit IRC16:47
khemRP: bug is here
yoctiBug 25477: was not found.16:48
RPkhem: hmm, interesting. I wonder if that helps us or not16:48
khemI wonder if we need your patch still16:48
RPkhem: I suspect prefix won't relocate to where we need it :(16:49
khemprefix is from --sysroot I believe ?16:50
khemin that relocation patch hardcodes it to -DSYSCONFDIR which might break --sysroot logic16:51
RPzeddii: going forward, builds will be like where the step1b log has the config at the start16:51
RPkhem: --sysroot is not what we want here16:51
RPkhem: we want the build sysroot, not the target16:51
khemright, my question is how it is supposed to work16:52
khemI see16:52
RPkhem: right, I only changed the build we needed to change16:53
khemand nativesdk will always be relocated16:53
khemunless folks install it once and then copy the install tree around16:53
RPkhem: if they do that other things will break16:53
RPkhem: we really need to talk to the gcc people about what we need and how to do it all properly16:54
*** Bunio_FH <Bunio_FH!> has joined #yocto16:54
khemyeah perhaps GNU couldron attendence will help16:55
khemall GNU toolchain folks are there16:55
RPkhem: hmm, paris in June16:56
LetoThe2ndmckoan: thanks for the input!16:59
LetoThe2ndi know the topic was a bit unconventional today, but hopefully it helps the newcomers :)17:04
*** WillMiles <WillMiles!~Will@> has joined #yocto17:08
qschulzLetoThe2nd: there's always someone who will find value in your articles/videos, don't worry if it didn't attract many people or make people interact on the chat.17:09
LetoThe2ndqschulz: hehe, it was more meant as a reason why i chose to talk about it :)17:11
*** fl0v0 <fl0v0!~fvo@> has quit IRC17:11
LetoThe2ndqschulz: lately i conclude that most views accumulate on youtube anyways. i usually get 200 on a new video in the first week, or so.17:11
*** m1ster_r0b0t <m1ster_r0b0t!> has joined #yocto17:13
*** tomeccles <tomeccles!~tomeccles@> has quit IRC17:17
*** mihai <mihai!~mihai@unaffiliated/mihai> has quit IRC17:18
* RP spots how one of the mystery ab failures happens 17:21
*** nayfe <nayfe!uid259604@gateway/web/> has quit IRC17:22
*** armpit <armpit!~armpit@2601:202:4180:a5c0:103:47a6:6829:8136> has quit IRC17:26
*** armpit <armpit!~armpit@2601:202:4180:a5c0:88be:17f0:935c:9e35> has joined #yocto17:28
*** MrETH <MrETH!~Goldcoin@> has joined #yocto17:46
*** [Sno] <[Sno]!~sno@> has quit IRC17:46
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC17:49
mckoanLetoThe2nd: YW17:49
*** mckoan is now known as mckoan|away17:50
*** dreyna <dreyna!> has joined #yocto17:51
*** LocutusOfBorg <LocutusOfBorg!> has joined #yocto17:57
*** LocutusOfBorg <LocutusOfBorg!> has quit IRC17:57
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto17:57
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:59
*** yann <yann!> has quit IRC18:00
*** comptroller <comptroller!> has quit IRC18:03
*** Sandrita <Sandrita!ade76a22@gateway/web/cgi-irc/> has joined #yocto18:06
*** locutus_ <locutus_!> has joined #yocto18:07
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC18:09
khemRP: sent a binutils 2.34 update patch give it a shot when AB is free18:10
*** vmesons <vmesons!~rmacleod@> has joined #yocto18:10
khemRP: I am running builds in parallel, its not DOA so far18:10
*** kpo <kpo!> has quit IRC18:10
khemoh now I see a problem :)18:10
*** vmeson <vmeson!~rmacleod@> has quit IRC18:10
*** kpo <kpo!> has joined #yocto18:11
khemlibtool: Version mismatch error.18:11
RPkhem: I'll wait on the next version ;-)18:13
khemyes soonish18:15
khemthere are so many ways we build binutils18:16
*** Siva <Siva!48a3dc1a@> has joined #yocto18:16
*** ecclescake <ecclescake!~tomeccles@> has quit IRC18:19
*** leon-anavi <leon-anavi!~Leon@> has quit IRC18:20
*** comptroller <comptroller!> has joined #yocto18:20
kanavin_homeRP: I suppose there's nothing right now I need to look at?18:21
*** fitzsim <fitzsim!> has joined #yocto18:21
kanavin_homeI can't do anything from work yet, and should be careful with doing yocto stuff at home as family is not keen on that :)18:22
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto18:22
JPEWRP: Would you mind doing a build of meta-mingw/master-next on the AB when it is convenient?18:23
*** ecclescake <ecclescake!~tomeccles@> has joined #yocto18:26
*** Siva <Siva!48a3dc1a@> has quit IRC18:26
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC18:27
*** hpsy <hpsy!~hpsy@> has quit IRC18:28
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto18:31
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto18:32
*** locutus_ <locutus_!> has quit IRC18:32
armpitJPEW, meta-mingw master-next build finished 40 minutes ago for that  branch. do you need another build?18:32
armpitJPEW, ah so you want the gcc changes18:33
*** meego <meego!~meego@2001:41d0:fe7e:c800:34bd:eefb:2e34:bec6> has quit IRC18:33
*** gtristan <gtristan!~tristanva@> has quit IRC18:34
RPkanavin_home: Nothing urgent, just the general bug backlog now....18:34
RPJPEW: running18:35
RParmpit: that was earlier to test a fix I pushed there18:35
JPEWRP: Thanks!18:35
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC18:36
JPEWRP: What was the mystery failure?18:36
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC18:36
*** yann <yann!> has joined #yocto18:37
RPJPEW: the _signal_ one from selftest18:37
RPturned out to be our broken code :(18:37
* RP is in the process of deleting it18:37
RPkanavin_home and rburton would be proud18:37
*** pohly <pohly!> has quit IRC18:39
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:47
* RP suspects he couldn't get away with deleting the svn fetcher18:48
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:48
paulbarkerRP: Sadly I've still got clients using that18:51
paulbarkerAt least it's not p418:52
RPpaulbarker: I wish the people use it would fix it and send patches and maybe improve the test suite18:52
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:238d:84be:b349:9184> has quit IRC18:54
*** yann <yann!> has quit IRC18:56
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:238d:84be:b349:9184> has joined #yocto18:56
paulbarkerRP: I'm a bit limited with what I can do with this one but I may be able to at least run the test suite in their context18:56
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto18:57
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:238d:84be:b349:9184> has quit IRC18:59
*** kanavin_home <kanavin_home!~ak@2a02:2450:1011:56f:238d:84be:b349:9184> has joined #yocto19:00
*** FrazerClews <FrazerClews!> has quit IRC19:00
*** guerinoni <guerinoni!> has joined #yocto19:01
*** opennandra <opennandra!> has joined #yocto19:05
RPJPEW: Is still an issue or not with the various patches?19:06
yoctiBug 13733: normal, Medium+, 3.1 M3, JPEWhacker, NEW , Reproducibility issue in perl on ubuntu160419:06
*** grumpydad <grumpydad!> has joined #yocto19:12
khemRP: do you have a binutils build handy for x86_64 ?19:14
JPEWRP: That was the encode modules using host compiler to determine how to generate code19:14
khemI need to see output of <cross>-ld -m1 for x86_64 cross binutils on master if anyone has handy19:15
RPkhem: yes19:16
JPEWRP: So I believe it's fixed. I believe all the perl reproducibility bugs I'm aware of have been fixed19:16
RPJPEW: that was my thought too. We could probably close that one then19:16
RPJPEW: thanks, I'll close? (or you can?)19:17
JPEWRP Will do19:17
khemRP: I am trying to get rid of patch for enabling pe targets so if you have ld built on master and can see what says with ld -m1 will help me19:17
*** ningauble <ningauble!> has joined #yocto19:18
RPkhem: ./recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-ld: unrecognised emulation mode: 119:18
RPSupported emulations: elf_x86_64 elf32_x86_64 elf_i386 elf_iamcu elf_l1om elf_k1om i386pe i386pep19:18
*** grumpydad <grumpydad!> has quit IRC19:20
khemRP: perfect thanks19:22
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC19:23
*** vmesons <vmesons!~rmacleod@> has quit IRC19:25
khemRP: sent V2 now19:28
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:30
*** opennandra <opennandra!> has quit IRC19:32
*** LocutusOfBorg <LocutusOfBorg!> has joined #yocto19:43
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto19:43
*** JBook_SE <JBook_SE!a434f282@gateway/web/cgi-irc/> has joined #yocto19:48
khemRP: wait for v3 now I am seeing a target build fail19:51
JBook_SEQuestions for anyone that wants to answer, what are some best practices for dealing with remote crashes of application software on embedded systems? Our product unfortunately gives 0 info not a core dump... Nothing so I'm looking for ideas on how this is typically handled, shipping binaries with symbols so a core can be recovered? We are using19:53
JBook_SEyocto not sure if that helps.19:53
*** vdehors <vdehors!> has quit IRC19:53
*** vdehors_ <vdehors_!> has joined #yocto19:53
milloniis there a simple way to delete those bits of sstate cache that haven't been touched in a long time?19:56
millonitrying to free up some space19:56
kanavin_homemilloni: find -atime19:57
milloniwill removing random bits like that not break it though?19:57
kanavin_homeno, if you are not running any builds at the same time19:57
milloniok, great19:57
kanavin_homeJBook_SE: reproduce the crash locally would be the first step19:59
milloniJBook_SE: when reproducing the crash, you might want to change the configuration so that you get the info that you need20:02
milloni(enable coredumps, debug symbols etc)20:02
millonii would say it's useful to have a "debug" variant of your product to use for stuff like this20:03
millonithere are ways to do that in yocto20:04
*** stephano <stephano!> has quit IRC20:04
milloniare you using poky? i know poky has some DISTRO_FEATURES that might be relevant here20:05
*** stephano <stephano!> has joined #yocto20:05
JBook_SEThanks for the input, we are trying to reproduce locally with a debug build but unfortunately it took something like 25 days of high activity to crash it the first time at the customer and we are struggling to reproduce20:07
JBook_SEI was thinking for the future how can this be avoided. we are using poky20:07
*** falstaff <falstaff!~quassel@> has joined #yocto20:10
*** rubdos <rubdos!> has quit IRC20:10
JBook_SEmilloni the DISTRO_FEATURES you mention is there quick link to some documentation on these?20:11
milloniJBook_SE: yeah if you google it it should come up with something20:12
LetoThe2ndJBook_SE: have a look at minicoreedumper, which is in meta-oe.20:12
milloniin my experience customers are often bad at using yocto :)20:12
*** stephano <stephano!> has quit IRC20:13
*** stephano <stephano!> has joined #yocto20:13
LetoThe2ndJBook_SE: i don't think theres a DISTRO_FEATURE around that you can use, you would have to introduce it yourself for your usecase20:13
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC20:14
JBook_SEminicoredumper looks very much like what we need20:15
JBook_SEmilloni LetoThe2nd thanks for the input and help20:15
LetoThe2ndJBook_SE: have fun20:16
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:20
*** orzen <orzen!> has quit IRC20:21
*** guerinoni <guerinoni!> has quit IRC20:21
*** rubdos <rubdos!~rubdos@2a02:578:859d:700:8b44:5716:382d:a7da> has joined #yocto20:23
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC20:24
RPThe number of weird races the autobuilder finds continues to amaze me :(20:24
tgamblinRP: more quirks with running/stopping QEMU?20:25
yoctiBug 13803: normal, Undecided, ---, unassigned, NEW , devtool setupClass file copying race20:25
*** vmeson <vmeson!> has joined #yocto20:31
*** opennandra <opennandra!> has joined #yocto20:33
*** OnkelUlla <OnkelUlla!> has joined #yocto20:45
*** [Sno] <[Sno]!> has joined #yocto20:48
*** gsalazar <gsalazar!~gsalazar@2001:818:e633:c100:83a0:92b7:67ab:e154> has joined #yocto20:52
*** jani191 <jani191!> has joined #yocto21:11
*** opennandra <opennandra!> has quit IRC21:14
jani191I'm working with NXP iMX8QXPMEK evaluation board.  I downloaded bsp release L4.19.35_1.1.0_MX8QXP from following site:21:16
jani191This bsp release is for Yocto Project 2.7 (Warrior)21:16
jani191I built yocto project for this bsp release.  Then, I invoked following command to extract toolchain:21:16
jani191DISTRO=fsl-imx-xwayland MACHINE=imx8qxpmek bitbake core-image-minimal -c populate_sdk21:16
jani191A new folder is created in build/tmp/deploy/sdk21:16
jani191Inside sdk folder, there is filename:  fsl-imx-xwayland-glibc-x86_64-core-image-minimal-aarch64-toolchain-4.19-warrior.sh21:16
jani191I copied this script to /opt folder.  Then, I executed this script to install sdk.  I chose to have sdk installed in build/mysdk folder.  Inside mysdk folder, there is environment setup21:16
jani191script:  environment-setup-aarch64-poky-linux.  I ran this environment setup script to setup sdk environment.  What is the next step?  The files that were compiled by yocto project, do I21:16
jani191need to compile same set of files with sdk?  If yes, how?21:16
jani191Please provide detailed information in building linux image from sdk.21:16
jani191I read through 'Yocto Project Application Development and the Extensible Software Development Kit(esDK)' but didn't find any information on compiling source code from sdk.  I want to view same21:16
jani191set of source code files that were compiled when I created the yocto project.21:16
*** gsalazar <gsalazar!~gsalazar@2001:818:e633:c100:83a0:92b7:67ab:e154> has quit IRC21:23
RPjani191: usually you'd source that environment script and then use the compiler (CC), cflags and other settings to build your software21:25
jani191RP:  Where is the software?  In sdk, where are the set of files that were compiled by yocto project?21:26
RPjani191: the output is in the sdk (e.g. the libraries and headers) but not the original source, that would be in the original build21:29
*** tgamblin <tgamblin!~tgamblin@> has quit IRC21:32
jani191RP:  What is the use of sdk?21:33
JPEWjani191: The SDK is useful if you want to build software outside of Yocto. For example, we compile our proprietary applications with the SDK then copy them to the device for development21:34
*** berton <berton!~berton@> has quit IRC21:36
kanavin_homeRP: this patch has been dropped many times, but i have never got any feedback
*** comptroller <comptroller!> has quit IRC21:39
jani191I booted my target board with embedded Linux image built from yocto project.  I need to step through USB host source code in embedded Linux kernel.  Do I use sdk to create my development and debug environment?21:39
*** alinucs <alinucs!> has quit IRC21:39
*** alinucs <alinucs!> has joined #yocto21:41
*** yann <yann!> has joined #yocto21:42
*** alinucs <alinucs!> has quit IRC21:43
RPkanavin_home: its on my "not quite convinced its right or wrong" list21:47
RPkanavin_home: I think it depends how we define the image and I'm not sure we clearly did that21:47
jani191JPEW:    >> 'then copy them to the device for development'  Do you mean you integrate your proprietary applications with the Yocto Project and rebuild Linux image from Yocto Project for testing?21:47
*** Sandrita <Sandrita!ade76a22@gateway/web/cgi-irc/> has quit IRC21:48
kanavin_homeRP: not sure I follow you, but are you seeking something like three ptest images, one with only fast tests, another with fast+slow, and a third with the full set?21:53
kanavin_homebecause otherwise I'm not sure what the argument against the patch is. ptest-pkgs pulls in bash-ptests which is otherwise banned for being unstable, and it is entirely coincidental it does not pull in something from the blacklist that hangs21:55
*** comptroller <comptroller!> has joined #yocto21:56
RPkanavin_home: we have multiple conflicting requirements for that image. It was partly there to illustrate the ptest image feature but then I broke it with the fast/slow thing21:56
RPkanavin_home: Your patch is probably the right thing to do, I'm just not 100% sure21:57
*** dev1990 <dev1990!> has joined #yocto21:59
*** vineela <vineela!vtummala@nat/intel/x-dlzcsghrgukjsjul> has quit IRC22:00
*** maudat <maudat!~moda@> has quit IRC22:00
*** vineela <vineela!~vtummala@> has joined #yocto22:01
*** locutus_ <locutus_!> has joined #yocto22:02
kanavin_homeI am fully convinced that ptest-pkgs is actually harmful, as you never know what you end up with in the image and how long ptests will take :) explicit lists are the way to go22:02
JPEWjani191: Yes, our nightly builds and release builds are built completely in Yocto22:04
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC22:05
JPEWjani191: The SDKs are primarily used so that we don't need all developers to build up the complete image when all they care about is a single application22:05
JPEWjani191: Many can't anyway because they use Windows22:05
jani191JPEW:  I just want to make sure I understand.  When you compile your proprietary application with sdk, you cannot test it unless you integrate and build it with yocto project?22:07
JPEWjani191: No. The application built with the SDK can be copied over to the target and run as you would any other application22:09
JPEWjani191: That's sort of the purpose of the SDK :)22:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto22:10
JPEWjani191: It's just that the (traditional) SDK can't build up a whole image, and when it comes time to release, attempting to shove together an application built with the SDK and an image built with Yocto is complicated (beleive me, I've tried :); it's easier to build the application in Yocto in the first place22:10
JPEWjani191: But, it also depends on your use cases; one of the great things about Yocto is that it can support a lot of different ways of building up embedded systems22:12
jani191JPEW:  >> 'copied over to the target and run as you would any other application'     so application built in sdk can run in target without uboot, kernel, and file system?22:14
*** WillMiles <WillMiles!~Will@> has quit IRC22:15
RPkanavin_home: well, yes, but it should match the ptests to the contents of your image22:15
mischiefi currently have a need to make fit images differently from how yocto does it now. i need to do it as part of image generation and not as a task in the kernel recipe. what is the right way to depend on the kernel from a recipe? DEPENDS = "kernel-vmlinux" ?22:18
*** locutus_ <locutus_!> has quit IRC22:19
*** LocutusOfBorg <LocutusOfBorg!> has joined #yocto22:20
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto22:20
RPmischief: depends which bit of the kernel you want to depend upon really22:20
RPDEPENDS += "virtual/kernel" is one way22:20
mischiefah, right. we have PREFERRED_PROVIDER_virtual/kernel set to our own kernel recipe.22:21
mischiefi need to make a fit image but i can't use kernel-fitimage.bbclass22:21
RP - /me wonders what will break next :(22:22
mischiefthe fit image i need to make is tied directly to the root filesystem, so i think it is appropriate to implement it as an image class - does that seem right?22:22
RPJPEW: that build was green btw22:22
RPmischief: that would seem reasonable (as an extra image type)22:23
mischiefok. we need this for dm-verity btw, where the root hash of the fs is inserted into the fit. yocto does not seem to cater to this case very well currently.22:24
* RP files a bug for the warning, its a race22:26
RPmischief: I'mnot very happy with the fit support, not least as there are no tests22:26
RPJPEW: ^^^22:29
* RP wonders how much of -next needs to drop because of that :(22:29
vmesonjani191: "so application built in sdk can run in target without uboot, kernel, and file system?" <-- Not typically22:30
*** comptroller <comptroller!> has quit IRC22:30
vmesonjani191: "so application built in sdk can run in target without uboot, kernel, and file system?" <-- Not typically+busybox+....)22:31
kanavin_homeRP probably just the wayland meson conversion patch22:32
vmesonjani191: your conversation with JPEW suggests that you'd need to deploy your app on top of core-image-minimal (uboot+linux-yocto+busybox+...)22:33
vmesonjani191: it's possible to build a 'bare-metal' system using yocto but that's not the typical workflow.22:34
RPkanavin_home: thanks22:34
vmesonjani191: see:
jani191vmeson:  >> you'd need to deploy your app on top of core-image-minimal (uboot+linux-yocto+busybox+...)     but the sdk that I setup doesn't have uboot + Linux + yocto + busybox?  All it has is libraries and headers?22:36
*** rcw <rcw!~rcw@> has quit IRC22:37
jani191vmeson:  core-image-minimal is in yocto.  sdk doesn't have it?22:38
*** yann <yann!> has quit IRC22:39
*** comptroller <comptroller!> has joined #yocto22:39
vmesonjani191: right, so you need to get the steps to boot core-image-minial from NXP if you don't have them already.22:40
*** d_s_e <d_s_e!~d.s.e@> has quit IRC22:41
jani191vmeson:  I created core-image-minimal from yocto and booted target from sdk card.22:41
*** d_s_e <d_s_e!~d.s.e@> has joined #yocto22:41
jani191vmeson:  My question is that I setup sdk by extracting toolchain from yocto project.  What does this sdk contain?22:42
vmesonjani191: okay (I'm not actually sure what an "sdk card" is... )22:42
jani191vemson:  soryy sd card22:43
khemRP: finally sent v3, which should work, please schedule that one for binutils22:43
jani191vmeson:  sorry sd card22:43
vmesonjani191: the sdk is a -software development kit- so it contain the compiler and various libraries and header files that you can link your application against.22:43
vmesonjani191: ah ha! -- that's a bad typo! :)22:43
jani191vmeson:  so if I build 'hello world' application in sdk.  The built binary image will only contain 'hello world' ?22:45
*** tgamblin <tgamblin!> has joined #yocto22:45
jani191vmeson:  The build binary image won't compile any other packages, such as uboot, kernel, and file system?22:46
vmesonjani191: correct.22:47
jani191vemson:  And I can run 'hello world' application in my target board?22:47
vmesonjani191: yes.22:47
jani191vmeson:  what will be the file extension of 'hello world' application?22:47
RPhalstead: autobuilder is getting quite the workout ;-)22:48
vmesonjani191: Of course you have to get the app to the target somehow... scp,or mount the SD card, or use rpm/ipk. there are many ways to do it.22:48
khemRP: thanks I will monitor it22:50
vmesonjani191: it depends on what you tell the compiler to call it. The -o flags takes any name! :)  I think you need to read some docs and maybe watch some introductory videos to learn a bit about Yocto.22:50
jani191vmeson:  ok.  So applications built in sdk run stand alone in target because sdk doesn't compile uboot, kernel, and file system packages?22:51
vmesonjani191: people seem to like the "Live Coding with Yocto Project #1: download and first build" series:
vmesonI haven't watched it since I've been using Yocto and doing embedded development for a while.22:52
jani191vemson:  Your help is much appreciated.22:53
vmesonjani191: spend a bit of time reading docs, watching these videos, do some tests and come back later this week. okay?22:53
jani191vmeson:  ok.  One more question22:54
vmesonjani191: sure, it's a big learning curve. We can help a bit but there's no subsitute for hands on experimentation.22:54
vmesonjani191: ok, but I'm going to have to charge you double for that one! :)22:54
jani191vmeson:  Applications built with sdk must run stand alone in target board because uboot, file system, and kernel aren't built in sdk?22:56
vmesonjani191: your question is too vague. If you ask if hello-world runs on top of core-image-minimal, then I can say yes but...22:57
jani191vmeson:  How can hello-world run on top of core-image-minimal when sdk doesn't build core-image-minimal?22:58
vmesonan application _could_ link agains other libraries that you also need to bring to the target. Try building core-image-minimal for qemux86-64 and then use 'runqemu'.22:58
vmesonyou'll learn loads!22:58
jani191vmeson:  >> Try building core-image-minimal for qemux86-64 and then use 'runqemu'.    build this from sdk?22:59
vmesonjani191: no, just follow the steps in the 'Yocto Project Quick Build' document that I just linked above.23:00
vmesonjani191: then you can take what you learn from there and figure out the sdk. okay?23:01
jani191vmeson:  ok but I already built yocto project for nxp board and I'm not getting the big picture on sdk.23:03
*** dv_ <dv_!> has quit IRC23:04
vmesonjani191: maybe some (Wind River specific) docs will help you get the big picture:
* vmeson wraps up for the day.23:08
RPjani191: think of the sdk as a standalone toolchain you could use for development, or you could use the full build environment instead. Some people need one, some people need the other23:10
*** Bunio_FH <Bunio_FH!> has quit IRC23:12
jani191RP:  By full build environment, I believe you mean yocto project.  Yocto project contains USB System and USB drivers in Linux kernel.  I have setup sdk from yocto project.  If I create USB application from sdk and load it in my target board, I can't test it because I don't have the kernel?  Kernel is in yocto build.  It's not in my USB application23:15
jani191I build from sdk?23:15
*** dv_ <dv_!> has joined #yocto23:16
jani191I'm not getting the point of sdk because the stand alone application created from sdk can't be tested because sdk doesn't create the framework or lower layers of software?23:17
RPjani191: presumably you have a kernel and rootfs image for your board. The SDK will contain some development headers. Whether there are enough headers there to do USB kernel dev work I'm not sure23:18
*** locutus_ <locutus_!> has joined #yocto23:18
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC23:18
jani191RP:  ok.  Thank you!23:19
jani191vmeson:  Thank you!23:19
jani191JPEW: and anyone else that helped me with SDK questions.  Thank you!  I appreciate the help.23:20
*** jani191 <jani191!> has quit IRC23:20
*** locutus_ <locutus_!> has quit IRC23:24
*** comptroller <comptroller!> has quit IRC23:34
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC23:41
*** comptroller <comptroller!> has joined #yocto23:49
*** agust <agust!> has quit IRC23:51
khemzeddii: we need to backport for perf to build with latest binutils23:57
khemzeddii: I am carrrying temporarily23:57

Generated by 2.17.2 by Marius Gedminas - find it at!