**** BEGIN LOGGING AT Wed Feb 15 03:00:01 2017 **** BEGIN LOGGING AT Wed Feb 15 09:15:16 2017 Feb 15 12:06:13 i there a way to cleanup those hash? I can't get through these erros... Feb 15 12:06:22 hi everyone Feb 15 12:06:25 i have errors like : ERROR: Taskhash mismatch dc3543e66b52acc379ec340f0c3f7703 verses 581ae57e28e43d6c41e72240a2c01f04 for ... Feb 15 12:06:31 I would like to cleanup the hash Feb 15 12:07:23 something's changing in the metadata between parse and execution time, most commonly that's when a recipe uses DATETIME and the fix would be to add it to vardepsexclude for the task/variable Feb 15 12:08:31 you might be able to debug better by looking at the task signatures https://wiki.yoctoproject.org/wiki/TipsAndTricks/Understanding_what_changed_(diffsigs_etc) Feb 15 12:09:16 joshuagl, I'm modifying a file in the rootfs_postprocess in the image (I tried inside the receipe but it was not good at all) Feb 15 12:11:10 joshuagl, thanks for the link Feb 15 12:12:28 aurele: modifying files in the rootfs with ROOTFS_POSTPROCESS_COMMAND is common (see rootfs-postcommands.bbclass) so it's nothing intrinsic to that, you'd need to share specific or use the tools above Feb 15 12:12:32 np Feb 15 12:36:27 what is the best way to overwrite/modify a file coming from one layer in a .bbappend file? Feb 15 12:41:53 CoLa|work, I would say bbappend to modify the behaviour or add some treatment (new file, remove a file, and so on), but if I want to change the version I usually use a new receipe Feb 15 13:39:09 question: how do I preserve debugging symbols in a native binary? Feb 15 13:39:21 the issue is that rpmsign is crashing, and I need to debug it Feb 15 13:48:44 kanavin: I started to write a tips&tricks about that, 2s Feb 15 13:48:50 https://wiki.yoctoproject.org/wiki/TipsAndTricks/DebugNativeRecipeWithGdb Feb 15 13:54:04 joshuagl: thanks, I might have an addition to that.... Feb 15 13:54:10 (will figure it out in a moment) Feb 15 13:54:31 kanavin: that'd be great, thanks Feb 15 13:55:46 joshuagl: before I figure out the addition, I think set sysroot /path/to/build/tmp/sysroots/x86_64-linux no longer works in rss world Feb 15 13:56:17 kanavin: hmm, suspect you're right Feb 15 13:57:52 joshuagl: another thing is that I believe you need to also compile the source code with -g, or you won't be able to do much useful debugging, but I need to confirm this Feb 15 14:01:41 joshuagl: yep, you need to ensure -g Feb 15 14:02:08 otherwise, even though the binaries are not stripped, they don't have the debugging info in the first place, so you'll get a function call trace and nothing else Feb 15 14:03:29 kanavin: please update the wiki :-) Feb 15 14:07:20 joshuagl: apparently wiki account creation goes through a human, so can't do it immediately Feb 15 14:08:34 kanavin: approved, go wild Feb 15 14:17:25 joshuagl: there you go Feb 15 14:17:42 for me fiddling with sysroots seems unnecessary, gdb just magically finds everything Feb 15 14:18:23 kanavin: nice, thanks for updating! Feb 15 14:20:05 HOORAY MAGIC Feb 15 14:20:08 Feb 15 14:25:18 Hello, I have created an image with my defined recipes. Is it possible to get the version of the build on the image ? Or the Version of every package ? Feb 15 14:29:26 Hunk: you mean after building it, or you mean at runtime of the image? Feb 15 14:29:42 on runtime of the image Feb 15 14:31:52 Hunk: http://cgit.openembedded.org/openembedded-core/tree/meta/classes/image-buildinfo.bbclass?h=master Feb 15 14:33:05 nice ty Feb 15 16:36:41 Hi... I just failed at sending a series of patches with cover letter (https://patchwork.openembedded.org/series/5333/#) I suppose I didn't use the right subject in the cover mail. Is there any way to fix that ? (First time I tryed to send a patches with a cover) :/ Feb 15 16:42:04 Okay, big fail on that one, even patches names are wrong Feb 15 17:21:55 hi all. I currently have a custom defined machine (arm64 based, let's call it hw1) used to build custom image (let's call it image-dev). Everything work pretty fine. My problem appear while trying to generate a sdk for this couple: the problem is that it fails at the final step of do_populate_sdk while trying to install packagegroup-cross-canadian-hw1.deb. I can't find any package with `find build/ -iname "packagegroup-cross*.deb" Feb 15 17:22:31 any idea ? Feb 15 17:23:37 if i run bitbake packagegroup-cross-canadian:do_cleanall and then bitbake packagegroup-cross-canadian Feb 15 17:24:26 everything run fine and with no error but i still get no package generated Feb 15 18:05:37 * paulg just sent a fix for http://errors.yoctoproject.org/Errors/Details/130583/ in case anyone else was looking at it. Feb 15 18:37:49 hello all Feb 15 18:41:13 I have a quick question regarding packages. I am getting an error do the root_fs task that reads Feb 15 18:41:16 Computing transaction...error: Can't install packagegroup-core-frick-devtools-1.0-r0@all: no package provides libxl Feb 15 18:42:54 The recipe can be found at https://gist.github.com/wrrn/0a69fa93134d54dd717c062a6de32ea2 Feb 15 18:43:28 If I add PACKAGES = "${PN} Feb 15 18:43:55 it works but if I space append to PACKAGES with the += Feb 15 18:44:11 I get an error saying that libxl is in the package list twice Feb 15 18:44:29 I was wondering why that is the case Feb 15 18:48:56 there's no need to override PACKAGES. easiest to just adjust FILES so ${PN}-dev doesn't grab it anymore Feb 15 18:48:57 FILES_${PN} += "${libdir}/*.so" Feb 15 18:48:57 FILES_SOLIBSDEV = "" Feb 15 18:48:59 will do it Feb 15 18:50:47 Thanks Feb 15 18:59:27 If I just included libxl-dev instead of libxl would I need to make those changes? Feb 15 19:04:03 It is erroring out if I include libxl-dev with this new version of the recipe: https://gist.github.com/wrrn/0a69fa93134d54dd717c062a6de32ea2 Feb 15 19:04:18 The error reads Computing transaction...error: Can't install libxl-dev-1.0-r0@cortexa9hf_neon: no package provides libxl = 1.0-r0 Feb 15 19:07:14 The error is occuring during the rootfs task Feb 15 19:18:35 Hi everyone, I've been using Yocto for the last few months and I've learned the basics. I have create a BSP for a custom board for an industrial camera and I've created my own recipes and such. Feb 15 19:18:45 With the basics covered, can anyone recommend Yocto resources (books, web links, etc...) that describe the steps needed turn a basic Yocto embedded Linux distribution to a production ready embedded Linux distribution? Most general information I find in books and on the web seem geared towards getting people introduced to Yocto. There seems to be less information on best practices around bring a system to production. Feb 15 19:18:56 I'm wondering if I overlooked some resources on this topic that others have found useful. Feb 15 19:36:57 mpthompson: thats a good point, usually yocto project enables with tools and processes that helps poeple define their production process. I think there are probably less documents or posts on usecases in production, I have been deploying it in several different products and while its true that the tools and processes help I dont think there is one single production recipe it differs from company to company Feb 15 19:37:19 probably I should do some blogposts on this :) Feb 15 19:38:04 I have heard on Mars a day is 24hr 40mins ( earth hrs ) so if I go to mars I will get that 25th hr in the day Feb 15 19:38:48 yeah, i dont' think you can really have best practices on the flow to production, but having some solid examples for different cases would probalby be well received Feb 15 20:30:56 hello, i've asked in #gnu and #linux but I did not get a response. Any of you smart guys know of a channel where I could talk about version 3 api of libnl (netlink) sockets? Feb 15 20:52:04 khem: thanks for the response. It would be good to see a white paper or other type of document that describes how other's have approached using Yocto in an actual product production cycle. Feb 15 20:52:42 i wouldn't be surprised if some of that is done by some of the OSVs with yocto-based products Feb 15 20:53:53 I'll be examining what Wind River has done with Yocto. Some of their documents describing Pulsar come close to what I'm seeking, but they are pretty skimpy. Feb 15 20:56:26 davis: #kernel Feb 15 20:57:11 Circuitsoft: thanks Feb 15 20:58:03 Networking question: My network bridge config doesn't come up automatically on boot. Running either "ifup -a" or "ifup br0" fixes it. Any ideas why it wouldn't? Feb 15 20:58:33 networking/interfaces does say "auto br0" Feb 15 20:59:37 you could put if-up br0 in your rc.local ? Feb 15 21:00:30 There isn't one. Is it automatically created (Yocto krogoth)? Feb 15 21:01:07 sorry....I dunno. was a guess. Feb 15 21:01:24 that's what I always used2do. Feb 15 22:02:15 join Feb 15 22:02:22 Hi All Feb 15 22:02:44 Can some one help me my fetch is failing Feb 15 22:02:51 reddy_: you're using an invalid url Feb 15 22:03:01 go read one of the hundreds of other git recipes, or the bitbake or yocto documentation Feb 15 22:03:28 but when i do git clone git@abc-gitlab.xyz.com:Platform/abc-ip.git Feb 15 22:03:40 irrelevent Feb 15 22:03:41 it perfectly pulls the srcs Feb 15 22:03:49 bitbake uses its own fetcher, it doesn't blindly copy entries from SRC_URI to the underlying commands Feb 15 22:04:30 how i should proceed on thi splease Feb 15 22:04:55 confused when i do git colne it get sthe sources but the same path fails in recipe Feb 15 22:05:43 http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#var-SRC_URI Feb 15 22:05:46 http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#new-recipe-makefile-based-package Feb 15 22:05:49 i just told you Feb 15 22:05:55 [15:03:01] go read one of the hundreds of other git recipes, or the bitbake or yocto documentation Feb 15 22:06:21 i ll ook at the of the examples Feb 15 22:06:24 http://www.yoctoproject.org/docs/2.2/bitbake-user-manual/bitbake-user-manual.html#git-fetcher Feb 15 22:06:44 i read that part Feb 15 22:06:59 then read it again. nowhere does it say you can drop foo@bar.com and expect it to know that's git Feb 15 22:07:04 it explicitly states git urls start with git:// Feb 15 22:07:58 hhmm got what you said thanks .. my bad i over looked that part Feb 15 22:09:15 Change git@abc-gitlab.xyz.com:Platform/abc-ip.git to git://git@abc-gitlab.xyz.com/Platform/abc-ip.git;protocol=ssh and it'll work fine Feb 15 22:09:32 but again, *read the documentation* or one of the *hundreds* of existing git recipes that all use the correct syntax in the future Feb 15 22:12:24 kergoth: thanks you so much Feb 15 22:12:33 np Feb 16 01:09:54 hi Feb 16 01:10:21 can someone point me how to access architecture or machine specific dadat in recipe Feb 16 01:10:32 *data **** ENDING LOGGING AT Thu Feb 16 03:00:01 2017