**** BEGIN LOGGING AT Mon Jul 30 03:00:00 2018 Jul 30 08:34:12 hi Jul 30 08:35:11 I am new to yocto project. Jul 30 08:35:43 I need to know how to add wayland to my image istead of x11 Jul 30 08:35:55 can any one help ? Jul 30 09:03:59 dawod: this is the first hit when i type 'yocto wayland' into google. https://wiki.yoctoproject.org/wiki/Wayland What have you already tried? Jul 30 09:09:37 the same for me, but at first i couldn't understand some details . i read it again and understand .thank you Jul 30 09:24:00 dawod: if you dont know what something means, the first thing i would do is go to the Mega Manual and ctrl + f for the term you are loooking for (https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html) Jul 30 09:26:32 fl0v0: thank you veru much . I will do in the next times. Jul 30 10:12:09 Good afternoon, Jul 30 10:12:09 Is there any easy way to install a legacy toolchain? For example gcc-4.8 on a modern YP ? Jul 30 11:28:34 https://lists.yoctoproject.org/pipermail/yocto-ab/2018-July/002279.html Jul 30 11:28:50 * tlwoerner congratulates ndec Jul 30 12:03:36 tlwoerner: thanks ;) Jul 30 12:04:46 it's sad to see jefro playing a reduced role (officially?) in this community, but it's great to see you taking this over Jul 30 12:04:52 ndec: congrats! Jul 30 12:07:00 hi tlwoerner , yes, jefro has stepped back officially. see https://lists.yoctoproject.org/pipermail/yocto-ab/2018-June/002233.html. this was the trigger for Lieu Ta to take the AB chairman position, and myself. Jul 30 12:07:23 also, i hope you've noticed that the 'member' page has been updated recently, with new platinum members.. https://www.yoctoproject.org/ecosystem/members/ Jul 30 12:07:36 ndec: yes very nice to see :) Jul 30 12:14:11 someone needs to update the subject of this channel (i.e. update the community manager) Jul 30 12:14:46 ndec: i was very surprised to see fb and am curious about their interest Jul 30 12:15:31 ndec: and i saw the ARM announcement in my feeds very recently Jul 30 12:15:49 * tlwoerner thinks these are interesting times for the project Jul 30 12:15:55 ;-) Jul 30 12:17:22 tlwoerner: https://github.com/facebook/openbmc Jul 30 12:18:34 well thats their fork but they're working upstream more now Jul 30 12:19:01 rburton_: nice! it's nice to see less home-brew Jul 30 12:20:30 yeah Jul 30 12:21:04 extrapolating from the size of their data centre and the fact that their servers run yocto makes me think they've got one of the largest deployments in the world Jul 30 12:25:01 now that they've joined the -ab, maybe we'll also start to see them at devdays, ELC(E)s, and OED{A|E}Ms Jul 30 12:38:39 Hello! I am new to yocto, and have a question: How do I add apt-get to my target? I have added PACKAGE_CLASSES ?= " package_deb" and EXTRA_IMAGE_FEATURES ?= " package-management". apt-get is added, but is functionally worthless, as it doesn't have any sources or anything. Jul 30 12:42:25 How can I make available a file of one recipe (recipe-A) in another recipe (recipe-B)? Jul 30 12:42:46 e.g. package-config binary configuration script Jul 30 12:47:50 I guess it should be in recipe's B ${WORKDIR}/recipe-sysroot/usr/bin/crossscripts/ Jul 30 12:47:57 But it doesn't Jul 30 12:49:01 malanecora: recipe-A needs to install it so that it gets put into the sysroot, and recipe-B needs to have recipe-A in DEPENDS Jul 30 12:49:45 beware that not all paths that are installed by recipe-A are automatically part of the sysroot, but the standard paths for pkg-config scripts definitely are, so unless you're installing your .pc file in a non-standard location, this should work out of the box Jul 30 12:51:12 does anyone know how to write a recipe file for installing a folder in the rootfs ? Jul 30 12:51:42 i was trying the "cp"command, but's not working for me Jul 30 12:52:59 neverpanic: recipe-B already have recipe-A in DEPENDS. It's not a .pc script but kind of (the very same as the old configuration scripts used to be). Jul 30 12:53:26 So, I have to install it in sysroots, right? Jul 30 12:54:44 karthik__: It does works for me. Jul 30 12:55:12 I manage the folder as a normal file Jul 30 12:56:41 Hey guys! Having trouble with meta-intel-qat. Anyone faced issues with that before ? Jul 30 12:57:04 neverpanic: BTW, I'm installing it in ${bindir} Jul 30 12:57:55 malanecora: As long as it's in one of the standard paths (http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/staging.bbclass#n10), it should still work. Jul 30 12:59:32 karthik__: can you pastebin the recipe that you're tried and the error message you're getting? Jul 30 13:02:49 neverpanic: should I install it also in sysroot-dest folder in order to make the file available for other recipes? Jul 30 13:03:08 No, that should happen automatically. Jul 30 13:07:07 neverpanic : I don't have access to pastebin and let me see if i can find some alternative. Jul 30 13:07:37 karthik__: p.dnnr.de Jul 30 13:07:45 malanecora : can you share you bb file ? Jul 30 13:07:52 share your* Jul 30 13:08:17 neverpanic : you saved me from google :P Jul 30 13:09:26 neverpanic : https://p.dnnr.de/bGUAdBLSSKura06Y this is my recipe Jul 30 13:10:57 neverpanic : cannot stat the folder "eventmachine-1.2.7" in work directory is the error Jul 30 13:11:10 SRC_URI = "file://test" Jul 30 13:11:19 S="${WORKDIR}" do_compile() { : } do_install() { install -d ${D}/ cp -r ${S}/test ${D}/ } FILES_${PN} += "/test" Jul 30 13:11:36 Being "test" a folder with subfolders and files Jul 30 13:12:18 malanecora : what does the S varibale stands for ? Jul 30 13:13:26 Usually S = "${WORKDIR}/${BP}" Jul 30 13:14:06 In Yocto environment Jul 30 13:15:06 http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/conf/bitbake.conf?h=bernard Jul 30 13:15:22 karthik__: Not sure wildcards will work in SRC_URI. Jul 30 13:15:59 install: cannot stat ‘/home/iriejc/my_workspace/tmp/work/cortexa7hf-neon-linux-gnueabi/eventmachine/1.2.7-r0/eventmachine-1.2.7.gemspec’: No such file or directory Jul 30 13:16:18 this is the error the build is throwing when i tried the cp command in bb file Jul 30 13:16:38 neverpanic : then how do i point to that folder ? Jul 30 13:16:47 karthik__: have you tried using a tarball? Jul 30 13:16:54 nope Jul 30 13:17:09 tar the folder ? Jul 30 13:17:43 yes, and point the recipe to the tarball. that should automatically extract the contents into ${WORKDIR}, where you can cp them Jul 30 13:19:43 will try that Jul 30 13:22:35 Also, my /tmp/sysroots folder is empty, is that normal? Jul 30 13:26:12 IIRC the sysroots moved with the recipe-specific sysroots feature, but I'm not regularly using a modern Yocto with that feature, so I'm the wrong person to ask. Jul 30 13:28:46 How do I add apt-get to my target? I have added PACKAGE_CLASSES ?= " package_deb" and EXTRA_IMAGE_FEATURES ?= " package-management". apt-get is added, but is functionally worthless, as it doesn't have any sources or anything. Jul 30 13:29:35 neverpanic: Ok! Thank you! Jul 30 13:39:10 neverpanic : good suggestion. There is improvement. Thank you. Jul 30 13:39:32 arm-linux-gnueabi-objcopy:/home/iriejc/yocto_digi/my_workspace/tmp/work/cortexa7hf-neon-linux-gnueabi/eventmachine/1.2-r0/package/usr/lib/ruby/gems/2.5.0/gems/eventmachine-1.2.7/ext/fastfilereader/fastfilereaderext.so: File format not recognized Jul 30 13:39:38 but now i am getting this error Jul 30 13:40:00 why is not objcopy not recogonizing .so files ? Jul 30 13:58:51 wrong architecture, maybe? Jul 30 14:29:18 hey guys! When I run bitbake I get a 'CC= ... -fdebug-prefix-map = ...' but I do not get the --sysroot=path so some headers while they are there are not found Jul 30 14:29:28 and it throws a missing error while using devshell Jul 30 14:29:30 any idea? Jul 30 14:33:55 tendie: set PACKAGE_FEED_URLS in your local.conf to the base URL that you're running the feed on Jul 30 14:34:10 tendie: bitbake doesnt' run a http itself, so you need to do that bit yourself Jul 30 14:34:19 (i just have a lighttp on my build box) Jul 30 14:45:57 rburton: What do you mean, the base URL that I'm running the feed on? I think I'm a step or two behind that. Jul 30 14:53:14 Please take a look over this post! https://stackoverflow.com/questions/51496061/using-files-generated-by-other-recipes-in-yocto Jul 30 15:11:15 tendie: if you want apt-get to work then you need to host the feed somewhere... Jul 30 15:11:31 as i said, i just run a lighttp on the build machine and point to the right ip Jul 30 15:16:36 My target has an ethernet plug and can download things from repos with mercurial, why does is depend on the build host to get package feeds for apt-get? Jul 30 15:24:07 ok who understands mips Jul 30 15:24:18 lol.. 'what part' Jul 30 15:24:20 tendie: where else is apt going to get package feeds from? Jul 30 15:24:28 fray: arch flags and tunes and etc Jul 30 15:24:40 fray: debugging the sdk failure where cmake won't link Jul 30 15:32:08 rburton: I guess I'm still misunderstanding. I am going to ask some questions to clarify what I'm not getting: A package feed is like the urls you would find in sources.list in /etc/ept. Is this correct? Jul 30 15:32:25 the URLs point to a package feed yse Jul 30 15:32:26 yes Jul 30 15:36:07 Okay. So if i'm looking to get apt-get on my target to mimic how it default is set up on for example ubuntu, PACKAGE_FEED_URLS should contain those urls found in sources.list. That's one step, correct? Jul 30 15:39:46 ubuntu has a web server hosting their package feeds Jul 30 15:39:57 you'll have to do the same, bitbake doesn't install a web server for you Jul 30 15:40:52 some *distros* may or may not provide a package feed, but it's not possible for oe/yocto to provide a generic one, as there are too many ways to change the build in ways that break binary compatibility Jul 30 15:41:00 New news from stackoverflow: Build Qt5 with Cmake in Yocto Jul 30 15:44:12 kergoth: so because my image isn't using ubuntu, I can't use the ubuntu package feeds by just copying those URLs. Is this correct? Jul 30 15:45:51 that's true for any distro of any kind. packages from one distro aren't safe to install on other distros unless they're explicitly compatible. that's true on the desktop as well as embedded. Jul 30 16:12:19 tendie: *if* you want a working package feed then set PACKAGE_FEED_URLs to the base URL that you'll have the feed on, and bitbake will write the correct sources.list using that URL Jul 30 16:12:45 i run a local httpd on my build machine so PACKAGE_FEED_URLS=http://flashheart.local/deploy/ Jul 30 16:23:52 like many yocto projects, my image recipe generates a foo.rootfs.ext file in the deploy/images/machine directory. Jul 30 16:25:22 i need to custom-generate a similar type of file. how do i a) specify the components which go into the file, and b) create a partition of a specific type (in my case, fat32)? Jul 30 16:25:41 components == files.. Jul 30 16:26:40 s/foo.rootfs.ext/foo.rootfs.ext4/ Jul 30 16:26:57 does it require wic? Jul 30 16:27:23 per section 5.6 of the development manual? Jul 30 16:27:29 want to generate my own Jul 30 16:27:37 ignore that last line ^^^^ Jul 30 16:27:41 https://www.yoctoproject.org/docs/2.0/dev-manual/dev-manual.html#creating-partitioned-images Jul 30 16:28:45 partitioning would require wic or something similar/custom, yes Jul 30 16:29:21 can you just use fdisk somehow in the recipe? Jul 30 16:29:35 (running on linux) Jul 30 16:30:11 to create a partition table, sure, but scripting fdisk is a pain in the ass, and you'd still have to know the correct offsets to dd the filesystem image into the right spot in that image Jul 30 16:30:36 parted is better, but still a royal pain. there's a reason wic exists, it wraps exactly this sort of thing for you Jul 30 16:30:53 but sure, you could definitely roll your own if you want to, i've done it before Jul 30 16:31:33 i use a bong. Jul 30 16:31:36 :) Jul 30 16:32:39 is there an example of this somewhere? Jul 30 16:33:05 of an entire recipe, that is, which performs these steps? Jul 30 16:33:33 it's generally done in an image type class introducing a new image type, not a recipe Jul 30 16:33:44 and you'd likely have to check old branches, since most everyone has moved to wic Jul 30 16:34:16 so you mean folks do this by using wic outside of bitbake? Jul 30 16:35:47 did you mean the wic commands are used within the class routines to generate an image type? Jul 30 16:36:06 s/did you mean/or did you mean.../ Jul 30 16:42:53 why am i constantly feeling like using yocto is like getting directions without knowing which way north is?!?!? Jul 30 16:48:58 image types are functions/variables with the commands to create an iage of that type Jul 30 16:49:14 those types are added to IMAGE_TYPES by the machine .conf to control what image binaries are emitted Jul 30 16:49:20 i.e. tar.gz, ext4, wic, etc Jul 30 16:49:25 you can create your own as well Jul 30 16:49:43 fairly sure image types are covered by the yoctoproject.org docs, but it's been a while since i read them Jul 30 17:36:40 When I boot my Yoco distribution (systemd based), for some reason it already has a somewhat recent date set (Fri Jul 20 08:26:37 UTC 2018) - where does this come from? Asking because /var/lib/systemd/timesync/clock does not exists initially. Jul 30 17:55:01 reto: your board may have a battery backup Jul 30 18:08:51 yates: nope Jul 30 18:09:14 it is our own board and there is no rtc (MediaTek MT7688 based) Jul 30 18:09:30 And on every startup the time is reset to around Fri Jul 20 08:26:37 UTC 2018 Jul 30 18:10:01 Pretty sure it just takes a timestamp as reference and uses it - I just would like to understand which file and which server (likely systemd) Jul 30 18:17:30 does the mips24kEc have an on-board clock? perhaps the kernel is initializing it? Jul 30 18:26:35 let me back WAY up and ask a top-level question: what is an "image"? is it the rootfs? Jul 30 18:27:23 "IMAGE_FSTYPES: Specifies the formats the OpenEmbedded build system uses during the build when creating the root filesystem." Jul 30 18:29:49 kergoth: i've looked through the docs and don't see any section specific to images and image_types. can you please provide a poitner? Jul 30 18:31:19 i am not trying to create a rootfs "iamge" Jul 30 18:31:21 image Jul 30 18:31:41 i am trying to create a fat32 "image" with zImage and the .dtb files on it Jul 30 18:32:03 this for for swupdate, so that image can be added to sw-description Jul 30 18:32:14 even if you don't use the image type mechanism directly, you can easily *read the image type functions* to see how they're constructing the binaries Jul 30 18:32:33 either look at the wic one to see how wic is used, or look at an old branch's custom image types to see how folks use fdisk/parted/etc to construct images Jul 30 18:32:47 i.e. many layers have done an image_types_sdcard in the past prior to migrating to wic Jul 30 18:33:03 how old is "old"? morty? Jul 30 18:33:07 or just do it yourself, really your call Jul 30 18:33:17 i don't know the exact timeline of wic adoption, it was gradual Jul 30 18:33:42 just search the layer index for image_types, or mksdcard, or whatever, or again, just research how to script fdisk and do it yourself Jul 30 18:33:45 * kergoth shrugs Jul 30 18:34:04 kergoth: regarding the package management discussion earlier: is there a distro I can use that is compatible with the ubuntu package feeds? That is most likely a requirement for my current project. Jul 30 18:37:53 where are the "*image type functions*"? Jul 30 18:38:43 i'd love to read them and adapt to them. Jul 30 18:39:33 image_types.bbclass? Jul 30 18:58:21 tendie: http://layers.openembedded.org/layerindex/branch/master/recipes/?q=apt Jul 30 19:00:31 yates: I'm including apt, but the target doesn't get flashed with anything in sources.list. Jul 30 19:03:38 i'm no expert on package management, but i get the repo doesn't have your machine type Jul 30 19:03:43 s/get/bet/ Jul 30 19:04:26 and i'm an apt-idiot - i use rpm/dnf (fedora) Jul 30 19:04:37 (for my host machine) Jul 30 19:05:33 and "flashed"? Jul 30 19:05:54 i don't apt would do any flashing, just copying to the filesystem. Jul 30 19:06:05 s/don't/don't think/ Jul 30 19:06:08 (dang...) Jul 30 20:38:12 how does something in a .bb file cause anything in the image_types.bbclass to be run? Jul 30 20:38:21 i'm not getting that connection Jul 30 20:42:41 and what distinguishes a "non-image" recipe from an "image" recipe? Jul 30 20:48:43 what is a "bootable live image"? Jul 30 20:48:49 (do_bootimg) Jul 30 20:49:58 like "fedora live"? Jul 30 20:50:07 something you can boot off a thumbdrive? Jul 30 20:57:00 kergoth: perhaps you don't understand where i am confused. if all i had to do was write my own script to use fdisk or whatever to generate a .fat32 file, i'd have been done days ago. that part i know. Jul 30 20:57:43 what i am trying to do is get YOCTO to do this as part of a recipe (or a recipe which invokes functions in a bbclass, or what the hell ever) Jul 30 20:58:59 i want ultimately to generate the .swu file by running "bitbake swu", which would then do what's necessary to generate the ext4 of the rootfs (i think i have this part down) and then fat32 of the "linux" image (zImage + dtbs) Jul 30 21:00:13 the .swu file is one output from the babic's swupdate process Jul 30 21:02:48 i see that there is a built-in "do_rootfs" routine which is part of a standard set of image tasks. but i want to build a "linux" fs (zImage + .dtbs in a fat32), not a rootfs Jul 30 21:04:38 what distinguishes an "image" recipe from a "non-image" recipe? Jul 30 21:05:34 WHAT DISTINGUISHES AN "IMAGE" RECIPE FROM A "NON-IMAGE" RECIPE? Jul 30 21:09:20 WHAT DISTINGUISHES AN "IMAGE" RECIPE FROM A "NON-IMAGE" RECIPE? Jul 30 21:12:34 yates: whether the recipe inherits the image class. "inherit image" Jul 30 21:12:53 and screaming and repeating yourself isn't particularly productive Jul 30 21:19:39 what does the syntax "python () {...}" accomplish in .bbclass files? Jul 30 21:20:07 how are such functions invoked? by what name? Jul 30 21:28:58 is it true that all non-manual tasks (https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#ref-tasks) get invoked when running bitbake, but the bbclass files which some recipes may not define every task function, so that function basically does nothing? Jul 30 21:29:23 s/which some recipes/which some recipes are based on/ Jul 30 21:29:24 by default bitbake runs the do_build task (specifically, the task defined by the BB_DEFAULT_TASK variable) Jul 30 21:29:41 it runs any tasks that do_build depends on Jul 30 21:30:04 addtask foo creates a task that has to be run manually, addtask foo before do_build or before some otehr task that's run by default, will be run automatically Jul 30 21:35:14 how do you make do_build depend on a task? Jul 30 21:40:59 kergoth: are you saying the addtask (after/before) mechanism is precisely how you accrete dependencies to the do_build task? Jul 30 21:41:02 i just told you Jul 30 21:41:03 yes Jul 30 21:41:08 within a recipe, anyway Jul 30 21:41:21 cross-recipe dependencies are defined with DEPENDS/RDEPENDS_ and various variable flags Jul 30 21:41:44 i see Jul 30 21:41:51 but yes, before == the other recipe runs after this task, aka depends on this task, and after is vice versa Jul 30 21:55:09 yates: you could look at https://github.com/Freescale/meta-fsl-arm/blob/master/classes/image_types_fsl.bbclass. _generate_boot_image() Jul 30 21:56:44 thanks justinttt Jul 30 21:57:28 again, what does the syntax "python () {...}" accomplish in .bbclass files? Jul 30 21:59:31 see the bitbake user manual, it covers the file format Jul 30 22:01:59 see Anonymous Python Functions Jul 30 22:05:11 yates: https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#bitbake-style-python-functions Jul 30 22:08:08 yates: here is the source of some of the bitbake utils functions to look at. https://github.com/openembedded/bitbake/blob/master/lib/bb/utils.py Jul 30 22:29:58 armpit: We can't take that rm_work patch for sumo, it breaks things. There are fixes from me in master to rm_work but its invasive Jul 30 22:34:53 RP, ok Jul 30 22:38:34 armpit: I did merge the rest, thanks! Jul 30 22:41:22 np. glad I can help Jul 30 23:05:36 rsalveti: I think a patch I just posted should fix your hardlink issue in package.bbclass Jul 31 00:41:51 Hello, I'm in the middle of bring-up for a custom intel x86-based board with a linux-based OS created using yocto. I'm currently working on getting the kernel to boot into userspace, but there seems to be some issue with the initramfs live installer. The last kernel log I see through the UART console is "Freeing initrd memory...". And then nothing else. Jul 31 00:44:08 I think this could be caused by a number of things. One of them being that the userspace init program is logging out to /dev/console, but I'm not connected to the right console for userspace applications (kernel was started with console=tty0 console=ttyS0,115200 and i do get kernel logs) Jul 31 00:44:30 the other possibility would be something incorrectly configured in the initramfs. Jul 31 00:45:13 Right now I'm looking for documentation on the initramfs system that seems to be included with OpenEmbedded by default. Where would I be able to find this? Jul 31 00:48:24 RP: awesome, will give it a try tomorrow, thanks for fixing the issue! Jul 31 01:55:31 robbawebba: I think there was issues with the console, can you try hooking up a monitor to your device to make sure its not getting a different output?, also you can try adding debug prints to the init script to see if it actually gets started Jul 31 02:03:22 aehs29: Thanks for the suggestion! Do you know if the discussions around this issue were in the mailing list, a bug tracker, or elsewhere? Jul 31 02:04:41 aehs29: unfortunately HDMI is not an option at the moment since the necessary lines for HDMI display are not fully hooked up to the CPU. I Jul 31 02:05:18 'll doublecheck with my colleague if we can enable HDMI output somehow Jul 31 02:06:25 aehs29: I've given the log outputs a shot, but no luck there. I'm about to try a custom initramfs that just enters a busybox shell. Jul 31 02:24:07 robbawebba: You can try bugzilla, Im sure there are bugs about the serial stuff, there was different behavior on genercix86 and core2/i7 machines, look that up Jul 31 02:24:28 robbawebba: debug prints to /dev/kmsg you should be able to see (I think) Jul 31 02:25:47 robbawebba: you can try with poky-tiny that does a little more than just dropping to shell Jul 31 02:26:44 robbawebba: poky-tiny + core-image-tiny from meta-intel **** ENDING LOGGING AT Tue Jul 31 03:00:00 2018