**** BEGIN LOGGING AT Mon Mar 05 03:00:03 2018 Mar 05 07:46:07 morning everyone Mar 05 07:46:45 how do I check YP compatibility for a layer that's compatible with morty Mar 05 07:47:08 the yocto-compat/check scripts came in during rocko Mar 05 07:47:35 so when I try to run those I get a bunch of "no recipes available for" errors Mar 05 07:47:40 which makes sense Mar 05 07:47:51 as my layer is only targeted for morty Mar 05 08:54:45 hi! Since I upgraded to pyro, I noticed that my kernel module packages have "-${LINUX_VERSION}${LINUX_VERSION_EXTENSION}" as new suffix. I used to add files to my kernel module packages (FILES_${PN} += "my_file"). How can I do that now? FILES_${PN}-${LINUX_VERSION}${LINUX_VERSION_EXTENSION} doesn't seem to be valid (I believe ${LINUX_VERSION}${LINUX_VERSION_EXTENSION} is expanded to ""). Mar 05 09:32:22 New news from stackoverflow: Cross Compiling libfreefare-pcsc Error Mar 05 10:26:03 Guys, can you point to wiki on how to add docker to target rootfs? Mar 05 10:27:28 zks: here it is, in meta-virtualization: http://layers.openembedded.org/layerindex/recipe/33269/ Mar 05 10:28:36 LetoThe2nd: Yeah. This is the recipe. But i'm looking for how-to or tutorial... Mar 05 10:29:25 zks: um, whats more to it than just adding it to your image? Mar 05 10:30:02 LetoThe2nd: Not sure... Probably nothing more. Mar 05 10:30:12 :-) Mar 05 10:30:29 LetoThe2nd: So, is it just [CORE_IMAGE_EXTRA_INSTALL = ]? Mar 05 10:30:52 LetoThe2nd: So, is it just [CORE_IMAGE_EXTRA_INSTALL = docker, bitbake core-image-XXX, runqemu...]? Mar 05 10:31:20 zks: erm, are you talking about the bash invocation, or what? Mar 05 10:31:36 zks: i mean... hopefully you have already a custom image? Mar 05 10:32:05 LetoThe2nd: I'm using core-image-full-cmdline with QEMU-x86. Mar 05 10:32:31 zks: well then, your first step is: create a custom image, and base it off core-image-full-cmdline. Mar 05 10:32:42 after that, just add it in there. Mar 05 10:33:11 LetoThe2nd: Why should I create a custom image (I just lack a knowledge here :-)? I can just use CORE_IMAGE_EXTRA_INSTALL... Mar 05 10:34:07 zks: because of reproductibility and ease of reuse. chances are extremely high that this is not the only modification you'll want to make, and it becomes very painful quickly if you just pile up stuff in local.conf Mar 05 10:34:27 LetoThe2nd: got it. Mar 05 10:34:28 oO( everybody tries to avoid creating images ) Mar 05 10:34:54 LetoThe2nd: But apart from the custom image - is this only to add a "docker" recipe? Mar 05 10:35:08 LetoThe2nd: ... or some additional configuratin should be done anyway?... Mar 05 10:35:24 the other method is to pile up stuff in either local.conf or your distro config. Mar 05 10:35:51 which is both a bad idea, unless you have very specific reasons (in which case you wouldn't have to ask) Mar 05 10:37:13 LetoThe2nd: Ok. Got it. Custom image. Mar 05 10:37:17 LetoThe2nd: Thanks man! Mar 05 10:37:24 have fun. Mar 05 10:38:43 LetoThe2nd: I've written a PPT to try to push the employer to Yocto. 20 slides. Would you mind to take a look? Mar 05 10:38:49 LetoThe2nd: https://docs.google.com/presentation/d/1QptRMjq7BhU2ApDuoKKh30ww8jpi3QW7nyaCP4iai_k/edit?usp=sharing Mar 05 10:39:49 LetoThe2nd: No hard details, only high-level examples for CTO/CEO types. Mar 05 10:43:39 Also, about my kernel module problem, it seems that kernel-module-XXX_VERSION-YYYY.ipk are not installed anymore. Only kernel-module-XXX-${LINUX_VERSION}${LINUX_VERSION_EXTENSION}_VERSION-YYYY.ipk seem to be installed. Is it normal? Mar 05 10:45:42 zks: THB, your examples are pretty much all flawed. Mar 05 10:46:15 LetoThe2nd: Thanks man for your time. All the examples are extremely simplified. Mar 05 10:46:48 LetoThe2nd: ... to the point of not being correct - just to convey the sence of what needs to be done. Mar 05 10:48:12 zks: 1) no need to build packages before adding them 2) adding them via env on bibake image is a really bad idea. 3) youtube stuff is totally NOT advised Mar 05 10:48:49 well if you want to convey actually incorrect information for the sake of getting your intentions across... its your decision. Mar 05 10:50:28 its jsut that things like these have the tendency to pop up in other contexts again and cause trouble Mar 05 10:51:41 LetoThe2nd: Well, I'm fixing the stuff according to your comments. I just lack the knowledge yet to pinpoint the killer-feature examples. Mar 05 10:52:35 the killer features vary heavily between users, so its hard to tell what is helpful for you, or actually being complicated. Mar 05 10:53:48 read that as: "really think about what will help your product and company, and not what you like personally. there are other choices too." Mar 05 10:55:27 LetoThe2nd: I'm well familiar with the other choices - buildroot, Ubuntu-based distro, no-distro-at-all, anything in-between. Mar 05 10:55:38 one thing that often is helpful is license tracking, for example. Mar 05 10:56:39 LetoThe2nd: The best option apart from Yocto would be Ubuntu-snapshot distro for MPV and buildroot for the production. Mar 05 10:58:16 LetoThe2nd: But all of them suck IMHO. Buildroot - fast bootstrap, hard to maintain between various products. Ubuntu-based - not reproducible, not rebuildable, not tracked to the any version (no git commit), no-distro-at-all - is a real pain in the ass. Mar 05 10:59:16 LetoThe2nd: Actually, the license tracking - I think both R&D and suite-guys do not care... Mar 05 11:00:00 like i said: its important to iron out things that matter for your business. and to be honest: licenses should care. especially if you sell things, and are not just doing consulting. Mar 05 11:14:13 LetoThe2nd: Thanks man. I'll add the license stuff - the company sells routers after all... Mar 05 11:19:28 i know it's not strictly supported, but does anybody have any pointers on getting poky building on Debian Sid? Mar 05 11:26:54 LetoThe2nd: BTW - I really appreciate your time. I do not take your kind support for granted. Mar 05 11:27:14 LetoThe2nd: Shit,... I'm too soft-hearted today ... )) Mar 05 11:27:28 * LetoThe2nd did not try to be kind :-) Mar 05 11:28:48 BCMM: the better way probably is to say what problems you are seeing. Mar 05 11:29:50 LetoThe2nd: had a few different ones, so i decided to just go back to the "quick start" instructions and try to build an example image Mar 05 11:30:15 my current blocking problem is e2fsprogs-native, i'll pastebin the log... Mar 05 11:32:01 http://dpaste.com/05AD16Y Mar 05 11:33:26 BCMM: is this master HEAD? Mar 05 11:34:10 Do you know how can I change the version of kernel in meta-xilimx ? Mar 05 11:34:37 LetoThe2nd: no, this is following http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html exactly Mar 05 11:35:31 LetoThe2nd: i'm not to good with git stuff to be honest - does "master HEAD" just mean the source i get by doing "git clone" and nothing else? Mar 05 11:36:37 BCMM: yeah Mar 05 11:42:01 LetoThe2nd: i had the same error on a very recent git pull, but to be fair that was on a more complicated image and i suppose there could be something funny in my local config there Mar 05 11:42:13 should i try and build core-image-minimal on the latest head? Mar 05 11:42:51 BCMM: well, slimming down test cases is always a good idea. :-) Mar 05 11:43:45 LetoThe2nd: i know basic git questions are probably offtopic, but what's the best way to get back to head after following the instructions in qs? Mar 05 11:43:57 (i could just clone again but that seems like a waste) Mar 05 11:45:06 BCMM: well.... unless you did actively modify files that the checkout brought you, you never left head. Mar 05 11:45:44 BCMM: so i guess that there's no action needed. Mar 05 11:46:04 LetoThe2nd: "The previous Git checkout command creates a local branch named poky_2.4.1. The files available to you in that branch exactly match the repository's files in the rocko development branch at the time of the Yocto Project 2.4.1 release." Mar 05 11:46:13 i may have understood that incorrectly, then Mar 05 11:47:51 BCMM: ah, they have changed it, then. Mar 05 11:48:11 LetoThe2nd: yeah, i'm sure when i first started out on yocto the qs just went to the latest code Mar 05 11:48:23 try to give it git reset --hard; git clean -df; git checkout master Mar 05 11:49:13 "Your branch is up to date with 'origin/master'." - thanks Mar 05 11:49:46 and meta-yocto-bsp = "master:bd5424f5b05a0a65471a77632efe7b9907370217 now Mar 05 11:49:56 instead of roco:something Mar 05 11:50:38 hmm it's not falling over immediately any more. i'll wait and see what happens i guess; thanks. Mar 05 12:05:52 LetoThe2nd: ah, now i'm back to the problem that I had with my "real" build - "*** These critical programs are missing or too old: GNU ld" when configuring libc Mar 05 12:05:56 http://dpaste.com/3VKRDH3 Mar 05 12:08:41 and i can't find much on google that isn't gentoo-specific for that. any chance it's a misleading message that can also be triggered by ld being too *new*? Mar 05 12:12:13 how can I find the src_uris of all recipies? perhaps all recipes used in an image... Mar 05 12:23:27 ernstp: for some sort of manifest i presume? Mar 05 12:23:47 ernstp: distrodata has several tasks that almost do that, easy to copy/paste and edit Mar 05 12:24:16 ah, a task... Mar 05 12:27:08 rburton: thanks for the pointers. will read up on distrodata.bbclass and distro_check.py... Mar 05 12:27:27 or, use tinfoil to iterate the datastore Mar 05 12:28:10 scripts/verify-bashisms (if you ignore the multiprocessing) is basically a loop over all recipes Mar 05 12:28:42 actually scripts/contrib/verify-homepage is even samller Mar 05 12:30:08 ah yes! that's actually what I want... an api for the parsed data. Mar 05 13:01:12 zeddii: ping Mar 05 13:01:20 zeddii_home: ping here too Mar 05 13:02:22 Any idea why my board hangs on "Starting kernel ..."? I tested other uImage and works but the uImage generated from yocto isn't working Mar 05 13:33:08 New news from stackoverflow: CMake won't find_path in yocto environment, but will with same repo and cmake outside of yocto Mar 05 14:25:34 RP: I ran the check script against meta-ti and it still has some issues so I won't ack its approval on YP Compatible until it is fixed. Mar 05 14:27:19 Hey guys, I'm trying to figure out where in my recipes can I disable the serial console from starting on ttymxc0 (specific to the imx6). I'm quite new to yocto and I've only worked on one board so far so let me know if you need some more context as I'm not entirely familiar with this whole thing :) Mar 05 14:28:43 flying_sausages: it has a variable on the machine file (SERIAL_CONSOLE). Set it to = "" and it should do the trick Mar 05 14:29:00 can you elaborate on machinefile please? Mar 05 14:29:21 conf/machines/.conf Mar 05 14:29:31 ah right yes was looking at that earlier Mar 05 14:31:37 otavio, if I want to make a file that will make this ad-hoc change without editing the .conf itself, how could I make this happen? through a bb? bbappend? Mar 05 14:34:35 what is the difference between env and envtools when using or_runmake? Mar 05 14:53:32 seebs: I've cleaned up a few pseudo-related issues in YP bugzilla; can you take a moment and look at remaining ones (close/comment/update status/etc.)? Thanks :) Mar 05 14:53:33 https://bugzilla.yoctoproject.org/buglist.cgi?list_id=605970&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=IN%20PROGRESS%20REVIEW&bug_status=REOPENED&bug_status=NEEDINFO&component=pseudo Mar 05 14:55:12 seebs: oe-core master pulls in d7c31a25e4b02af0c64e6be0b4b0a9ac4ffc9da2 of pseudo, I believe Mar 05 14:57:44 Hello yocto experts, can somebody please help me with followeing question? I am building a recipe which relies on a header file from a propritary header-file which is placed within kernel source. Now i have to get access to that header file. Therefor i added DEPENDS += "virtual/kernel" and do_configure[depends] += "virtual/kernel:do_shared_workdir" to my recipe. But somehow the linux/include is not within my recipes-sysroot. Any ide Mar 05 15:46:20 mwiesing: I think that is caused by the "kernel headers" not being the same as "the kernel"... I think you would have to do something special to get your user space application to get the headers from "the kernel", but usually isn't not something you would want to do Mar 05 16:03:49 Hey again, so I think I found the culprit to my previous issue, it was the serial-getty@ttymxc0.service which would still get started even if it was disabled. I then masked it with systemctl mask (servicename). How can I achieve this on the image I'm building? I traced the "cause" to be in sources/poky/meta/recipes-core/systemd where there's a systemd-serialgetty.bb and a folder with the same name but no .bb Mar 05 16:07:48 flying_sausages: disable in systemd speak does not mean disable for normal mortals ;) systemctl mask just creates a symbolic link to /dev/null. IIRC it even prints out what it creates. I created a do_install_append somewhere, which just creates the same symbolic link to /dev/null under ${D} Mar 05 16:08:26 @kanavin, thanks for posting the list. I had forgotten about the ./.. bug, I think that's old enough that it was on my "when management lets me put some time into this" list back at WR. :P Mar 05 16:09:26 new longer status report sent out this week, i hope people enjoy the extra detail Mar 05 16:10:37 seebs: the list is simply all the pseudo bugs that aren't resolved verified or closed :) Mar 05 16:11:02 seebs: shame that the host contamination issue is still with us :( Mar 05 16:12:26 seebs: how is your job search going? Mar 05 16:22:48 u1106, I added PACKAGE_EXCLUDE +=" systemd-serialgett" and got what I wanted in the end Mar 05 16:23:47 Now I need to figure out how to automatically run a script on boot time from the recipe, any pointers where I can bounce off of? Mar 05 16:30:32 I don't know. Nothing solid yet, anyway. It turns out that "remote only" is a significant barrier sometimes. Mar 05 16:30:44 I think this would be less true if people looked at performance statistics. :P Mar 05 16:31:41 seebs: are you in the US? Mar 05 16:33:51 seebs: fwiw, when recruiters approach me, I act super interested, but then tell them I'm not relocating :) they seem to have this strange idea that moving to another country, or continent is not a big deal, while coming to office is very important. I think we should all try to change that mentality little by little :) Mar 05 16:34:13 Yeah, I am in the US. Mar 05 16:34:42 I've got apps out to a handful of places that look interesting, I'll see whether anything comes of it. My least favorite part of the thing is the bit where it takes weeks to hear back on things. Mar 05 16:35:28 I last commuted in the mid-90s. I figure I have a pretty good idea how necessary it is. Mar 05 16:35:49 seebs: the worst is when they also ignore questions about it, and then still many weeks later send you an anonymous, generic rejection Mar 05 16:36:18 Hi, guys! I have a seemingly simple question that I don't know an answer to. Will be grateful if anyone could pitch in and help. I need to make a recipe for an out-of-tree kernel module which needs a device tree overlay for its work that is compiled alongside the code (make will do its thing and generate a dtbo file in the root directory of the module). Then I need to take this dtbo and transfer it to the Mar 05 16:36:24 /boot/overlay directory. Is there any advice for this scenario? Mar 05 16:46:49 anybody got any idea about this failure to configure glibc? http://dpaste.com/3VKRDH3 Mar 05 16:47:01 i'm not sure where the ld binary it's trying comes from Mar 05 16:52:53 if i just execute them manually, other binaries in tmp/work/i586-poky-linux/glibc-initial/2.27-r0/recipe-sysroot-native/usr/bin/i586-poky-linux work Mar 05 16:53:19 but i get ./i586-poky-linux-ld: /home/ben/poky-test/poky/build/tmp/sysroots-uninative/x86_64-linux/lib/libc.so.6: version `GLIBC_2.27' not found (required by ./i586-poky-linux-ld) Mar 05 16:55:29 i'm trying to build u-boot getting erro "make: *** No rule to make target 'envtools'" with oe_runmake envtools, anybody have idea that is it a problem on u-boot side? Mar 05 16:57:03 i can compile u-boot with oe_runmake env but then objcopy get format problem with fw_printenv binary Mar 05 17:03:48 New news from stackoverflow: aggregate several software modules into one package Mar 05 17:25:25 I think I found a bug: I have 2 kernel modules recipes. In every recipes, I add some files to FILES_{PN}. But only 1 of the 2 recipes has its files installed. Both .ko are installed. The main difference is in the name of the recipes: the one which doesn't see its files installed has a name close to the name of the .ipk generated with the .ko. If I rename the my recipe adding '-driver' the files are installed. Mar 05 20:19:58 zeddii: can i expect a new devsrc patch today? Mar 05 20:20:01 zeddii_home: ^ Mar 05 20:21:02 unfortunately not. ppc and mips needed a tweak for 4.15, which I fixed, and am rebuilding now. I’ll send my whole queue late tonight, but too late for GMT. Mar 05 20:21:51 ok, maybe tomorrow. :) Mar 05 20:21:58 thanks Mar 06 01:00:04 * armpit boy is this going to be fun Mar 06 01:01:25 * armpit me first, no me first, no me first... Mar 06 01:19:43 yoctoproject.org transition to the new site? Mar 06 01:21:33 Seems like it...I cant seem to access the docs anymore :-( Most or every doc link gives "Not Found" Mar 06 01:22:07 hunter522: Yes - here also. No doc access at all. Mar 06 01:26:53 scottrif, we are but I though ti wasn't until next week Mar 06 01:27:27 oh cool. its live Mar 06 01:29:57 working on getting the docs back... Michael helping Mar 06 01:41:41 halstead fixed the docs :) Mar 06 01:43:34 thanks Mar 06 01:44:54 sweet! thanks :-) **** ENDING LOGGING AT Tue Mar 06 03:00:02 2018