**** BEGIN LOGGING AT Mon Jun 05 03:00:03 2017 Jun 05 09:22:33 Hi Jun 05 09:22:51 I have one newbie question , how to add libusb support in qemu. Jun 05 09:23:33 I have added in bbappend file EXTRA_OECONF_append = " --enable-usb" Jun 05 09:23:37 but didn't work. Jun 05 09:23:41 any idea ? Jun 05 10:31:29 dk`: this is probably late and you have the solution already :) Jun 05 10:31:58 dk`: you need to add PACKAGECONFIG += "libusb" Jun 05 10:32:16 dk`: in your bbappend Jun 05 11:32:37 ed2: there? Jun 05 11:58:53 rburton: here Jun 05 11:59:32 ed2: your latest wic series does something which means rmc gets installed whereas before it didn't. was this intentional? fixing a bug? Jun 05 11:59:38 (with meta-intel) Jun 05 12:01:08 rburton: i've added implicit dependency to EFI_PROVIDER, which is rmc-db in meta-intel. Jun 05 12:01:37 rburton: however, it should only work if EFI_PROVIDER is set. This is probably the case for meta-intel too. Jun 05 12:02:29 rburton: does it break something? Jun 05 12:03:13 rburton: btw, why do we need to test everything on meta-intel? I used only default set of layers previously. Jun 05 12:03:37 i only noticed because thats the bsp i have by default Jun 05 12:03:54 yeah seems sane thoug, i'll ping sgw later to be sure he's happy with that Jun 05 12:04:53 rburton: I hope he'll be happy as wic image building is enabled in meta-intel and EFI_PROVIDER is set, so it must be built. Jun 05 12:11:19 Hi all! Trying to make mpg123 1.23.6 play mp3 on beaglebone black via attached USB soundcard and alsa. Using yocto morty/core-image-base for stock target "beaglebone". speaker-test runs fine, soundcard is listed in aplay -l. My problem: mpg123 wont play on alsa, no output module/driver available, i.e.: mpg123 --list-modules shows no alsa option, just pulse and some builtin modules. Any ideas? (Sorry for flood, ne Jun 05 12:11:19 wcomer) Jun 05 12:12:27 distrozapper: the recipe says that it only enables alsa support if you don't have pulseaudio enabled in your distro Jun 05 12:13:20 so either remove pulseaudio from DISTRO_FEATURES to make it go away for good, or just override PACKAGECONFIG to "alsa" for mpg123 Jun 05 12:13:29 (the docs cover option 2) Jun 05 12:15:46 rburton: Thanks very much for help, I read the recipe but didnt interpret it like that. I will try and do like you tell. Merci! Jun 05 12:17:42 Hello Jun 05 12:18:06 how do I apply the preempt-rt kernel patches to the build? Jun 05 12:18:20 first day with yocto :) Jun 05 13:02:28 TurBoss: Use linux-yocto-rt as the kernel provider? Jun 05 13:02:51 in bblayer.conf? Jun 05 13:03:30 seems no Jun 05 13:03:42 ok will investigate thanks! Jun 05 13:09:30 RP: PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" ? Jun 05 13:09:47 TurBoss: right Jun 05 13:09:51 Thanks Jun 05 13:15:08 Is anyone here familiar with the "new theme" (USE(NEW_THEME)) code in WebKit? Jun 05 13:15:55 Arg wrong chat window, sorry Jun 05 13:39:57 Hi guys... is possible to use meta-openembedded/meta-networking recipes in poky distro? I'm interested in autofs recipes but I don't understad if is compatible with poky... Jun 05 13:40:53 yes Jun 05 13:41:22 why would it not be? trying to see what bit of the model you don't understand. Jun 05 13:48:56 RP: just fired another gcc7 test build to see where we are Jun 05 13:52:35 rburton: so I just add meta-openembedded/meta-networking and meta-openembedded/meta-python in my bblayer.conf? my dubt is if I make that continue to have a poky distro and not an hybrid beetween poky and openembedde... Jun 05 13:53:18 so poky is an example of how to build an OE based distribution Jun 05 13:53:29 by using OE you are by definition creating a hybrid of what you want Jun 05 13:53:44 yes, add the layers to bblayers and then add the packages you want to your images Jun 05 13:55:43 rburton: ok... now I understand... thanks Jun 05 17:56:05 how do enable "boot to qt" Jun 05 19:21:24 I'm getting this error when running bitbake Jun 05 19:21:25 http://dpaste.com/1RXZQ5H Jun 05 19:21:44 PATH contains '.', './' or '' (empty element), Jun 05 19:34:53 rburton: do we have recents runs with gcc7 on AB ? Jun 05 19:36:59 TurBoss: then you should fix your PATH variable Jun 05 19:45:12 My PATH doesn't look like the one that outputs when i run bitbake Jun 05 19:47:57 khem: was just looking for you :) Jun 05 19:48:06 khem: http://errors.yoctoproject.org/Errors/Latest/?filter=beaea15cf2429291b0f29ba3d1a12729f1d13ba3&type=commit Jun 05 19:58:19 kergoth: sorry I didn't sourced the oe-init-build-env Jun 05 19:58:25 solved Jun 05 20:23:56 does poky pyro/morty come with enough meta layers to add qt5 Jun 05 20:25:10 black_13: yes. Just read the README of the qt5 laeyr Jun 05 20:25:16 *layer Jun 05 20:26:26 then you would have to add meta-qt5 Jun 05 20:27:04 meta-qt5 is the layer with qt5 in, so just use that Jun 05 20:27:14 https://github.com/meta-qt5/meta-qt5 Jun 05 20:27:23 is the correct place to clone from Jun 05 20:27:27 i ask Jun 05 20:29:00 ~ Jun 05 20:29:10 yes Jun 05 20:29:32 https://layers.openembedded.org/layerindex/branch/master/layer/meta-qt5/ Jun 05 20:47:26 in order but build the qt5 layer I would add meta-qt5 to the BBLAYERS variable ? Jun 05 20:48:28 yes Jun 05 20:48:39 thats how you add a layer to your build configuration Jun 05 20:49:14 and even if its an x86 machine it will be than happy to do this? Jun 05 20:49:29 all the instructions I find are for ARM Jun 05 20:50:25 sure Jun 05 20:50:38 thats just because the qt5 people are building on a beagle or something Jun 05 20:50:59 top hit on google is http://doc.qt.io/QtForDeviceCreation/qtee-custom-embedded-linux-image.html Jun 05 20:51:15 which includes the intel nuc with an intel core Jun 05 20:51:36 I have x86 mini notebook i fished out of the "trash" from work it was basically new it was being used as a serial term Jun 05 20:52:03 i want to use qt5 with out X11 Jun 05 20:53:22 here is my bblayers.conf file http://codepad.org/0wRjxcAS Jun 05 20:55:50 zeddii: one last kernel failure with gcc7, http://errors.yoctoproject.org/Errors/Details/143869/ Jun 05 20:56:11 khem: so its just the kernel and mesa left for gcc7 Jun 05 20:57:59 RP: mut fired on yocto.io Jun 05 21:00:03 zeddii: also https://bugzilla.yoctoproject.org/show_bug.cgi?id=10456 is likely a morty point release blocker Jun 05 21:00:04 Bug 10456: normal, Medium+, 2.3 M4, dengke.du, REOPENED , X can not launch on qemumips64 Jun 05 21:00:29 RP: I added PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" to build/conf/local.conf Jun 05 21:01:03 but I get this : http://dpaste.com/2S0D8ZA Jun 05 21:01:03 TurBoss: its 10pm for RP so i suggest asking the room instead of just one person Jun 05 21:01:14 oh sorry Jun 05 21:02:00 well Jun 05 21:02:14 I need something else to build a realtime kernel? Jun 05 21:02:39 what kernel settings do i need to use the frame buffer qt5 Jun 05 21:56:08 TurBoss: you never specified which MACHINE you wanted to use. linux-yocto-rt doesn't support raspberrypi. So you need a kernel recipe for the raspberrypi which someone has applied the rt patches to... Jun 05 21:56:15 TurBoss: I have no idea about that Jun 05 21:56:40 Ok thanks! Jun 05 22:30:10 bye Jun 06 00:37:52 after build sato image with iso support the iso based linux is unable to start X11 Jun 06 02:06:33 what is the file type to make a testable image for qemu arm? Jun 06 02:44:23 how would I make the /tmp dir be readable Jun 06 02:44:39 /tmp is readable. what exatly is the issue? Jun 06 02:47:52 the mount is "/dev/loop0 on / type ext4 (ro,noatime,nodiratime,data=ordered) Jun 06 02:48:06 this is iso based **** ENDING LOGGING AT Tue Jun 06 03:00:02 2017