**** BEGIN LOGGING AT Fri May 18 03:00:04 2018 May 18 06:53:28 is anybody else experiencing difficulties building cross-canadian gdb for arm w/ rocko? May 18 06:56:14 it fails because `error: no usable python found` :-/ I see that the automatically provided python is a wrapper script May 18 06:57:09 this happens with gdb 8 May 18 07:08:08 disabling gdb's python support via PACKAGECONFIG makes it compile (at least). May 18 07:56:45 hmmm. `populate_sdk` does not succeed for a rather small image. `[Errno 2] No such file or directory: '/home/yocto/build/bar/tmp/work/bar-foo-linux-gnueabi/gui-image/1.0-r0/sdk/image/opt/foo-bar/i.MX6-PD-rocko-2017-03-20/sysroots/x86_64-foosdk-linux/usr/lib/locale'` May 18 08:03:23 http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oe/sdk.py#n45 fails, because `localedir` does not exist May 18 08:14:33 which recipe is supposed to create it? May 18 08:33:31 I guess it's http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/lib/oe?id=46ce466e19cd238410baf383e919472ec8801b85 May 18 08:47:06 the package `nativesdk-locale-base-en-us.utf-8_2.26-r0_x86_64-nativesdk.ipk` is empty :-/ May 18 09:23:23 khem: latest ovmf works here. any idea why it was working for you but not me? May 18 09:59:05 what's the right way to provide a custom .dts to linux kernel May 18 09:59:23 create an own recipe with .bbappend doing the job? May 18 10:04:42 Hi, I'm trying to bitbake -c menuconfig linux-kernel and I end up with "checklist.c:(.text+0x2c): undefined reference to `wmove'" + alot more undefined references. The recipe has DEPENDS += "dtc-native ncurses-native". I'm using rocko on a Debian 9 machine. I also have ncurses installed on Debian, but it should not matter. Any ideeas ? May 18 10:08:44 rburton: well look, U-Boot might just be fixed soon May 18 10:08:57 Marex: nice May 18 10:09:05 rburton: I think I found the bug, so then I can enable U-Boot on qemux86 and let the drone update it May 18 10:09:39 rburton: just trying to decide if I want to carry a patch or wait for v2018.07 cycle with the qemux86 enablement May 18 10:10:05 if the patch isn't too heavy lets carry it, in theory AUH will run, upgrade, and drop it May 18 10:11:16 rburton: but I dont want to have patches on top of u-boot recipe :-) May 18 10:12:06 rburton: oh well ... I might as well backport it temporarily as a part of the qemux86 enablement series May 18 10:13:06 rburton: if you can, please pick the v2018.05 update I sent, I'll backport the patch and enable U-Boot on qemux86/-64 once that patch lands in u-boot/master May 18 10:13:13 ok May 18 10:13:24 thanks! May 18 10:15:50 JaMa: annoyingly libsdl2 isn't happy on mingw May 18 10:18:54 installing ncurses-dev on the build host solved the problem... May 18 10:19:45 Shouldn't it just use the -native generated libs ? Why doest it use the build machine/system wide ones ? May 18 10:23:01 rburton: I neved did anything with mingw :/ May 18 10:23:29 mostly solved by disabling the x11 bits but it fails to link May 18 10:23:39 ggtk: yes, it should May 18 10:25:34 ggtk: is this the linux-yocto kernel? May 18 10:27:35 anujm: it's a recipe for the Atmel kernel, http://www.at91.com/linux4sam/bin/view/Linux4SAM/LinuxKernel#linux4sam_5_8_tag, based on Kernel 4.9 May 18 10:28:33 ggtk: does this help: https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/recipes-kernel/linux/linux-intel/0001-menuconfig-check-lxdiaglog.sh-Allow-specification-of.patch May 18 10:30:41 anujm: interesting... I'll try it May 18 10:32:27 ok. I think this patch is in all linux-yocto kernels so you probably wont see it if you can try that out. May 18 10:32:28 I purged ncurses-dev and now it still works ... so it's also inconsistent... May 18 10:35:02 Sorry, i was quick to judge, uninstalling ncurses-dev got the problem back, so forget my last point May 18 10:41:21 New news from stackoverflow: Yocto 2.4.2 cannot do_rootfs because of dependent package May 18 10:41:59 anujm: that patch does the job,menuconfig starts, life saver ! thanks May 18 10:47:00 great! May 18 10:49:16 if anyone understands mingw then i've a sdl2 link problem i'd appreciate help with May 18 10:57:21 I have a small "make[1]: cc: Command not found" issue at hand. I have an old jethro based poky environment where I have added "luci" from some MentorEmbedded/meta-openwrt. Everything works in that system. However, I am now updating poky and meta-openembedded etc. layers to "rocko" and this luci-module is giving me this "command not found" error (had to add "inherit pkgconfig" to luci_git.bb recipe to even get that far). Anyway, I am guessing this issue May 18 10:57:48 muppe: modern yocto prunes $PATH and cc isnt on the list of approved names May 18 10:58:16 if that is meant to be using the cross compiler then you've found another bug May 18 10:58:30 if its meant to be using the host compiler, patch the makefiles to use $BUILD_CC May 18 11:00:02 Ok, thanks. My target environment is Raspberry Pi but not sure whether that part of recipe is compiling something for the host or for the target. Need to check. May 18 13:14:23 rburton: Whats the mingw problem? I've worked with it some. May 18 13:18:26 JPEW: https://pastebin.com/N03tGmmb May 18 13:18:40 nativesdk-libsdl2 on mingw May 18 13:21:15 hello guys.. I have built the sdk using TOOLCHAIN_HOST_TASK_append += "nativesdk-cmake" in my local.conf and running bitbake core-image.minimal -c populate_sdk May 18 13:21:48 then I have installed it using the script tmp/work/deploy/sdk May 18 13:22:58 In one of my source files I use the #include directive, pgpio.h is generated by the pgipo recipe. May 18 13:23:44 By the way cmake says thet it can't find the pgpio.h file May 18 13:23:54 I think I am missing something May 18 13:24:47 is pgipo in your core-image-minimal? May 18 13:25:25 alternatively cmake is being cmake, and proving a pain May 18 13:27:25 rburton: yes It's in a depend statement of the recipe the curruntly build the same application May 18 13:27:32 currently* May 18 13:28:53 which is in the image? so hard to tell when people say "core-image-minimal" without saying what they're doing to it May 18 13:29:18 if it was 'my image which has IMAGE_INSTALL+=this list of recipes' it would be a lot easier May 18 13:29:38 on which note, *dont use core-image-minimal and modifications in local.conf*, just make your own image recipe May 18 13:29:45 the toolchain bit can go in the image too May 18 13:30:16 uh ? May 18 13:31:26 I have a recipe called cloud4drones, this recipe has a RDEPENDS_${PN}+=" pgpio" May 18 13:32:27 then i local.conf I have CORE_IMAGE_EXTRA_INSTALL += " cloud4drones" May 18 13:33:01 if cloud4drones is C, surely that should be DEPENDS and then let bitbake work out the rdepends for you May 18 13:33:30 yes, is C. I didn't know that.. May 18 13:33:36 rburton_: Hmm, that SDL error sure *looks* familiar.... I can't quite place it. May 18 13:33:48 fberg: RDEPENDS is runtime depends, not build time May 18 13:34:32 fberg: anyway you'd expect the header to be present but without seeing any of your recipes i can't tell if pgpio is packaging correctly, or if the header is in fact in the sdk but cmake can't find it May 18 13:34:43 you need to look and see if its missing, or if cmake is being dumb May 18 13:35:19 if all is sussposed to be installed correctly where do I have to expect to find this .h ? May 18 13:37:00 in the sysroot May 18 13:38:36 which is tmp/sysroots ? May 18 13:39:24 I'm not totally dumb but I am really confused May 18 13:40:16 just do find . -name pgpio.h inside the sdk May 18 13:42:00 New news from stackoverflow: Gumstix Overo Yocto Qt5 deployment May 18 13:42:46 ok, thanks rburton_. I'll give it a try May 18 15:48:56 nice. my provider blocked yoctoproject.org together with all the docs ^_^ Oh, that insane game with telegram blockade.) May 18 15:49:29 thanks god there are free online proxies. May 18 15:50:44 how did yoctoproject.org get caught up in the telegram blockade? poor blocking (by IP range or something)? May 18 15:51:26 (yp.org is via amazon AFAIK.. but I thought telegram stopped using amazon) May 18 15:52:54 might be. telegram has used so many IPs, so russian communication services just started to block whole pools of IPs.) May 18 15:53:07 Particularly I keep getting ERR_CONNECTION_RESET. May 18 15:56:06 rburton_: earlier I did patches directly cherry-picking in a local ovmf git checkout May 18 15:56:18 this time I did them using quilt May 18 17:51:58 Hi All, May 18 17:54:23 Question: My silicon provider is providing some support packages as rpms built against yocto jethro, I need to incorporate them into the image I am building, but I'm having trouble working out how to write a recipe that installs RPMs into the final image... (I know they work as I have successfully installed them on the running build...) May 18 18:06:49 tffh: I believe bin_package.bbclass was around back in Jethro. You could use that class to install RPMs. May 18 18:07:29 tffh: The "subdir" parameter in the SRC_URI is useful when the input package is rpm, ipk, deb and so on, for example: May 18 18:07:31 tffh: SRC_URI = "http://foo.com/foo-1.0-r1.i586.rpm;subdir=foo-1.0" May 18 18:08:43 Hi stephano, Thank-you very much, I shall investigate bin_package May 18 18:09:01 tffh: No problem. More info here: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-classes-bin-package May 18 18:09:35 tffh: Also, out of morbid curiosity, who is your silicon vendor? May 18 18:10:36 intel May 18 18:12:15 * stephano plants his palm firmly on his face May 18 18:12:44 tffh: Here's an example using tar, RPM will be similar: https://github.com/openembedded/meta-openembedded/blob/master/meta-networking/recipes-connectivity/wireless-regdb/wireless-regdb_2016.06.10.bb May 18 18:12:56 I just queried your user info... May 18 18:13:03 Thankyou once again. May 18 18:13:13 tffh: Np. Ping me if you have questions. May 18 18:14:11 * tffh is a microcontroller software dev who is finding all of this side of things seriously out of her depth but isn't being given any option by her employer. May 18 18:43:01 New news from stackoverflow: Using Conditional Syntax (Overrides) in BitBake May 18 19:32:02 tffh: intel is giving you RPMs built against jethro? curious what bit of intel did that as they need a talking to May 18 19:32:48 (speaking as a yocto engineer employed by intel) May 18 19:35:55 JaMa: do you use musl? May 18 19:36:11 JaMa: i'm seeing musl builds hang in webkitgtk when it runs qemu-user during the build May 18 19:37:40 JaMa: g-i specifically May 18 19:49:18 rburton_: I'm being told that the only way to garentee support is to do what they have validated, and that is to use(or mimic) the leafhill BSP. May 18 19:50:57 * tffh has noticed that jethro is a little old, but is having enougth trouble getting things working with Intel's instructions to follow. May 18 19:54:44 I assume this is an Apollo Lake part.. assuming so, there are both Yocto Project and meta-intel BSP components you can use.. May 18 19:55:00 You only need to follow what Intel is telling you, if you are expecting them to support some piece of the software.. May 18 19:55:14 various commercial OSVs support the Apollo Lake parts as well. May 18 19:55:26 (and on code newer then Jethro) May 18 20:02:07 what I have so-far failed to do is to get the Camera interface working with just meta-intel. The kernel patches I was supplied with for the MIPI CSI all pertain to the jethro BSP. May 18 20:03:13 I know we (Wind River) have customers using the camera interface on architectures newer then Jethro.. but I'm not involved int he project so I don't have details. May 18 20:03:35 (unfortunately many of the people I would ask are out of the office today and Monday).. May 18 20:04:01 I know I should be able to use something newer, but to date I've been dependant on support from the Intel team a lot and thus teathered to their validation platform. May 18 20:10:55 rburton_: nope, only glibc May 18 20:17:23 Thankyou all for your help tonight. May 18 20:17:28 * tffh waves **** ENDING LOGGING AT Sat May 19 03:00:00 2018