**** BEGIN LOGGING AT Wed Jul 10 03:01:22 2019 Jul 10 06:35:18 good morning Jul 10 06:46:04 Hello, I have run bitbake ok, but when runqemu with `runqemu qemux86 tmp/deploy/images/qemux86/core-image-minimal-qemux86.ext4`, I got error `runqemu - ERROR - Failed to run qemu: Could not initialize SDL(x11 not available) - exiting`. It seem likes this : https://lists.yoctoproject.org/pipermail/yocto/2013-April/013239.html. How to resolve this? T Jul 10 06:46:05 hanks! Jul 10 06:57:30 huynq: as stated in the answers to that email the issue depends on the missing packages into your host machine Jul 10 07:09:20 mckoan: I see, but my host machine has installed libsdl1.2-dev. Which packages I missed ? Jul 10 07:13:52 huynq: x11 not available means that you are probably conencted over ssh or such Jul 10 07:14:19 so, no x11, at least not directly. just add the 'nographic' parameter. Jul 10 07:31:12 LetoThe2nd: Great answer. The actual reason is by I'm invoking command from ssh. When I tried in direct machine, it works as well. Jul 10 07:32:21 huynq: :) Jul 10 07:33:42 LetoThe2nd: Thank you :) Jul 10 08:34:26 I use systemd drop-in, but after booting fresh image, systemctl restart X, says "files changed on disk, do daemon-reload", what am I missing ? Jul 10 08:36:54 Hi, is anyone know how to access and run BBCooker method generateTaskDepTreeData in cooker.py using poky 2.5? Jul 10 08:42:52 akrpic77: You should do as recommend: `sudo systemctl daemon-reload` Jul 10 08:44:01 huynq: why is that necessary ? I havent changed anything, and it's fresh bitbaked image booted for the first time Jul 10 08:45:07 I forgot to mention that i have my own python Tinfoil wrapper Jul 10 09:13:18 New news from stackoverflow: libc.so.6: error adding symbols: DSO missing from command line Jul 10 10:16:36 I cannot for the life of me get the native golang compiler included in my SDK when using "-c populate_sdk" Jul 10 10:16:40 Anyone know how? Jul 10 10:18:25 Error: "(...) rdepends upon non-existent task do_package_write_deb in /.../poky/meta/recipes-devtools/go/go-cross_1.10.bb" Jul 10 10:20:36 kristoiv: i'm just about to leave, but this should be doable through https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#sdk-adding-individual-packages Jul 10 10:20:45 kristoiv: speicifically, TOOLCHAIN_HOST_TASK Jul 10 10:21:01 https://www.yoctoproject.org/irc/%23yocto.2018-12-23.log.html#t2018-12-23T21:20:49 Jul 10 10:21:03 LetoThe2nd, I'm trying, but that is where I get my error Jul 10 10:22:09 Trying one of the other suggestions, TOOLCHAIN_HOST_TASK = "go-crossdk-aarch64" Jul 10 10:25:52 Looks like it might work with "go-cross-canadian-aarch64". Anyone can explain that x)? Jul 10 10:26:01 LetoThe2nd, thanks btw! Jul 10 11:53:10 Chrusel76: ping :) Jul 10 11:53:23 Chrusel76: glad you liked the show, and you made it here :) Jul 10 11:53:51 Chrusel76: actually there's little magic to it, just type your question and wait for something to happen. Jul 10 12:10:04 LetoThe2nd: ping :-) - i've got it (the communication thing) - thanks. Jul 10 12:13:28 Chrusel76: so, welcome! Jul 10 12:16:21 I'm still struggeling to get golang in my Yocto SDK. Using TOOLCHAIN_HOST_TASK = " go-cross-canadian-aarch64" I got the compiler itself, but the GOROOT is almost empty. No standard library at all... Jul 10 12:16:30 Anyone have experience doing this? Jul 10 12:17:13 I'm btw currently tring to add TOOLCHAIN_TARGET_TASK = " go go-dev" to see if that brings what I need Jul 10 12:17:19 But I'm just guessing Jul 10 12:33:56 Okay, new theory: I'm being stupid :D. go-cross-canadian-aarch64 + go-cross-canadian-aarch64-dev + go-cross-canadian-aarch64-staticdev, maybe that fixes it Jul 10 12:34:26 theres a packagegroup for that isn't there? Jul 10 12:34:27 kristoiv: i'm no pro there, but explicitly adding canadian or such just sounds wrong. Jul 10 12:34:41 kristoiv: packagegroup-go-cross-canadian? Jul 10 12:34:52 LetoThe2nd, what is "canadian" in this context? Jul 10 12:34:55 kristoiv: you probably want something that is rather called go-cross.... or what rburton just said Jul 10 12:35:17 the standalone go sdk is meta/recipes-core/meta/meta-go-toolchain.bb and just uses that packagegroup Jul 10 12:35:34 kristoiv: a canadian cross compiler means, that it was compiled on host triplet A, runs on host triplet B, and compiles for host triplet X Jul 10 12:35:39 s/X/C/ Jul 10 12:35:54 hence double-cross, nicknamed canadian-cross Jul 10 12:36:12 LetoThe2nd, Aha! Nice. Well that is wat we are doing only host and target are the same. But the package group may be good Jul 10 12:36:13 packagegroup-go-cross-canadian Jul 10 12:36:22 no actual canadians have been harmed in the making of this compilers, at least to my knowledge. Jul 10 12:36:56 kristoiv: you can build a SDK on host A for running on host B, so it is a canadian. just typically, A=B because typically they're both x86-64. Jul 10 12:37:10 unless you've one of the two arm boxes that is powerful enough :) Jul 10 12:37:10 rburton, exactly Jul 10 12:40:19 rburton, maybe I'm really looking for packagegroup-go-sdk-target? "Target packages for the Go SDK" Jul 10 12:40:58 kristoiv: look at meta-go-toolchain, it uses both. you need the native tools and target libs Jul 10 12:41:24 rburton, will do, thanks Jul 10 13:07:00 hi, I'm trying to create dual rootfs using wic file and also add data partition (is there some was in wic to tell --source should be some file or directory)? Jul 10 13:07:18 I cna create empty data partition but would like to be populated with some files Jul 10 13:08:02 rburton, LetoThe2nd, you guys are heroes! I finally have something that works great. However, in order to get my additions into the SDK of my target image I had to put these things in my local.conf. Is there a better way? How is meta-go-toolchain.bb supposed to be used? I didn't find that I could inherit it even so I copy/pasted the relevant TOOLCHAIN_*_TASK lines. Jul 10 13:11:14 kristoiv: just by judging from the recipe itself, i'd say copy-paste the TOOLCHAIN_* lines into the image recipe that you want to create the sdk for. Jul 10 13:11:47 LetoThe2nd, Good idea Jul 10 13:22:49 yes that Jul 10 13:42:23 halstead, thanks for committing the change Jul 10 13:44:02 New news from stackoverflow: recipe also produces -native output that needs packaging Jul 10 14:36:21 Do we document clearly anywhere the best practice for layers to only modify recipes when their relevant DISTRO, MACHINE or other flag is actually enabled? And to avoid setting things in layer.conf? Jul 10 14:36:35 I need something "official" I can point someone at Jul 10 14:36:51 LetoThe2nd: yesterday's video is now published on youtube. we are getting better ;) Jul 10 14:37:15 ndec: \o/ Jul 10 14:38:34 The `common.test_signatures` test in yocto-check-layer covers those best practices but if you don't understand what "recipes that change signatures" means then that isn't very clear Jul 10 14:39:01 ndec: i actually wonder if the 151 views for #1 are to be taken serious, or if that was crofton testing it a 100 times because he couldn't believe we finally made it :) Jul 10 14:40:02 probably somewhere in between. Jul 10 14:42:54 ndec: and, hooray: me and $COWORKER got travel permission for ELCE today. i'll annoy you all in real life then, not only through a tiny window on your screens! Jul 10 14:44:14 New news from stackoverflow: creating an npm based recipe for Yocto korgoth fails Jul 10 14:47:41 armpit, Sure. Should I respond to the list as well? Jul 10 14:47:54 nah Jul 10 14:49:11 halstead: thanks! Jul 10 14:54:15 aehs29: am I right in thinking you never tried libstdc++ with newlib? Its being asked about on the poky list but I'd guess we've never tried it Jul 10 15:44:22 New news from stackoverflow: Using Yocto with meta-balena causes a parse error Jul 10 16:44:32 New news from stackoverflow: Error executing a python function in exec_python_func() Jul 10 22:36:25 RP: wow, its crazy, how I'm literally working on that right now Jul 10 22:36:45 RP: I'm submitting patches for libstdc++ + newlib this week Jul 10 22:37:20 RP: I got it working now, its a matter of cleaning up and sending now Jul 10 22:37:35 RP: also I still have issues sending patches to the list Jul 10 22:41:31 RP: could you do me a favor and reply that its being fixed to that thread, I just replied but I don't think my email got there Jul 10 23:35:16 aehs29: your email did arrive Jul 10 23:35:35 aehs29: interesting coincidence, glad I asked you now! :) Jul 11 00:11:00 JPEW: patches posted :) Jul 11 01:51:15 Hi guys, I have installed successfully Poky with core-image-minimal. But as I investigated from https://layers.openembedded.org/layerindex/branch/master/layer/openembedded-core/, it has ca-certificates recipe. But actually as I checked on my built Poky, there is no directory ca-certificate or ssl. Jul 11 01:52:52 This is qemu of my Poky: https://i.imgur.com/fEce1uI.png Jul 11 01:53:46 What did I miss to get ca-certificate? **** ENDING LOGGING AT Thu Jul 11 03:01:20 2019