**** BEGIN LOGGING AT Thu Jun 18 02:59:59 2015
Jun 18 06:50:36 <joshuagl> RP: around? I'd like to run an AB build whilst all the slaves are idle
Jun 18 07:27:54 <mckoan> good morning
Jun 18 07:35:24 <sm0ketst> morning all
Jun 18 07:38:38 <sm0ketst> i'm using 1.7.2, genericx86 and core-image-minimal for one Celeron M unit. It stops at "Waiting for removable media..". I've checked the "action=add" in init-live.sh and seems ok. Any help? thanks
Jun 18 08:15:51 <lpapp_> good morning
Jun 18 08:59:42 <RagBal> denix, can you help me getting gles-omap3 5.01.01.02 to work in my fido build with Qt5? I have no idea what I'm doing wrong here as it keeps failing on error: Can't install libgles-omap3-es5-5.01.01.02-r38.1@cortexa8hf_vfp_neon: no package provides libews.so
Jun 18 08:59:57 <RagBal> denix, I also tried to use oe-core but didn't succeed either
Jun 18 09:07:36 <RagBal> I'm stuck with error: Can't install libgles-omap3-es5-5.01.01.02-r38.1@cortexa8hf_vfp_neon: no package provides ld-linux.so.3
Jun 18 09:10:19 <parrot> so suppose I want to replace linux-yocto recipe with something call linux-spam, what do I need to add to ensure that poky takes linux-spam instead of default linux-yocto?
Jun 18 09:10:48 <lpapp> set it as preferred?
Jun 18 09:11:26 <parrot> lpapp: how do I do that?
Jun 18 09:11:28 <lpapp> PREFERRED_PROVIDER_virtual/kernel ?= "linux-spam"
Jun 18 09:12:21 <lpapp> you can also leave the question mark out depending on your case.
Jun 18 09:12:55 <parrot> that difference the question mark makes
Jun 18 09:12:57 <parrot> ?
Jun 18 09:13:15 <lpapp> read the bitbake manual
Jun 18 09:13:20 <lpapp> it is not really the main thing for you.
Jun 18 09:13:58 <lpapp> but in any case: http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#setting-a-default-value
Jun 18 09:14:36 <lpapp> I assume that both will work in your case.
Jun 18 09:15:36 <parrot> lpapp: I guess it should since i have not made a similar assignment before. Thanks :-)
Jun 18 09:16:02 <lpapp> also, see http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PREFERRED_PROVIDER
Jun 18 09:44:13 <miandonmenmian> where can i find the yocto page for hob ?
Jun 18 09:44:47 <miandonmenmian> https://www.yoctoproject.org/projects/hob  this link seems broken
Jun 18 09:54:07 <silviof> miandonmenmian: https://www.yoctoproject.org/tools-resources/projects/hob
Jun 18 09:56:54 <miandonmenmian> thanks silviof
Jun 18 09:57:28 <lpapp> what happened to bluel... :O
Jun 18 09:59:50 <RagBal> denix, no way... when using PACKAGE_CLASSES = "package_ipk" the build works
Jun 18 10:19:06 <mckoan> hello, the history command doesn't work when switch off and switch on the board, do I need ant special setting?
Jun 18 10:28:05 <LetoThe2nd> mckoan: um, like an rw filesystem? ;)
Jun 18 10:34:37 <bluelightning> morning all
Jun 18 10:47:45 <lpapp> hi bluelightning
Jun 18 10:48:01 <bluelightning> hi lpapp
Jun 18 10:48:53 <lpapp> bluelightning: shall I create a separate recipe for the SDK with the previously discussed variable not to have an impact on the image creation, too?
Jun 18 10:49:20 <bluelightning> sure
Jun 18 10:49:47 <bluelightning> it's only going to affect an image that uses dev-pkgs/dbg-pkgs/doc-pkgs etc. in IMAGE_FEATURES though
Jun 18 10:50:58 <lpapp> so not e.g. image-core-minimal?
Jun 18 10:59:41 <bluelightning> lpapp: no, not unless you added those by way of your config / EXTRA_IMAGE_FEATURES
Jun 18 11:21:38 <miandonmenmian> howdy bluelightning
Jun 18 11:29:22 <bluelightning> hi miandonmenmian
Jun 18 11:31:23 <lpapp> bluelightning: so does that mean if I exclude, let us say, busybox, it remains in the image?
Jun 18 11:32:31 <bluelightning> lpapp: yes - this variable excludes the complementary packages to the list of packages you specify, not the actual package itself - but in terms of the SDK that may mean there's nothing to pull that package into the SDK and therefore it doesn't go in
Jun 18 11:51:43 <lpapp> bluelightning: we only have EXTRA_IMAGE_FEATURES = "debug-tweaks"
Jun 18 12:39:38 <mckoan> LetoThe2nd: it is a rw fs
Jun 18 12:49:29 <_4urele_> mckoan, I would say that you have to look in your busybox configuration, but i'm not sure at 100%
Jun 18 12:52:18 <_4urele_> mckoan, on my target I have a .bash_history
Jun 18 12:52:42 <_4urele_> mckoan, if you want I can share my busybox .config
Jun 18 13:17:15 <lpapp> bluelightning: it seems that I could not log in without EXTRA_IMAGE_FEATURES = "debug-tweaks" as root.
Jun 18 13:17:18 <lpapp> why is that?
Jun 18 13:17:22 <lpapp> We do have a root passwd.
Jun 18 13:18:08 <bluelightning> I don't know off hand - have you verified that your root password is actually getting set in /etc/passwd in the image?
Jun 18 13:19:21 <lpapp> sure
Jun 18 13:21:04 <bluelightning> I ask because if it was set there correctly, it would work...
Jun 18 13:23:25 <lpapp> yeah, that is my assumption, too.
Jun 18 13:24:42 <bluelightning> ah, one thing
Jun 18 13:25:03 <bluelightning> if you are using ssh then I believe we are tweaking the configuration of that to allow root logins as part of that feature
Jun 18 13:32:51 <lpapp> ssh, sure.
Jun 18 13:32:54 <lpapp> sorry, forgot to mention that.
Jun 18 13:40:35 <lpapp> bluelightning: will that have any impact on the SDK generation?
Jun 18 13:40:47 <bluelightning> no - why would it?
Jun 18 13:41:26 <lpapp> I would not know. It also contains the debug word :)
Jun 18 13:41:28 <lpapp> like -dbg :)
Jun 18 14:08:44 <lpapp> bluelightning: where shall I put this, into the distro/image or somewhere else?
Jun 18 14:09:00 <bluelightning> where should you put what, sorry?
Jun 18 14:22:14 <lpapp> bluelightning: the variable with its values.
Jun 18 14:22:32 <bluelightning> lpapp: the image recipe
Jun 18 14:51:00 <lpapp> bluelightning: thanks, guess there is no way to exclude files as opposed to packages?
Jun 18 14:53:01 <bluelightning> lpapp: there isn't, no
Jun 18 14:54:45 <mie_> Hi i would like to use my own autoconf l
Jun 18 14:55:34 <mie_> bin. Can i just replace autoconf-native bin ?
Jun 18 15:03:02 <bluelightning> mie_: you probably could but that sounds like a strange thing to want to do...
Jun 18 15:21:43 <lpapp> bluelightning: hmm, if it is a regex, how does one specify a list of packages?
Jun 18 15:21:46 <lpapp> busybox, foo, etc?
Jun 18 15:22:48 <bluelightning> lpapp: |
Jun 18 15:23:36 <lpapp> thanks
Jun 18 15:27:11 <jc__> if i add "EXTRA_IMAGE_FEATURES = "package-management"" that will allow the embedded client to download/install packages, right?
Jun 18 15:28:16 <bluelightning> jc__: provided you set up the package manager to point to some feeds, yes
Jun 18 15:29:05 <jc__> my client will not have the ability to get packages, not sure how i add a package to it before i bitbake it.
Jun 18 15:29:40 <jc__> i can create a recipy to build a program from source but how does it get into the file system where it belongs
Jun 18 15:30:00 <jc__> ie. populate /usr/bin
Jun 18 15:30:50 <bluelightning> jc__: I'm not sure if I'm understanding correctly but if you create a recipe you should get a package produced at the end
Jun 18 15:30:53 <jc__> .. or a prebuild rpm package
Jun 18 15:31:03 <jc__> a rpm package right?
Jun 18 15:31:53 <jc__> btw: I am still using qemuarm to figure this out
Jun 18 15:33:04 <bluelightning> if you're using RPM packaging (the default in the local.conf that poky gives you) then yes
Jun 18 15:34:27 <jc__> how does the rpm then get installed? After the client is booted and from there? or can it be installed into the root filesystem before the zImage is created?
Jun 18 15:34:56 <jc__> zImage contains the kernel and the filesystem (?)
Jun 18 15:43:35 <WarheadsSE> anyone can give me insight as to why the comparison fails, but the values are in the parse ?
Jun 18 15:43:36 <WarheadsSE> http://pastie.org/10247199
Jun 18 15:48:14 <mckoan> _4urele_: thx, it's very weird because with Yocto 'daisy' it worked
Jun 18 16:00:16 <bluelightning> jc__: if you mean can rpm files produced somewhere other than the build system be installed into the image, that's tricky - you may be better using a recipe to repackage them
Jun 18 16:00:43 <bluelightning> jc__: the zImage file is a compressed kernel
Jun 18 16:08:58 <fishey1> So I'm using PREFERED_PROVIDER_foo = "4.%", and I've noticed that it ends up matching the _lowest_ version number that starts with "4." instead of the _highest_ (which is what I'd expect)
Jun 18 16:09:06 <fishey1> Is matching the lowest number expected behavior?
Jun 18 16:09:39 <fishey1> (specific packages is mono in meta-mono git://git.yoctoproject.org/meta-mono)
Jun 18 16:10:08 <bluelightning> fishey1: do you mean PREFERRED_VERSION?
Jun 18 16:10:23 <fishey1> bluelightning: I do, mistyped here
Jun 18 16:11:17 <fishey1> (but, thankfully, not in by distro.conf file)
Jun 18 16:13:17 <bluelightning> I suspect it's picking up the first recipe that matches the preferred version string without considering the actual number
Jun 18 16:13:23 <bluelightning> which may well be a bug
Jun 18 16:32:32 <WarheadsSE> Any feedback on this http://pastie.org/10247199 coming back and throwing the for all recipes that include it ?
Jun 18 16:32:51 <WarheadsSE> http://pastie.org/10247289
Jun 18 16:39:00 <lpapp> bluelightning: PACKAGE_EXCLUDE_COMPLEMENTARY = "foo|bar|baz" ?
Jun 18 16:40:48 <bluelightning> lpapp: it's a standard regex match on the name
Jun 18 16:41:10 <lpapp> bluelightning: so there is no need for leading space like for some other variables, etc?
Jun 18 16:41:22 <bluelightning> er, no
Jun 18 16:41:44 <bluelightning> leading space is when you _append to a variable containing a space-separated list...
Jun 18 16:42:48 <lpapp> ok, thanks.
Jun 18 16:43:17 <bluelightning> have you actually tried this yet?
Jun 18 16:46:02 <jc__> bluelightning: thank you, adding to my notes about repackaging an existing rpm package.
Jun 18 16:54:57 <bluelightning> jc__: FYI we do have a class to make that a bit easier - http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-classes-bin-package  http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/bin_package.bbclass
Jun 18 17:09:36 <lpapp> bluelightning: I am just trying it now.
Jun 18 17:14:30 <WarheadsSE> self-answer to my previous question, apparently @ time of inherit'ing, there is no populated value from the machine.conf. Thus d.getVar("PREFERRED_VERSION_${PN}") is None
Jun 18 17:56:44 <lpapp> bluelightning: how can I check what is in the SDK without installing it? Is it available somewhere in the build directory?
Jun 18 18:02:31 <dasabhi> hello i know yocto is used to build your own custom linux image
Jun 18 18:02:47 <dasabhi> does that mean i can also use it to build a custom linux kernel image?
Jun 18 18:03:09 <lpapp> files-in-sdk.txt maybe?
Jun 18 18:03:31 <lpapp> dasabhi: what is the difference?
Jun 18 18:07:33 <dasabhi> lpapp: um....i thought it meant building specific distros like arch or gentoo
Jun 18 18:07:54 <lpapp> heh, no
Jun 18 18:08:07 <dasabhi> lpapp: so it just building the kernel image itself
Jun 18 18:08:11 <lpapp> those have far more packages than available recipes
Jun 18 18:08:16 <lpapp> but in theory, you could.
Jun 18 18:08:25 <dasabhi> lpapp: this makes my life sooo much easier lmao
Jun 18 18:08:36 <dasabhi> lpapp: thank you so much :)
Jun 18 18:08:39 <lpapp> well, a linux image does contain a kernel
Jun 18 18:08:49 <lpapp> so yes, it can generate uimage, zimage, etc.
Jun 18 18:09:55 <lpapp> and you can use your custom kernel
Jun 18 18:10:02 <lpapp> or just the custom patches on top of the available kernels, etc.
Jun 18 18:10:20 <lpapp> but if you are only interested in the kernel, why cannot you build that outside of the Yocto environment?
Jun 18 18:10:40 <lpapp> or you are interested in the whole thing, but you want to make sure that you can customize the kernel as you please?
Jun 18 18:51:28 <lpapp> bluelightning: unfortunately that variable did not work out :(
Jun 18 18:51:40 <lpapp> bluelightning: the executables are still in the installed SDK :(
Jun 18 18:51:49 <lpapp> bluelightning: is there a way for me to easily debug this?
Jun 18 18:54:23 <bluelightning> lpapp: buildhistory dependency graphs would probably be the place to start
Jun 18 19:05:47 <lpapp> bluelightning: "Build history is disabled by default. To enable it, add the following INHERIT statement and set the BUILDHISTORY_COMMIT variable to "1" at the end of your conf/local.conf file found in the "
Jun 18 19:05:52 <lpapp> does it really have to be at the end of the file?
Jun 18 19:06:06 <bluelightning> no, whereever you want in the file is fine
Jun 18 19:06:21 <lpapp> right, also I used BUILDHISTORY_FEATURES = "image"
Jun 18 19:06:31 <lpapp> shall I remove that or add sdk in there, etc?
Jun 18 19:06:55 <bluelightning> sdk would need to be in there
Jun 18 19:07:19 <bluelightning> or comment it out and it'll enable sdk image & package history by default
Jun 18 19:07:43 <bluelightning> bbl
Jun 18 19:08:00 <fishey1> bluelightning: welp, I've sent out a patch that fixes my PREFERRED_VERSION ordering pain. Indeed, the sorting used to select packages wasn't using version when there were certain preferences involved
Jun 18 19:08:02 <lpapp> ok, hmm.
Jun 18 19:08:25 <lpapp> bluelightning: files-in-sdk.txt then?
Jun 18 19:09:46 <lpapp> bluelightning: fwiw, I do not get to have such a file.
Jun 18 19:14:25 <lpapp> bluelightning: I did bitbake -c populate_sdk my image after comment that line out as you wrote.
Jun 18 19:43:12 <lpapp_> bluelightning: sorry, left work
Jun 18 19:43:16 <lpapp_> but still interested in the reply.
Jun 18 21:04:35 <kergoth> hmm, odd
Jun 18 21:05:02 <kergoth> pygtk.pth ended up owned by the host user (running bitbake), and there's a creat replacement warning in pseudo.log
Jun 18 21:05:57 <kergoth> shouldn't the new one be used in preference to the old in a creat(), rather than ignoring the new? hmm
**** ENDING LOGGING AT Fri Jun 19 02:59:59 2015