**** BEGIN LOGGING AT Thu Jan 18 03:00:02 2018 Jan 18 07:29:57 New news from stackoverflow: Linux Build Machine - Virtual/Real or otherwise? [closed] Jan 18 08:30:06 New news from stackoverflow: Adding multiple patches to SRC_URI in a recipe -- Yocto Jan 18 10:00:19 New news from stackoverflow: Yocto: recipe to manage dependencies with Go lang Jan 18 10:30:23 New news from stackoverflow: Recipe to manage dependencies Jan 18 12:30:37 New news from stackoverflow: Yocto recipe to manage Go dependencies Jan 18 15:48:15 vmeson: this is the bug we discussed https://bugzilla.yoctoproject.org/show_bug.cgi?id=11288 Jan 18 15:48:16 Bug 11288: normal, Medium+, 2.5 M3, kexin.hao, NEW , X Server fails to start on qemuarm64 (need CONFIG_FB?) Jan 18 15:48:23 vmeson: could you verify assignee? Jan 18 15:49:58 vmeson: nm, I see you sent mail Jan 18 16:38:26 May I run both Weston and IVI shells simultaneously on Wayland? Jan 18 17:14:09 are we serious "Fixed porno hack" Jan 18 17:19:30 armpit: talk to scottrif ;-) Jan 18 17:32:50 haha Jan 18 17:32:55 yeah that was funny Jan 18 17:32:58 "funny" Jan 18 17:33:17 not as funny as the time the guy posted a bug with a screenshot showing pornhub tabs, but still funny Jan 18 17:54:54 yo sri Jan 18 17:54:58 ww Jan 18 18:08:05 I'm trying to create a makefile based recipe where the makefile invokes libtool, but somehow when invoking libtool --mode=link libtool doesn't use arm-poky-linux-gnueabi-gcc to link the static library. what can I do to fix that? Jan 18 18:09:53 jaeckel: you'll need to set CC LD etc etc. have you considered using a proper build system like autotools/cmake/meson instead of a hard-to-get-right makefile? Jan 18 18:11:08 rburton: where do I have to set that? in the recipe? Jan 18 18:12:13 well the makefile works for literally all linux distributions Jan 18 18:12:22 my hunch is that libtool respects the LD environment variable Jan 18 18:12:36 its failing for oe so literally all isn't quite correct ;) Jan 18 18:13:05 so maybe exporting LD will be sufficient Jan 18 18:18:58 LD is already set to arm-poky-linux-gnueabi-ld --sysroot=/yadda/yadda Jan 18 18:23:52 rburton: hahaha I didnt see that one Jan 18 18:31:51 can someone help me? I updated to Rocko but now the dnsmasq doesn't start up, on pyro I had the service After=systemd-resolved.service . I get the error of directory /etc/resolv.conf for resolv-file is missing, can not poll, but I can manually start the dnsmasq Jan 18 18:39:02 ikkysleepy: I have seen this before and have been meaning to looking more closely at a proper resolution Jan 18 18:39:29 unfortunately there are many services which either write or read resolv.conf Jan 18 18:39:52 so the fix is not straightforward and will depend on what you include in your image Jan 18 18:41:17 unfortunately Yocto deals with this file differently than Ubu and RH Jan 18 18:42:26 I can't give you an easy fix as it might depend on what behavior you want Jan 18 18:42:59 local caching via dnsmasq or others, always go outside the system... Jan 18 18:43:22 yeah, trying to see what service I need to do. I have a start up script so I might just start it that way. odd that from pyro to rocko is all that was changed and it worked fine in pyro. Jan 18 18:43:43 ya, either carry a bbappend for base-file or dnsmasq Jan 18 18:44:08 you can make it as a pre-condition to create the file before the execstart for dnsmasq for example Jan 18 18:44:27 I have a bbappend for dnsmaq and have After=systemd-resolved.service, but now that doesn't work so trying to see which will will make it work. Jan 18 18:45:33 sounds good, you are on the right track. use https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html for some more information Jan 18 18:45:49 and be careful not to let bind (ie. named) and dnsmasq clash Jan 18 18:51:46 I have hostapd running to create AP, seems broken now... anyways thanks ... i'll keep looking into what is going on. Jan 18 19:43:52 quick update. Changing the after to different service didn't work... but adding systemctl start dnsmasq with my startup script worked. I guess this is the solution for now. Jan 18 22:46:01 rburton: bug number? ("not as funny as the time...") Jan 18 22:46:01 Hi, Is it possible to build Yocto Roko release on Centos 6.6? Jan 18 22:46:36 tlwoerner: some gnome bug which the reported managed to convince the admins to delete from mysql Jan 18 22:46:43 oh how we laughed Jan 18 22:47:07 :-) Jan 18 22:49:29 btman_: the supported distro is 7, so you'll need to install the buildtools tarball we provide to give you newer tools Jan 18 22:56:25 rburton: Is the buildtools tarball available in the yocto download site? Jan 18 22:56:29 yes Jan 18 22:58:14 https://www.yoctoproject.org/downloads/tools/rocko24/buildtools-esdk-rocko-24 Jan 18 22:58:25 rburton: Thanks a lot! Jan 18 23:18:38 rburton: ./x86_64-buildtools-nativesdk-standalone-2.4.sh Error: The SDK needs a kernel > 3.2.0 . Does this mean I can not run pyro builds on my RHEL 6.7 machine running 2.6 kernel? Jan 18 23:19:17 ha, well, that's interesting Jan 18 23:19:56 rhel6 is *very* old you know? Jan 18 23:20:38 you could just try building oe and seeing what fails Jan 18 23:20:49 might be trivial things to fix, like installing a newer make from source Jan 18 23:21:04 if you're using poky then you'll need to wipe the SANITY_TESTED_DISTROS assignment to stop it moaning Jan 18 23:23:29 rburton: Yeah, but we need to support it as of now :( Jan 18 23:25:40 rburton, by "if you're using poky then you'll need to wipe the SANITY_TESTED_DISTROS assignment to stop it moaning", do mean I will have to build builtools from source? Jan 18 23:26:08 i mean if you were planning to use poky then it will moan that centos6 isn't supported on every build Jan 18 23:26:13 but give it a go and see what breaks Jan 18 23:26:23 we dont test/support it but you never know Jan 18 23:26:35 no need for buildtools, just see what else it moans about Jan 18 23:38:25 you'll definitely need buildtools, just you'll need to build your own, most likely Jan 18 23:39:01 might want the EPEL repository if they're still maintained Jan 18 23:43:28 failed at m4-native-1.4.18-r0 saying "kernel too old" Jan 18 23:46:04 btman_: hahaha Jan 19 01:31:44 fray, morning Jan 19 01:31:56 sorry, wrong channel Jan 19 01:41:42 oops **** ENDING LOGGING AT Fri Jan 19 03:00:00 2018