**** BEGIN LOGGING AT Fri May 12 03:00:03 2017 May 12 05:09:15 1000 open files should mean 1000 *processes*, not just threads. Although I guess once you have multiple tasks in parallel, too. Hmm. May 12 05:56:13 can I use yocto to create x86 images? It seems kernel is qemu only May 12 05:57:48 sobczyk: of course xou can. standard MACHINEs would be generic-x86 and generic-x86-64, these days. May 12 05:58:12 sobczyk: see also https://www.yoctoproject.org/downloads/bsps/pyro23/generic-x86 May 12 07:14:38 I try to resize my yocto root partition. But I always have some error messages. https://pastebin.com/wdjyqpyn Someone can help me please ? May 12 07:16:47 hamdyaea: well are you trying to a) unmount a partition in use b) do this on a ro medium? May 12 07:19:34 LetoThe2nd, : I can't umount it : https://pastebin.com/X5sxV827 May 12 07:19:47 LetoThe2nd, : What's a ro medium ? May 12 07:20:02 hamdyaea: ro = read only May 12 07:20:07 LetoThe2nd, : read-only ? no I can write and read May 12 07:20:31 LetoThe2nd, : It's an hddimg not an iso May 12 07:21:02 hamdyaea: realroot just souds like this is some tricky environment. like an overlay involved, or such. can you please put a full output of "mount" onto a pastebin? May 12 07:24:25 LetoThe2nd, : https://pastebin.com/CSaiyaSN May 12 07:26:23 hamdyaea: just as expected. your / is a loopmount onto something that is probably in /mnt/realroot. so as long as the system is running, you certainly cannot unmount /media/realroot May 12 07:27:00 hamdyaea: i'd rather suggest to look at how the hddimg is created and then modify it accordingly, instead of doing weird magic later. May 12 07:42:11 LetoThe2nd, : You mean that I can modify the local.conf to change the size of my .hddimg ? May 12 07:42:30 hamdyaea: that is not what i said. May 12 07:43:18 hamdyaea: i said "look up how it is created, and then change it accordingly" that *might* be just setting a value in your .conf, but it also might be something different May 12 07:43:37 LetoThe2nd, : The system is on a flash card. When I connect the flash card on my computer I can't see what's inside /dev/sda/ I just see 13 go free and I can't resize it May 12 07:44:14 how is that realted to what i just said? May 12 07:44:52 LetoThe2nd, : I don't know what more to do with the .hddimg May 12 07:45:04 rad it again one more time. May 12 07:45:14 i did not say "do something with the hddimg" May 12 07:46:03 LetoThe2nd, : I know but I try to find what to modify May 12 07:46:23 OK, so I'm a nebie. BUT, please explain this behavior: Deleteing build artifacts in build/tmp/deploy/image and then rerunning bitbake fails with an error: https://pastebin.com/URSjiJcf May 12 07:46:44 Why aren't the images simply regenerated if they are missing May 12 07:47:41 Is it really necessary to use a bitbake clean or the equivalent to force a regeneration of images May 12 07:48:55 LetoThe2nd, : maybe the image_type is not the best for what I am doing ? hddimg ? May 12 07:49:08 hamdyaea: thats almost certain. May 12 07:49:54 Hey, does anyone have a working recipe for Mysql server? May 12 07:50:06 hamdyaea: probaly the best way would be to create a wic script for your specific case. May 12 07:50:33 maka_: https://layers.openembedded.org/layerindex/branch/master/recipes/?q=mysql suggests that no May 12 07:50:54 maka_: mariadb is in meta-oe, however: https://layers.openembedded.org/layerindex/recipe/5974/ May 12 07:51:00 LetoThe2nd: That one doesnt work really tho May 12 07:51:15 LetoThe2nd: and i need the mysql database, not mariad May 12 07:51:36 maka_: "doesn't work really" is the second most useless error description. the most useless one is "doesn't work" May 12 07:51:45 maka_: well then have fun in creating the recipe :-) May 12 07:51:51 OK, let me ask the question a different way: What's the least "intrusive" way to force target images to be regenerated ? May 12 07:52:07 LetoThe2nd: thats why i asked if someone had a working recipe for mysql ^^ May 12 07:52:09 LetoThe2nd, : wic format don't work with my flash card and my computer. I can't boot it May 12 07:52:41 hamdyaea: thats probably not related to wic itself, but to the config script you picked. May 12 07:52:56 maka_: well you probably can steal some bits from mariadb May 12 07:54:02 hamdyaea: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image-live.bbclass suggests that hddimg is just an awful trick to have a live image May 12 07:54:03 LetoThe2nd: yea, ill try that. I'm troubleshooting my own recipe for it now, hoping to get that to work May 12 07:54:53 Smitty_: technically, probably because hddimg and friends are just awful tricks to generate live images, and do not perfectly respect dependencies. May 12 07:55:47 Smitty_: e.g. they require the kernel image to be existent to be bundled, but do not have the dependency as it is not packaged into the root filesystem. May 12 07:57:17 LetoThe2nd, : I don't want a live image May 12 07:57:30 hamdyaea: i guessed so, but technically you are using one. May 12 07:57:55 LetoThe2nd: So, 2 questions. What's the "right" way to generate a live image, and how do I force a regenerate of images May 12 07:58:49 LetoThe2nd, : The problem is that I am in Jethro branch and in Jethro the iso is a live image May 12 07:59:28 hamdyaea: iso is always a live image. you just should really look at wic, and use it to create the image that you *really* want, instead of using these workarounds. May 12 08:00:08 Smitty_: hard to say. as far as i can see, there is no direct way to recrate kernel images through bitbake'ing a live image. May 12 08:01:00 Do you know a kind of minimal "clean" command ? May 12 08:01:31 LetoThe2nd, : but the iso in the branch morty let you install the system on the hard disk. The problem is that I need a software that is just available in the jethro branch May 12 08:01:38 LetoThe2nd, : I will try a wic May 12 08:01:48 Smitty_: a workaround would maybe be to include the kernel in your IMAGE_INSTALL May 12 08:02:32 hamdyaea: then do forward port your software, thats an alternative May 12 08:04:41 LetoThe2nd, : How I can do that ? May 12 08:04:58 hamdyaea: umm May 12 08:05:20 hamdyaea: create your own layer, put the stuff in there, fix the recipes as needed, etc? May 12 08:08:07 LetoThe2nd, : My recipes if almost full working and complete. I just need to resize the partition May 12 08:08:26 hamdyaea: then look at http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/image-live.bbclass#n231 and go figure May 12 08:09:07 hamdyaea: this is how the hddimg is created. find out where the sizes are set, and act accordingly. May 12 08:12:18 LetoThe2nd, : # Check the size of ${HDDDIR}/rootfs.img, error out if it May 12 08:12:19 # exceeds 4GB, it is the single file's max size of FAT fs. May 12 08:12:39 LetoThe2nd, : It seems that hddimg don't accept more than 4 go because of fat May 12 08:13:01 hamdyaea: i wold you its an awful trick. don't complain. May 12 08:13:05 *told May 12 08:15:49 LetoThe2nd, : I'm bitbaking a wic to try again May 12 08:16:31 hamdyaea: bluntly bitbaking wic will probably not help you. you'll have to look at what it does, and modify that for your usecase. May 12 08:16:45 LetoThe2nd, : once it's finish I can just flash my card with dd ? I mean with the wic file May 12 08:18:17 LetoThe2nd, : I look, and if I do in other format like : ext4.gz or tar.gz =? May 12 08:18:34 ls May 12 08:18:46 hamdyaea: the documentation suggests that if the wic script is correct, you should be able to dd it. May 12 08:18:49 hamdyaea: ttp://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#building-an-image-for-hardware May 12 08:19:15 LetoThe2nd, : What about other format ? May 12 08:19:30 hamdyaea: for your last question, step back for a second and think about what a ext4 or a tar is. and what a storage image is. May 12 08:21:12 hamdyaea : you can dd a .wic file. May 12 08:21:23 hamdyaea : is what I do May 12 08:23:30 LetoThe2nd, ChrysD : I can't do a wic format in jethro branch... May 12 08:23:53 At this time there was not all kind of format availabe like today May 12 08:25:02 hamdyaea: then fix your recipes and port them to a current branch, instead of wating your (and our) time by beating onto old software. May 12 08:25:08 *wasting May 12 08:27:39 @all Hi all, i made a custom image_type under a custom image recipe. In fact it's just python functions to build a multi config FIT image. I would like to make a classe to clean my image recipe but i don't find any example or info about that ... any idea ? cheers :) May 12 08:28:35 pinkSnake: maybe you can be inspired by the stuff sbabic does for swu images: https://github.com/sbabic/meta-swupdate/blob/master/classes/swupdate.bbclass May 12 08:28:38 LetoThe2nd, : The soft I neet Python-gtk is not available on current branchs and my python soft can't run without it May 12 08:29:10 marex-cloud: maybe you can also say a bit about the fit stuff -> pinkSnake May 12 08:30:03 hamdyaea: you can't have old software and request new features. either backport the features you need and make it work manually, or forward port your software. thats the way life is. May 12 08:30:50 LetoThe2nd, : I just want to resize my partition I don't want to rebuild everything from 0 May 12 08:31:07 @LetoThe2nd first thx for the link, what do you want to know about fit ? May 12 08:31:58 hamdyaea: well then. i have given you all the pointers i have. i showed you how the hddimg is built, for you to modify it. i have told you wic is the correct way to go for current software. there's nothing more i can do. May 12 08:32:11 pinkSnake: i personally, nothing :) May 12 08:33:14 @LetoThe2nd --> maybe you can also say a bit about the fit stuff o.0 okay i didn't understand xD May 12 08:33:29 pinkSnake: i addressed marex-cloud :) May 12 08:33:52 pinkSnake : What about your problem with the password you wanted to remove from production recipe ? May 12 08:34:03 @LetoThe2nd i think i need a second coffee today ^^ May 12 08:34:21 @ChrysD still in progress but nothing yet May 12 08:34:22 pinkSnake: coffee often helps! May 12 08:38:22 I should definitely start drinking coffee then. May 12 08:42:23 LetoThe2nd: what? May 12 08:43:09 marex-cloud: pinkSnake wants to do some FIT magic. maybe you can give some pointers or say if there is already what is needed? May 12 08:44:16 What magic? May 12 08:44:40 pinkSnake: ping ^^^^^ May 12 08:46:30 @LetoThe2nd @marex-cloud i'm already able to do a FIT image with multiple configuration ( dts, bitstream, ramdisk and kernel) i would like just to how to do cleaner ^^ because i just put all my stuff in image recipe and it's look like dirty ^^ i'm currently follwing @LetoThe2nd link to try to make an image bbclass May 12 08:49:17 Afaik kernel-fitimage bbclass can already do the bundling of all the stuff May 12 08:55:58 @marex-cloud i agree but i need to add fpga bitstream inside too May 12 08:58:54 Extend the bbclass or even better, use FPGA manager in Linux to operate your FPGA, that's the preferred way May 12 08:59:01 Which FPGA is it? May 12 08:59:20 Anyway, I've an appointment with my dentist now, bb in 1.30 hrs May 12 08:59:40 @marex-cloud see you :) for info Zyn7000 May 12 09:28:20 I created some yocto image and for wich I had at the boot the boot menu who ask for install or live. Is there a way to force bitbake to create this bootmenu ? May 12 09:46:11 I created some yocto image and for wich I had at the boot the boot menu who ask for install or live. Is there a way to force bitbake to create this bootmenu ? May 12 10:14:34 pinkSnake: should be supported by the FPGA manager May 12 11:02:24 hi, are buildhistory variables documented somewhere? For example what are FILES in binary package latest file, FILELIST seems to be the actual file content list. May 12 11:03:19 trying to read poky/meta/classes/buildhistory.bbclass but not getting it.. May 12 11:07:18 I created some yocto image and for wich I had at the boot the boot menu who ask for install or live. Is there a way to force bitbake to create this bootmenu ? May 12 11:07:52 @hamdyaea what do you mean about bootmenu ? May 12 11:08:49 pinkSnake, : I mean at statup when the system ask you if you where to install the system May 12 11:09:11 @marex-cloud not yet :S and it's a good training to make my first yocto class :) good to know you are still alive #dentist May 12 11:09:35 @hamdyaea witch arch ? bootloader ? May 12 11:10:39 pinkSnake, : 64 bit , yes the bootloader May 12 11:11:34 pinkSnake : " good to know you are still alive #dentist " x) May 12 11:11:37 pinkSnake, : like the grub May 12 11:12:16 hamdyaea : What you are complaining about ? You have a bootloader in command line and you want a GUI ? May 12 11:14:07 ChrysD, : i don't have any boot loader. I want to be asked if I want to use the system live or install it. maybe I need that https://layers.openembedded.org/layerindex/recipe/40586/ May 12 11:14:53 hamdyaea : You have barebox and U-boot. But do you know what a bootloader is ? How to manage it ? Set the bootargs for your system ? May 12 11:15:22 @hamdyaea like grub or it's grub ? May 12 11:15:38 mcfrisk: FILES is the varibale from the recipe with the globs in, FILELIST is what *actually* is in the package May 12 11:15:41 @ChrysD +1 May 12 11:16:17 ChrysD, pinkSnake : I want to flash an usb key and boot on it then the boot ask me if I want to install it and on wich place like in /dev/sda etc.. May 12 11:16:58 @hamdyaea> arch ? x86 ? arm ? May 12 11:17:35 pinkSnake, : x86 May 12 11:18:03 @hamdyaea it's a custom board ? computer ? you should tell us more about the hardware :) May 12 11:18:40 @hamdyaea i'm not expert but with x86 platform you should use Grub May 12 11:19:16 hamdyaea: you basically want a custom startup script that either kicks off an installer or live usage. i don't think that such a thing is already provided. May 12 11:19:36 if the decision is to be made a t bootloader time or userland time is secondary. May 12 11:19:51 hamdyaea : But what is the purpose of your project ? More you speak about your project, more I feel like that you want a distro for a computer more than for embedded devices. May 12 11:20:49 pinkSnake, LetoThe2nd : When I boot with an image from branch poky. At the first boot it ask me where to install the system. I install it then I can remove my usb key. My hardware is 64 bit x86 generic.. May 12 11:21:17 hamdyaea: from branch poky. ah, yes. May 12 11:21:20 ChrysD, : This is a computer that I need to use like an embedded device May 12 11:21:43 LetoThe2nd, : I want to know if there is a way to have it like in poky branch ? May 12 11:21:57 hamdyaea : funny ahah. And why as an embedded device ? Can't you take a simple distro that you can customise ? May 12 11:21:59 hamdyaea: come on, you keep asking and asking and asking again about stuff that results from mixing various releases. just bite the bullet, do your homework and port the stuff like you need it. May 12 11:22:41 hamdyaea: if it is already in at least *ONE* branch, theres absolutely *NOTHING* that keeps you from looking at it how it is done, and applying it to your custom thing. May 12 11:24:12 ChrysD, : it's a commercial product and we don't want that the custommer can modify it and we want it to be lightweight May 12 11:24:44 LetoThe2nd, : My question is : Is there a package or something like this that I can install ? May 12 11:24:57 hamdyaea: hey you said "it is in poky branch" May 12 11:25:19 @hamdyaea take a look to grub sources dude May 12 11:25:20 hamdyaea: then look at "poky branch" May 12 11:25:43 * LetoThe2nd sighs and better leaves this for good. May 12 11:26:05 hamdyaea: you've just described the live images, they have a boot/install option in the boot loader May 12 11:26:41 rburton, : That's what I need .. May 12 11:27:11 rburton, : Maybe I have to configure my local.conf to make a live image May 12 11:27:13 LetoThe2nd : keep cool :D May 12 11:29:16 ChrysD: i am totally cool. weekend is coming up, and it is not my "product" May 12 11:29:59 hamdyaea: if you're building a x86 image then you generally get one out of the box, so see if you have a .hddimg May 12 11:31:06 LetoThe2nd : Somebody cool doesn't sighs ahahah. Yeah right. May 12 11:31:07 rburton, : I have an .hddimg this is what I use. But the system start and that's it. It don't ask if I want to install etc May 12 11:31:45 Does devtool is the best way to change recipes ? I have a recipe that i would change and generate a patch in my workspace for example. May 12 11:31:57 rburton: hddimg caps out at 4gb due to fat trickery, and he prefers to stick to jethro and not forward for wic. (i've been trying to help all morning, and obviously am a bit frustrated for the effort spent for nothing now) May 12 11:32:42 @ChrysD you cannot just do a .bbappend on the recipe ? May 12 11:32:42 probably ubuntu+remastersys would've been a better option, or debian+preseeding. May 12 11:33:05 pinkSnake : Have done a .bbappend with the FILESEXTRAPATH and SRC_URI of the patch May 12 11:33:09 LetoThe2nd, : I can't move from jethro because I need absolutly python-gtk. May 12 11:33:23 pinkSnake : But still have error because of stripp off etc May 12 11:33:37 hamdyaea: and i told you to forward port it. anyways. i've made my point. May 12 11:34:20 what LetoThe2nd said May 12 11:34:46 LetoThe2nd, : I tryed to forward it to poky and master but it don't work. I think there are reasons why they didn't put the recipe after the jethro branch May 12 11:36:28 09:51 < LetoThe2nd> maka_: "doesn't work really" is the second most useless error description. the most useless one is "doesn't work" May 12 11:36:37 that applies here too, of course. May 12 11:37:27 hamdyaea: we took it out of jethro because its old software and nothing needed it May 12 11:39:04 rburton, : Our python software still need it.. But my first problem is I want to expand the system to use all my sf card and until now I can't move the partition. May 12 11:39:18 rburton, : This is why I try other ways to install it May 12 11:39:59 hamdyaea : so instead of changing the python software, you want to change yocto ? May 12 11:40:12 hamdyaea : maybe if you consider changing your python software, it would be quicker May 12 11:40:22 hamdyaea : But it depends of the python software I know... May 12 11:40:59 or just doing proper packaging into a layer of your own, that includes all the forward ported stuff you need. i don't see the point in all those workarounds upon workarounds. May 12 11:41:23 but again. weekend is coming, not my product. beer o'clock is near! May 12 11:42:09 hamdyaea: i'd say there's a pretty high number of people in this room that would package pygtk2 for the latest release for a good rate. or come back with actual error messages and the recipe. May 12 11:42:41 ChrysD, : It's a huge python software.. the same size as yocto so it's hard and complicated to make it change from pygtk to gtk3. May 12 11:43:05 rburton, : OK I will try it again.. May 12 11:44:34 hamdyaea : Ok i understand May 12 11:52:17 Is there a way to get BitBake to dump all the referenced repositories for a particular target (I am using target to mean, for example "core-image-sato") ?? May 12 11:52:55 Smitty_: repositories, in the sense of? May 12 11:54:10 So, I guess this is subtly complicated. I guess what I want to know is any "fetching" being done May 12 11:55:19 Smitty_: im sorry, but i don't understand the question still. May 12 11:55:36 I realise that theoretically there's no way to know, since a recipe could invoke a binary which fetches something, but, assume the standard references to git/subversion/whatever May 12 11:56:08 Smitty_: not sure of an easy way to say "will this target run any do_fetch tasks" May 12 11:56:26 what do you actually want to do? May 12 11:59:58 I've inherited a project in which there are several targets. Let's say they're supposed to be roughly identical. Let's call them target-release and target-dev. I'm trying to get a picture of how they differ. May 12 12:01:04 bitbake -e each of them to a file and use something like meld to see? May 12 12:01:10 I have discovered that target-dev accesses at least one git repository that is not accessed by target-release. Before I continue, I want to know all the differences, then kill whoever is repsonsible for such silliness. May 12 12:02:01 In this case, I have redefined "kill" to mean publicly humiliate May 12 12:10:28 i actually hope that my dev image pulls in stuff that is not in the release... May 12 12:18:19 Why would you want that ? I want my dev build to look exactly like my release build except for possibly for compiler optimizations May 12 12:19:28 I must be missing something really fundamental about this whole process - I seem to be getting stuck on issues which I would never have imagined were issues. May 12 12:20:41 Smitty_: you're free to wish for whatever you want in your dev image. i personally want valgrind, strace, gdb, stuff like that to be included then. which i certainly do not want in a production image. May 12 12:22:29 Hmmm.. I see... May 12 12:23:05 Smitty_: so maybe before "publicly humiliating" other people, ask them first, there might have been reasons for their doings. May 12 12:23:39 Can I ask why you care about those type of utilities being present, other than consuming a little storage, possibly ? May 12 12:23:57 i mean, i have two coworkers on the team. we cannot even agree on *two* dev images, let alone one. ;-) May 12 12:24:10 rburton, : I did it on the master branch. I installed the meta-debian to install pygtk. now I have many mistakes : https://pastebin.com/3HkusnWX May 12 12:24:11 Smitty_: do i need another reason than storage? May 12 12:24:42 rburton, : i changed the meta-debian from jethro to master May 12 12:25:26 No, just wondering if there's other reasons - OK, maybe security too, I suppose. I mean, if you ship gdb, strace, etc, I suppose this opens attack vectors May 12 12:25:57 Smitty_: actually it is absolutely no security concern in my case. May 12 12:25:57 OK, it's all a learning process - I've never had to worry about such things before May 12 12:26:19 its jsut shipping a 20MB update fie versus a 40MB or %=MB one., May 12 12:26:23 *50MB May 12 12:27:08 ok, one (partial) security concern: dev image has ssh. May 12 12:28:53 OK - I think I've grok'd the why they might differ thing. Now, I need to know how they differ. May 12 12:29:24 Smitty_: build both and compare the mainfests. thats the most obvious thing. May 12 12:29:42 Manfest...OK, new keyword May 12 12:29:54 s/Manfest/Manifest May 12 12:30:13 I guess a Manfest is what my ex-wife was into May 12 12:30:31 Smitty_: yellow-red card for you. May 12 12:30:58 A badge of honor ? May 12 12:32:05 not exactly. but anyways, next to your image files there should be the manifest files. those tell you want went into an image. May 12 12:33:11 plus, in tmp/deploy/licenses/$YOURIMAGENAME-$TIMESTAMP/ are more extensive license informations May 12 12:35:23 LetoThe2nd, : can you look at what I did please ? I changed the meta-debian from jethro to master. And now the bitbake don't work. Is it normal ? May 12 12:36:16 hamdyaea: if you switch only one layer and the others stay at a different branch, the build will break. did you do that? in that case, no need to even look. May 12 12:37:50 LetoThe2nd, : everything is the same branch : master May 12 12:38:25 hamdyaea: master is not a coherent branch. latest one is morty. May 12 12:38:41 LetoThe2nd, : Ok I will do it on morty May 12 12:43:19 hamdyaea: if you use meta-debian you basically don't get support from here May 12 12:44:55 take the pygtk2 recipe from before it was removed and see how it fails against master May 12 12:46:48 I have the same error with all in morty https://pastebin.com/ZNFgAgYp May 12 12:49:41 * LetoThe2nd sighs some more. May 12 12:53:18 (besides the fact that meta-debian does not have a morty, branch, so your statement is clearly incorrect) May 12 12:55:04 LetoThe2nd, : I'm trying to import somthing from Jetro to a newer branch. In meta-debian i just did : git branch morty then git checkout morty May 12 12:56:09 hamdyaea: so you created a branch and called it morty. which is not at all the same as getting the morty branch from upstream. May 12 12:57:59 LetoThe2nd : I'm a bit jealous. You seems more patient with hamdyaea than me ahah. May 12 12:58:03 LetoThe2nd, : So how can I import a layer from an older branch like this ? May 12 12:58:18 LetoThe2nd, : thanks for your patience :P May 12 12:59:17 ChrysD: i actually think that both of your approaches are about equally stupid. while you seem to make progress, in fact. May 12 12:59:41 LetoThe2nd : I don't have an approach, that's the point. May 12 12:59:49 LetoThe2nd : But still learning. May 12 12:59:56 hamdyaea: just don't do it. create your own layer. and stuff the relevant recipes in there. just like i told you some times already. May 12 13:00:39 ChrysD: i noticed. and i am pleasantly surprised despite still not wanting to encourage you too much. May 12 13:01:57 LetoThe2nd : Don't be rude withs newbie. yocto is powerfull and the mecanism are quite hard for somebody that never work there. Especially me with the fact that i'm also a newbie in linux. The things come time by time. May 12 13:02:18 LetoThe2nd : especially the best practices. May 12 13:02:50 ChrysD: i know. but when i hear things like "i want this workaround upon this workaround and my product is almost finished, i get the red lights." May 12 13:03:34 do you want to see the marks where bit my desk not to ask what product it is, so that i can aviod it? May 12 13:04:23 LetoThe2nd : I know, even me i complain about this. But get my position... I can't decide " sadly" to everything as you you can't help everybody also. I need to understand more the workflow to fit more. But also you know that I need to follow the workflow of the company who provided the sources. May 12 13:05:06 LetoThe2nd : So it's complicated to be at the point where you have to choise of redoing everything by yourself as a noob I am or continuing in the workflow of the company which have provided most of the sources. May 12 13:05:43 sorry, but "i know that its wrong but i don't have the time to fix it, so please #yocto help me to ship this crap" is just wrong. from *EVERY* point of view. May 12 13:05:53 LetoThe2nd : But I know that you will say that in that case i should ask for support to the company. Which I'm doing. But mostly when I come here, is to get the yocto mecanism and understanding how it works. May 12 13:06:15 LetoThe2nd : more than doing the stuff for me. May 12 13:07:08 LetoThe2nd : The difference is that i don't have to supply any result. When I come here, isn't for shipping anything, but more for educational purpose. May 12 13:07:12 ChrysD: hint: as a first thing, you can try to get your nomenclature right. you are mostly talking about OE technology, with some poky specifics mixed in here and then. not "yocto" :-) May 12 13:07:43 ChrysD: i noticed, i realized, and thats why i said i am pleasantly suprised. May 12 13:08:20 LetoThe2nd : And I'm also trying to help, because I guess that when you try to help and understand problems, you increase also the level of understanding. May 12 13:09:12 LetoThe2nd : That's why i'm not connected here only when I need help. May 12 13:09:43 :-) May 12 13:10:36 LetoThe2nd : And for exemple, it don't distinguish well between OE techno / Poky / Yocto for exemple. But I guess the first things is to know how OE Techno works because its the basis to then "masterize" in yocto. May 12 13:10:55 LetoThe2nd : I don't distinguish * May 12 13:11:34 LetoThe2nd : But still learning. May 12 13:14:07 ChrysD: actually you should, because yocto just is no software thing, no matter how often people repeat it. yocto is basically a brand name, under which some businesses coordinate their efforts. getting confused between poky/OE/bitbake/eventually toaster is fine, as its correlated software. but always naming it "yocto" is just wrong. imagine you would keep on saying "i take bayer" - when you actually mean "aspirin", just because its ... May 12 13:14:13 ... their best known product, and you assume that everybody else also just thinks about that brand. May 12 13:15:05 LetoThe2nd : So yocto is " jsut " a refresh of OE + Poky ? May 12 13:15:22 ChrysD: no that exactly is what it is *NOT* May 12 13:15:35 LetoThe2nd : ahah i'm confused May 12 13:16:30 LetoThe2nd : So yocto is just the name to say that a group of people have refreshed OE + POKy ? May 12 13:17:32 ChrysD: "yocto" is like a big pot into which a lot of engineering power and money is poured. these resources are then spent on several things that the yocto project wants to create. one of these things is poky. another one is an eclipse plugin. yet another one is documentation. and so on, and so on. May 12 13:17:33 ChrysD: oe-core is, well, oe-core. poky is a reference distro using oe-core as an example. May 12 13:17:59 rburton: don't know why but i feel like ... i should wear plaid. May 12 13:18:04 yocto is an umbrella organisation that organises and funds and stuff May 12 13:18:37 (umbrella *NOT* in the rihanna meaning!) May 12 13:19:31 rburton: wasn't the shortdesc that poky = oe-core + bitbake + special sauce? May 12 13:19:43 LetoThe2nd : So the rectification have done is better than what i said before ? May 12 13:20:16 LetoThe2nd: pretty much. special sauce is some BSPs not really designed for production use, and a change to the splash screen. :) May 12 13:20:32 rburton: splash screens are awesome. May 12 13:22:42 So Yocto project is a mutualisation of humans ressources to reproduct a friendly environment to helpl doing distro for embedded systems using OE-Core + poky with is based of the OE-Core and bitbake + some tools + swabber + toaster etc etc May 12 13:23:07 using OE-Core + if necessary a reference distro as poky * May 12 13:23:42 ChrysD: that sounds mostly right, yes. thats basically why anybody saying "this runs yocto linux" can only be wrong. May 12 13:23:45 poky is oe-core + bitbake + meta-poky, bundled up May 12 13:24:10 poky is entirely optional and just a fairly minimal example May 12 13:24:39 rburton : That's why i've rectify by seing " if necessary areference distro " May 12 13:24:43 yes, the really useful part is actually the oe-core <-> bibake correlation that comes with it. May 12 13:25:15 yeah, it ensures you use the right version, and if tracking master of oe-core then you know you'll get any required bitbake changes. May 12 13:25:35 rburton : But you make me confused when you say that poky is also bitbake. Because poky is for me a reference distro and bitbake a tool. And i don't really the correlation. Maybe because poky is more than a distro ? Poky it's a reference distro + tools to help doing distro ? May 12 13:25:56 bitbake is the build tool itself. it needs metadata May 12 13:26:02 oe-core is metadata May 12 13:26:14 poky is bitbake + oe-core + some other tiny layers, all bundled together May 12 13:26:35 rburton : maybe i'm confused between the " poky folder " and "poky distro " May 12 13:26:54 rburton : the same name used for two different things or I missing something ? May 12 13:27:59 I hereby declare beer o'clock. May 12 13:28:08 * LetoThe2nd vanishes in a weekendly puff of smoke May 12 13:28:21 man LetoThe2nd is in the best time zone May 12 13:28:31 rburton : But i think i'm understanding. Poky is the total set of tools for building + a reference distro which is named also poky right ? May 12 13:28:49 ChrysD: i guess so May 12 13:29:07 rburton : Yeah the best time zone :( and I hope a better weather than here. May 12 13:31:13 hey alll May 12 13:32:01 when there are multiple versions of a recipe (stable vs dev) is there an easy way to tell bitbake to compile both, so images can select the correct version later ? May 12 13:32:32 no May 12 13:32:34 or is that hardwired deeply in yocto ? May 12 13:32:36 darn May 12 13:32:37 yes May 12 13:33:02 so having a stable vs testing à la debian with yocto is not possible ? or at least not trivial May 12 13:33:16 boucman_work: you can do it exactly the same way debian does: with different distros May 12 13:33:17 ok, thx i'll look for a workaround May 12 13:33:45 yeah... i'll think about that, that might be the way to go... May 12 13:34:12 you could make the dev version parallel installable with the stable version May 12 13:34:23 then you can build both as they can have different names May 12 13:34:45 I understand only know that .patch is for patch only sources from a recipe, and not to change the recipe himself T_T May 12 13:35:04 thanks to pinkSnake, which i could have spend more time to try to patch the recipe itself for other week May 12 13:45:19 hey, i'm fairly new to this project. is there an example combinding layers and applications? i'm still reading into the docs and i can imagine their use but it's a bit vague for me May 12 13:46:35 cryptix : I guess it's better if you define more what you want to do. May 12 13:47:19 i'm trying to recreate libreelec with yocot, as an exercise. so i'm using the rpi bsp layer and would add swupdate and some kodi layer to install it but i don't yet see how or where these layers are bundled together to make the final image May 12 13:51:58 cryptix : so you have your bsp layer, but you would like to find which layer provides kodi ? May 12 13:52:03 maybe i'm missing something... i just don't see how adding layers to bblayers makes decisions about what is put into the image May 12 13:52:15 cryptix : ahhh ok i understand May 12 13:52:42 cryptix : For me, when you add a layer, is like having a toolbox. It's not because you have the toolbox that you will use all the tool for the work you will do. May 12 13:52:53 cryptix : you have to specify the packages you want to install in the recipe of the image May 12 13:53:00 cryptix : With IMAGE_INSTALL May 12 13:53:14 cryptix : or for testing in conf/local.conf with IMAGE_INSTALL_append May 12 13:53:43 cryptix : and the layer are just here to provides a set of recipes when you need to use it depending of what the recipe image requires May 12 13:53:56 cryptix : The layer is like the recipebook May 12 13:58:16 cryptix : But sometimes you can be surprised that some packages are in your image but not in the image recipe. For exemple ifi in a recipe you have RDEPENDS_${PN}= " + a list of packages", it means that the package you will produce from the recipe would need other packages to the run time, so it will install it. May 12 13:58:48 cryptix : and sometimes packages are below packagesgroup. So you can find some kind of IMAGE_INSTALL = packagegroup-nananan and in the "packagegroup-nananan" you have lot of other packages May 12 13:59:43 yeah adding a layer just makes it available to build, it won't change the images May 12 14:00:08 rburton : How to ruin a full monolog in only one sentence, omg May 12 14:00:22 rburton : I should be more synthetic ahahah May 12 14:01:08 May 12 14:01:11 thank you. i'm starting to see how the layers and recipies fall together.. bit jigsaw-ish if you ask me but i guess it's much more flexible this way :) May 12 14:01:25 cryptix: that's exactly the point May 12 14:01:49 there's a meta-perl layer with a gazzilion perl recipes in. you wouldn't want them all to be built if you added it just for one perl recipe. May 12 14:02:43 layers can and do provide samples images though, ie meta-xfce has a xfce sample image. May 12 14:02:49 i assumed some kind of final config where you say "give me kernel 4.4 with these pkgs" but i just needed to ad the rpi layer and set machine to pi2 to get a base system May 12 14:02:59 stop worrying and love yocto, i guess ;) May 12 14:03:46 cryptix : how can you define the file which you have set the machine to pi2 ? isn't a kind of final config ? ahah May 12 14:03:48 yea i found the rpi image recipe and working my back from there now until i get it May 12 14:04:11 ChrysD: yea but it was so empty for what it did :) May 12 14:05:32 cryptix : As I said, there is lot of mecanism.... If you tell to yocto that you want to use the package tennis-racket IMAGE_INSTALL = " tennis-racket " and the recipe to tennis-racket tell you that RDEPENDS_${PN}="tennis-balls, tennis-court", it will brings you the tennis-balls and tennis court for example. May 12 14:07:35 cryptix : but in the image recipe you just have "tennis-racket" May 12 14:08:23 yea, i'm starting to see the dependency resolution. i'll try to whip up my own image recipe next May 12 14:08:33 thanks again! May 12 14:09:06 cryptix : you have also other variables as EXTRA_IMAGE_FEATURES in build/conf/locale.conf... and if you put debug-tweaks it will brings ssh and root May 12 14:09:40 cryptix : So good luck ! May 12 14:14:24 cryptix : I forgot, you have image recipe, but you have also distro conf, machine conf. May 12 14:15:17 cryptix : the layer that supply the distro, you will have in the folder conf, another folder that is "distro" and you will have a "distroname.conf" file. Which you set what is the init manager, the loging manager etc ... May 12 14:16:57 cryptix : in the layre that provide the bsp for RPI, you can have also in the folder /conf/machine some files with ".conf" with the name of your machine which you specify for example what is the device tree used, some machines features such as wifi etc May 12 14:17:53 cryptix : but i don't know if the meta for rpi is done that way.... May 12 14:18:36 Time to go, bye all. May 12 14:19:02 it is, thanks a lot ChrysD May 12 15:04:04 hello guys, how to properly disable weston but leave wayland package in yocto? May 12 15:05:21 Erm, so I moved my entire Yocto build environment from /yocto/ to /thismount/yocto/. I have changed the ./build/saved_tmpdir to reflect the change, but some internal build tools get upset that some files exist. May 12 15:05:27 Any questions or suggestions appreciated. May 12 15:05:50 ./build/tmp/saved_tmpdir* May 12 15:09:27 @majuk welcom on Yocto cache... i you find a solution feel free to share it ^^ May 12 15:11:27 majuk: rm tmp and re-bitbake May 12 15:11:37 it will just pull everything from your sstate-cache May 12 15:11:48 Ox4: remove weston from your image May 12 15:12:23 Thanks. May 12 15:16:12 rburton: via IMAGE_FEATURES_remove? May 12 15:17:17 Ox4: well step 1 is working out why your image has weston in the first place May 12 15:30:20 rburton: actually I cannot explain because I have additional layers May 12 15:31:13 bitbake image -g -u depexp? May 12 15:34:20 rburton: http://ix.io/tvW May 12 15:37:21 Ox4: it needs python-gi and gtk3 May 12 15:37:48 rburton: ok, hold on for a while May 12 15:38:35 rburton: ah, I cannot do that, because it is launched in systemd container :-( May 12 15:38:38 lol May 12 15:38:45 just -g then, and read the dot file May 12 15:39:46 rburton: there are several file generated May 12 15:40:12 pn-buildlist, pn-depends.dot, package-depends.dot and task-depends.dot May 12 15:40:21 random thought: split out depexp into its own command and let it accept previous -g output instead of generating it May 12 15:40:59 kergoth: not a horrible idea May 12 15:41:19 kergoth: did i tell you i'd written a pkgdata browser? May 12 15:41:26 nope, sounds interesting May 12 15:41:28 not finished but sort of works May 12 15:41:36 poky-contrib:ross/pkgdata May 12 15:41:52 moderately helpful for finding stuff out about things you've built May 12 15:43:45 rburton: it seems I found the bb file May 12 15:44:20 rburton: http://ix.io/tvY May 12 15:44:47 there you go, don't pull that into your image :) May 12 15:49:49 rburton: but I think I need ti-sgx-ddk-km and ti-sgx-ddk-um packages May 12 15:54:30 Ox4: so install them May 12 15:54:46 the packagegroup is just a convenience. if you don't want bits of it, install the bits you do want. May 12 15:55:20 understood, thanks May 12 17:24:13 even though I have a kernel recipe in RM_WORK_EXCLUDE and indeed its skipping rm_work for it, the build directory where the kernel is actually built gets removed - why? May 12 18:45:52 Is there anything already in yocto or a layer to handle changing the "name" field in a legacy uImage (and writing a new uImage with the new name)? May 12 18:47:08 And if not: what's the best way to call into python in/near a IMAGE_CMD? (I want to modify a uImage for the image generation). May 12 19:34:05 jmesmon: BUILD_OS¶ May 12 19:34:06 Specifies the operating system in use on the build host (e.g. "linux"). The OpenEmbedded build system sets the value of BUILD_OS from the OS reported by the uname command - the May 12 19:34:06 first word, converted to lower-case characters. May 12 19:36:20 jmesmon: auch, that is not what you want, I believe May 12 20:34:37 anyone have an idea why a couple of my kernel modules would complain about missing symbols but others with plenty of symbols are fine? bluetooth: no symbol version for sock_register May 12 21:16:06 so who broke create-pull-request? I just got 'fatal: insane in-reply-to:' when i didn't specify the argument to set an in-reply-to.. May 12 21:16:44 looks like the logic is completely backwards. did they even test this? May 12 21:16:53 it passes —in-reply-to= when IN_REPLY_TO is *not* set May 12 21:16:58 and doesn't pass it when it is May 12 21:22:36 ah, they sent a follow up patch, but presumably after it was merged May 13 00:22:08 lsandov: ya, that is not what I want. the legacy uImage file format has a 32 byte "name" field. I'm trying to set it to something that includes a build number, but avoid rebuilding the kernel and all recipies that have depends on the kernel on every build. May 13 00:23:03 I had some python code written to do it, so I was hoping to load it as a module in bitbake, but it was easier just to make a package containing the single uimage-edit.py and run it as a command. **** ENDING LOGGING AT Sat May 13 03:00:01 2017