Thursday, 2013-07-18

*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC00:06
*** myopiate <myopiate!~myopiate@203.206.170.6> has joined #yocto00:11
myopiatehas anybody tried putting everything into /usr before? and linking /[s]bin to /usr/[s]bin etc.  kinda like the way Fedora does things now.00:12
myopiateI know busybox puts stuff in /bin and /sbin.  This could be solved.  glibc is installed in lib when I want it to go in /usr/lib.00:16
myopiatehas anyone tried changing base_prefix to something other than ""?00:17
myopiatedo you think it would break many packages?00:18
*** hollisb <hollisb!~hollisb@c-67-169-221-181.hsd1.or.comcast.net> has quit IRC00:19
*** _julian <_julian!~quassel@x2f10ff1.dyn.telefonica.de> has joined #yocto00:23
-YoctoAutoBuilder- build #213 of build-appliance is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/build-appliance/builds/21300:25
*** _julian_ <_julian_!~quassel@x2f09dc9.dyn.telefonica.de> has quit IRC00:27
*** davest <davest!Adium@nat/intel/x-uwhnzejsnkshiayq> has quit IRC00:29
*** W1N9Zr0 <W1N9Zr0!~W1N9Zr0@24-246-93-30.cable.teksavvy.com> has quit IRC00:30
waltersmyopiate, i have a brutal hack to do it but it operates after the packages00:31
waltersmyopiate, https://github.com/cgwalters/poky/commit/2ecded006b59455e3e55bbdd029ea089a1e1eddf  - if you want the packages to have UsrMove, i suspect it'd be a lot of work00:32
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto00:34
*** nitink1 <nitink1!nitink@nat/intel/x-fpvligariwpibuie> has quit IRC00:36
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto00:41
myopiatewalters, thanks!  I had thought about doing it this way.  it is probably all i need00:44
*** scot__ <scot__!~scot@client-74-113.natinst.com> has quit IRC00:49
*** pidge <pidge!~pidge@134.134.139.74> has quit IRC00:50
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC00:50
-YoctoAutoBuilder- build #51 of minnow-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow-lsb/builds/5101:03
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC01:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto01:05
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto01:17
*** nitink <nitink!~nitink@134.134.139.74> has joined #yocto01:19
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC01:24
*** W1N9Zr0 <W1N9Zr0!~W1N9Zr0@24-246-93-30.cable.teksavvy.com> has joined #yocto01:26
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto01:34
-YoctoAutoBuilder- build #206 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64-lsb/builds/20601:39
-YoctoAutoBuilder- build #25 of buildtools is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/buildtools/builds/2501:53
*** Saur <Saur!pkj@nat/axis/x-wfmqlcfodxumhfiy> has quit IRC02:01
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC02:01
-YoctoAutoBuilder- build #209 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64/builds/20902:03
*** silviof2 <silviof2!~silviof@ppp-93-104-167-171.dynamic.mnet-online.de> has joined #yocto02:04
*** silviof1 <silviof1!~silviof@ppp-188-174-150-82.dynamic.mnet-online.de> has quit IRC02:07
*** davest <davest!Adium@nat/intel/x-xfhbnurmvsdogddn> has joined #yocto02:12
-YoctoAutoBuilder- build #215 of poky-tiny is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/poky-tiny/builds/21502:15
-YoctoAutoBuilder- build #215 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86/builds/21502:15
*** Saur <Saur!pkj@nat/axis/x-rrrqgkgwrukypvid> has joined #yocto02:17
-YoctoAutoBuilder- build #65 of minnow is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/minnow/builds/6502:20
*** doerrpau <doerrpau!~doerrpau@cpe-70-124-65-123.austin.res.rr.com> has quit IRC02:30
-YoctoAutoBuilder- build #215 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-arm-lsb/builds/21502:32
*** davest <davest!Adium@nat/intel/x-xfhbnurmvsdogddn> has quit IRC02:39
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto02:58
-YoctoAutoBuilder- build #222 of nightly-x32 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x32/builds/22203:06
-YoctoAutoBuilder- build #183 of nightly-fsl-ppc is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-ppc/builds/18303:16
-YoctoAutoBuilder- build #212 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-ppc-lsb/builds/21203:19
*** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has quit IRC03:24
*** mitz <mitz!~mitz@KHP222227247006.ppp-bb.dion.ne.jp> has joined #yocto03:26
*** joshc <joshc!~joshc@rhlug/joshc> has quit IRC03:28
-YoctoAutoBuilder- build #210 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-multilib/builds/21003:30
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC03:30
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto03:31
*** doerrpau <doerrpau!~doerrpau@cpe-70-124-65-123.austin.res.rr.com> has joined #yocto03:32
*** joshc <joshc!~joshc@rhlug/joshc> has joined #yocto03:37
*** joshc <joshc!~joshc@rhlug/joshc> has quit IRC03:42
*** klinger <klinger!~klinger@e181128037.adsl.alicedsl.de> has quit IRC03:45
kergoththere we go, added —sysroot= to systemd-tmpfiles and ran it against ${IMAGE_ROOTFS} manually fine, now for integration and working out the kinks, then need a volatiles to tmpfiles.d migration story..03:45
kergoth(using systemd-tmpfiles recipe built for native)03:45
-YoctoAutoBuilder- build #224 of nightly-mips-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-mips-lsb/builds/22403:51
*** klinger <klinger!~klinger@g228060008.adsl.alicedsl.de> has joined #yocto03:58
-YoctoAutoBuilder- build #211 of nightly-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-arm/builds/21103:59
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto04:09
*** doerrpau <doerrpau!~doerrpau@cpe-70-124-65-123.austin.res.rr.com> has quit IRC04:18
*** agust <agust!~agust@p4FC4641B.dip0.t-ipconnect.de> has joined #yocto04:32
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC04:35
*** behanw <behanw!~behanw@216-58-123-51.cpe.distributel.net> has quit IRC04:38
myopiatecan I override a package variable within a distro.conf.  i.e.  I want to change EXTRA_OEMAKE for a specific package in the distro.conf rather than modifying the .bb file.04:40
myopiateShould I be wanting to do this? or am I trying to do things backwards.04:41
*** joshc <joshc!~joshc@rhlug/joshc> has joined #yocto04:41
-YoctoAutoBuilder- build #181 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-ppc-lsb/builds/18104:41
*** seebs <seebs!~seebs@97-92-17-178.dhcp.stcd.mn.charter.com> has quit IRC04:56
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC04:59
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC05:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto05:05
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto05:08
*** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC05:08
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto05:13
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has joined #yocto05:19
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto05:20
-YoctoAutoBuilder- build #184 of nightly-fsl-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/18405:45
*** Saur <Saur!pkj@nat/axis/x-rrrqgkgwrukypvid> has quit IRC05:50
*** cristianiorga <cristianiorga!cristianio@nat/intel/x-lbdvszylplthwike> has quit IRC05:59
*** Saur <Saur!pkj@nat/axis/x-tnmksvpafyubfsmo> has joined #yocto06:04
-YoctoAutoBuilder- build #212 of nightly-mips is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-mips/builds/21206:12
*** Saur <Saur!pkj@nat/axis/x-tnmksvpafyubfsmo> has quit IRC06:18
*** Saur <Saur!pkj@nat/axis/x-ikjghbvybhumwpah> has joined #yocto06:33
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC06:35
*** e8johan <e8johan!~quassel@p5B1526CC.dip0.t-ipconnect.de> has joined #yocto06:38
*** mihai <mihai!~mihai@80.97.15.150> has joined #yocto06:40
*** mihai <mihai!~mihai@80.97.15.150> has quit IRC06:41
*** Umeaboy <Umeaboy!~Umeaboy@213-21-78-12.customer.t3.se> has joined #yocto06:41
*** mihai <mihai!~mihai@80.97.15.150> has joined #yocto06:43
*** Saur <Saur!pkj@nat/axis/x-ikjghbvybhumwpah> has quit IRC06:46
*** bzb <bzb!~bzb@192-0-226-240.cpe.teksavvy.com> has joined #yocto06:52
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto06:53
*** bzb <bzb!~bzb@192-0-226-240.cpe.teksavvy.com> has quit IRC06:54
-YoctoAutoBuilder- build #183 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm-lsb/builds/18306:55
*** Saur <Saur!pkj@nat/axis/x-rchfxidhsxgshcmw> has joined #yocto07:01
*** plfiorini <plfiorini!~plfiorini@93-39-217-199.ip77.fastwebnet.it> has quit IRC07:01
*** Saur <Saur!pkj@nat/axis/x-rchfxidhsxgshcmw> has quit IRC07:08
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto07:13
-YoctoAutoBuilder- build #215 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-lsb/builds/21507:13
*** Saur <Saur!pkj@nat/axis/x-sbkjufhaqtatokwk> has joined #yocto07:23
*** florian <florian!~fuchs@port-217-146-132-69.static.qsc.de> has joined #yocto07:26
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:26
*** Saur <Saur!pkj@nat/axis/x-sbkjufhaqtatokwk> has quit IRC07:29
*** slaine <slaine!~slaine@84.203.137.218> has joined #yocto07:37
*** tbn <tbn!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has joined #yocto07:38
*** tbn is now known as Guest9792907:38
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has joined #yocto07:41
*** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto07:41
*** Saur <Saur!pkj@nat/axis/x-ctrtegclbovaourm> has joined #yocto07:44
*** cristianiorga <cristianiorga!~cristiani@134.134.137.75> has joined #yocto07:45
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:50
*** addu <addu!~addu@sestofw01.enea.se> has joined #yocto07:51
-YoctoAutoBuilder- build #177 of nightly is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8011/builders/nightly/builds/17707:52
bluelightningmorning all07:57
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC08:03
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC08:03
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC08:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto08:05
ndecbluelightning: morning!08:07
ndecso, i got more information from our dev.08:07
ndechis problem is a 'permission denied' issue during rm_work on gcc-runtime.08:07
bluelightninghi ndec08:08
ndechis 'pseudo' environment is very similar to mine. LD_LIBRARY_PATH has both /lib and /lib64.08:08
bluelightningpermission denied? hmm - can you tell what it's trying to delete when it fails?08:09
ndecwe just made an interesting finding. on his 'corporate' linux PC, he is required to install a 'Linux SDK', which in turns is enabling setuid on chmod and chown...08:09
*** RagBal <RagBal!~RagBal@84.105.78.52> has joined #yocto08:10
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto08:10
ndecso i am pretty sure that this is the origin of the problem.08:10
ndecbluelightning: rm: cannot remove `image/usr/include/c++/unordered_set': Permission denied08:10
ndecrm: cannot remove `image/usr/include/c++/cfloat': Permission denied08:10
ndecrm: cannot remove `image/usr/include/c++/cstdbool': Permission denied08:10
bluelightningwhat's stopping it I wonder...08:11
bluelightningdo_rm_work isn't a fakeroot task so pseudo shouldn't be in the way08:11
ndecyeah. i finally don't think it's related to pseudo.08:12
ndecbut the files mentioned above are owned by 'root'. though. that's why i initially thought it was related to pseudo.08:12
*** RagBal <RagBal!~RagBal@84.105.78.52> has quit IRC08:14
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has quit IRC08:15
*** jbaxter <jbaxter!~jbaxter@jimbax.plus.com> has joined #yocto08:18
bluelightningndec: owned by root outside of the pseudo environment? how is that possible?08:20
ndecbluelightning: ok... just got confirmation that the problem was the setuid.08:21
bluelightningndec: suid of what specifically?08:22
ndecas i said above, on his 'corporate' machine, we figured out that chown, chmod and mknod are setuid.08:22
*** zeddii_home <zeddii_home!~zeddii_ho@CPE002369bcfa62-CMbcc810032faf.cpe.net.cable.rogers.com> has quit IRC08:23
ndecso, i guess that OE uses those, and as a consequence some files ended up as 'root'. then in rm_work that explains the perm denied.08:23
ndecbluelightning: after doing the following commands, everything is back to normal:08:24
ndecsudo chmod -s `which mknod`08:24
ndec sudo chmod -s `which chmod`08:24
ndec sudo chmod -s `which chown`08:24
*** zeeblex <zeeblex!apalalax@nat/intel/x-egyfaqzurcstnhlv> has joined #yocto08:25
*** honschu <honschu!~honschu@p508F6F61.dip0.t-ipconnect.de> has joined #yocto08:26
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto08:26
ndecbluelightning: hehe... in gcc-runtime do_install, i found this:     chown -R root:root ${D}                                                            |08:28
*** jbaxter <jbaxter!~jbaxter@jimbax.plus.com> has quit IRC08:28
ndecperhaps we should add a 'sanity' check for that situation. and make sure critical commands don't have +s bit.08:29
*** belen <belen!Adium@nat/intel/x-htinqborqimpaxmv> has joined #yocto08:29
bluelightningndec: the question is how did they come to have that bit set in the first place?08:30
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC08:30
ndecbluelightning: by installing a 'company required' SDK on his linux pc.08:30
bluelightningoh dear08:30
ndecyeah... if they wanted to increase security, that's lame ;-)08:31
bluelightningsomeone ought to point out to whoever produces that SDK what a massive security hole they're enforcing on their users08:31
ndecyep... and I won't name that company, but it's a very well known very large corporation ;-)08:32
ndecbluelightning: do you think we should add a sanity check for that? since we now know that it does break the build...08:33
bluelightningif it's likely to be encountered by more than a few users in an isolated environment then it seems like we should have a check for it08:34
bluelightningndec: if you haven't already it would be good to run through a full fresh build on the machine with those things disabled just to make sure that was definitely the cause of the problem08:38
ant_workI somehow remember there was a bit of discussion about that chown08:38
ant_workhttp://cgit.openembedded.org/openembedded-core/commit/meta/recipes-devtools/gcc/gcc-configure-runtime.inc?id=db99a65b3e93dfacc27ea821c788f15b5de3a49708:47
ndecbluelightning: yes, a fresh build works now.08:47
ndecant_work: well, i think that line in this commit, is exactly what's causing the problem.08:48
ndecon the machine which had chown with +s bit.08:48
*** belen1 <belen1!~Adium@134.134.137.75> has joined #yocto08:48
ant_workhttp://lists.openembedded.org/pipermail/openembedded-core/2011-June/042775.html08:48
ant_workno, this one08:49
ant_workhttp://lists.openembedded.org/pipermail/openembedded-core/2011-June/043556.html08:49
*** belen <belen!Adium@nat/intel/x-htinqborqimpaxmv> has quit IRC08:50
ant_workspecifically gcc08:50
ant_workhttp://lists.openembedded.org/pipermail/openembedded-core/2011-June/043831.html08:50
*** jackmitchell <jackmitchell!~Thunderbi@host217-34-104-101.in-addr.btopenworld.com> has quit IRC09:00
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC09:03
*** jackmitchell <jackmitchell!~Thunderbi@host217-34-104-101.in-addr.btopenworld.com> has joined #yocto09:03
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto09:07
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has joined #yocto09:16
*** OlivierG` <OlivierG`!~OlivierG@LVelizy-156-44-42-252.w217-128.abo.wanadoo.fr> has joined #yocto09:17
*** OlivierG` <OlivierG`!~OlivierG@LVelizy-156-44-42-252.w217-128.abo.wanadoo.fr> has left #yocto09:18
*** RagBal <RagBal!~RagBal@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto09:21
*** Rootert <Rootert!~Rootert@54694E34.cm-12-2b.dynamic.ziggo.nl> has joined #yocto09:21
*** exosyst <exosyst!~nick@2.26.109.249> has joined #yocto09:22
erenmorning all09:24
*** jukkar1 <jukkar1!jukka@nat/intel/x-bwhkeabxdzxogcaj> has quit IRC09:26
*** jukkar <jukkar!jukka@nat/intel/x-yatttauwtthqpehh> has joined #yocto09:28
bluelightninghi eren09:29
*** jbaxter <jbaxter!~jbaxter@jimbax.plus.com> has joined #yocto09:31
erenbluelightning: https://lists.yoctoproject.org/pipermail/yocto/2013-July/017268.html09:32
erenlibcurl disables sftp, I am wondering if we should add it with PACKAGECONFIG09:32
erenhowever, we should first package libssh2 library09:32
erenany idea?09:32
bluelightningeren: right, we'd have to have a libssh2 recipe somewhere before adding that I think09:32
bluelightningI searched and there is only a libssh recipe in some unofficial layer which I'm guessing is not the same thing anyway09:33
erenbluelightning: is it worth packaging?09:37
erenthere seems to be one case, actually09:37
erenI'm not sure if libcurl with sftp is desired by most people09:38
bluelightningright, any additional libssh2 library would probably go into another layer such as meta-networking or meta-oe09:38
*** Stygia <Stygia!~gmpsaifi@0904ds6-noe.0.fullrate.dk> has joined #yocto09:39
StygiaA question to any number of the yocto project here - If I have written a significant number of recipes, many of which did not exist in advance, and want to contribute to the project - Should I just create my own layer and place it in a public repository, or is there a recommend procedure or collection of recipes somewhere where I could place them?09:41
Stygia*member of the09:41
*** ruben__ <ruben__!d908320e@gateway/web/freenode/ip.217.8.50.14> has joined #yocto09:50
bluelightningStygia: in the general case it depends on what category the recipes fall into09:52
bluelightningStygia: for your specific perl recipe case, we don't have a specific place for perl recipes outside OE-Core, so it seems reasonable to create one09:53
Stygiabluelightning, In this case, I have mostly cpan recipes, and then a few regular programs.09:53
Stygiabluelightning, Create one on my own repo, or as part of the project?09:53
Stygiabluelightning, I also made one for CCRYPT today, not related to the (presumably so-named) future meta-cpan layer.09:53
bluelightningStygia: unrelated recipes would go somewhere else; if there's no obvious place they could go to meta-oe09:54
Stygiabluelightning, I'm still somewhat in doubt. You are saying to contribute it directly back to OE/Yocto, as opposed to just hosting it all on my own repository, yes?09:55
bluelightningStygia: the OE community is fine with people maintaining layers in their own repos09:55
bluelightningStygia: it just gets a bit tricky if we have recipes in more central layers such as meta-oe depending on recipes in a layer that isn't in the same repository09:56
Stygiabluelightning, Well, alright, I will do that then. Is there a central place to help people find existing layers, not for hosting, but maybe just as a navigational aid?09:56
Stygiabluelightning, If not I think maybe there should be.09:57
bluelightningStygia: at the moment no such dependencies exist though; the issue can be addressed later if need be09:57
bluelightningStygia: sure, there's the layer index at http://layers.openembedded.org09:57
bluelightningthat provides a way for people to find out about the existence of any particular recipe no matter which layer it's in09:58
Stygiabluelightning, Yes exactly, great, that's what I needed. :) Well in that case I think I"m pretty set (until the next recipe gives me trouble), I'll finish up, make the repo public, and add it to that listing.09:59
bluelightningStygia: awesome :)09:59
Stygiabluelightning, Although, I think maybe CCRYPT could be included in the actual core distribution, maybe, it doesn't fit with meta-cpan and has no dependencies outside virtual/something which came build-in.09:59
bluelightningStygia: for that one it's probably best to submit a patch to add it to meta-oe10:00
Stygiabluelightning, Alright, I will do. Since I've honestly never contributed to an open-source project before... if I check out meta-oe, add my file and push it, then they will look at it and review my commit, yes?10:01
bluelightningStygia: this should help: http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded10:01
Stygiabluelightning, Thanks dude.10:02
Stygiabluelightning, Or dudeette, whatever.10:02
bluelightningStygia: dude in this case, but nice of you to consider the inherent ambiguity :)10:02
Stygiabluelightning, In my language it's much easier to just say something like 'dude' without worrying about gender.10:07
Stygiabluelightning, We do say 'man' to women but nobody really "notices"10:08
Stygiabluelightning, Only as slang.10:08
ant_workunforgivable ;)10:08
Stygiaant_work, Actually in most languages the male pronoun is the recognized "default". :P He doesn't always imply gender.10:12
Stygiaant_work, Although I think that only applies to English/Anglosax language group.10:12
rburtoni'd say "he" does imply gender in english, but it's abused because there isn't a non-gendered word that isn't archaic10:13
Stygiarburton, Well it does, but it is also the default pronoun AFAIK. Thou/thee is too old, but AFAIK "he" is what's supposed to be the default.10:14
Stygiarburton, I know books that consistently use "she" throws me off, because it's unusual, whereas "he" just gets skimmed.10:14
Stygiarburton, Although that is simply force of habit I do believe it's a semi-official convention, yea?10:14
pevYou can use "they" in some circumstances - a bit rude referring to people in the 3rd person if they're present though :-D10:15
rburtonhe is certainly the default option if the gender is unknown, but that's mainly just #everydaysexism ;)10:15
Stygiapev, Our "they"/thee is uber-polite, but not as archeic as Thou/Thee10:15
Stygiarburton, Well yes it is, but at this point trying to mess with the default pronoun is pointless and confusing IMHO.10:16
pevStygia:  Interesting! I like it when languages evolve but keep polite bits in still. I think it says something about the culture and personality of the people using the language...10:17
Stygiapev, Yes it does, although now we only use "thee" for really oldish people, it's like "Sir"/Mam to us, but a bit more archeic.10:17
Stygiapev, Danish, FYI.10:17
pevThat would make sense ; all the Danes I've met have been very polite!10:18
pevAlthough the "Sir" thing in the states always confuses me - it comes across as polite but the way people act while saying it generally makes it feel really false...!10:18
*** Umeaboy <Umeaboy!~Umeaboy@213-21-78-12.customer.t3.se> has quit IRC10:20
bluelightningI always hate being called sir10:25
*** rogerzhou <rogerzhou!~rogerzhou@1.202.252.122> has quit IRC10:39
*** swex_ <swex_!~swex@178.17.201.79> has joined #yocto11:01
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC11:03
*** swex <swex!~swex@178.17.201.24> has quit IRC11:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto11:05
StygiaHmm, if I have a recipe installing files into a shared area where those files already exist, and I am using automation (such as inherit cpan), can I prevent the warnings/errors without having to make a FILES_${PN} array for each recipe?11:06
bluelightningStygia: it's not really a FILES issue; the clashing files shouldn't be being installed in do_install (or more precisely, only one recipe should be doing that)11:07
*** Net147 <Net147!~Net147@60-242-179-244.static.tpgi.com.au> has joined #yocto11:08
Stygiabluelightning, Well, I'm not manually doing it for either recipe, I have two CPAN recipes, both using "inherit cpan", and they're conflicting.11:08
bluelightningStygia: no, it's likely an upstream issue; the workaround is to just add a do_install_append to delete the files11:08
Stygiabluelightning, Ah right, I will do that then. Presumably, upstream as in CPAN, yes?11:09
Stygiabluelightning, And not as in the maintainers of cpan.bbclass\11:09
bluelightningStygia: the specific cpan package I would think11:09
Stygiabluelightning, Seems likely, it's not the first package to install things provided by other packages.11:09
bluelightningStygia: I'm assuming it's not a case of a cpan script auto-downloading dependencies...11:10
Stygiabluelightning, Not in this case, I don't think.11:10
bluelightningok11:10
Stygiabluelightning, Although, looking back to my first week of barely being able to use bb, presumably that's exactly went wrong with my DateTime recipe back then.11:11
Stygiabluelightning, Not that it matters now though. :)11:12
Stygiabluelightning, After these couple of weeks, I could probably troll this newsgroup and be of help to news when you or rburton weren't around.11:12
*** klinger <klinger!~klinger@g228060008.adsl.alicedsl.de> has quit IRC11:24
pevHm, does DEPENDS imply RDEPENDS or do I need to set both?11:44
*** walters <walters!~walters@c-66-31-18-51.hsd1.ma.comcast.net> has quit IRC11:44
Stygiapev, They're different.11:45
Stygiapev, DEPENDS, AFAIK, lists build-time dependencies.11:45
Stygiapev, Things needed to actually build the package.11:45
Stygiapev, Whereas RDEPENDS is runtime dependencies, i.e. things needed for the package to even run.11:45
pevAm I right in thinking DEPENDS relate to recipe names and RDEPENDS is package names?11:46
Stygiapev, Ask bluelightning or rburton for confirmation, but I am pretty sure.11:46
Stygiapev, Nope, both recipe names AFAIK11:46
Stygiapev, The difference is, a DEPENDS will not necessarily be included in the image that uses the package that DEPENDS on it, whereas an RDEPENDS means "build this and include it"11:46
pevStygia:  Ahhh http://www.yoctoproject.org/docs/1.4/ref-manual/ref-manual.html#var-RDEPENDS11:48
Stygiapev, Huh. Well then clearly you are right.11:49
Stygiapev, Although, if I'm not mistaken, aren't package names _usually_ equal to recipe names?11:49
pevStygia:  Not sure, I think so - except a recipe can define quite a few package names based off the same root name e.g. -dev -dbg etc?11:50
pev*superset11:50
Stygiapev, Ah right, I do think so then. Unless you specify a package name explicitly, I think it becomes everything before _ in the recipe name.11:51
Stygiabluelightning, rburton would know.11:51
pevStygia:  So, I'm trying to test I've got it right. Is the right thing to do to blow away my three interdependent recipies via bitbake -c cleanall and then retest building the recipe that needs its dependencies satisfied?11:52
*** joeythesaint <joeythesaint!~jjm@128.224.252.2> has joined #yocto11:59
Stygiapev, Yes, in my experience.12:02
Stygiapev, But we warned cleanall removes changes to config from a menuconfig action12:02
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto12:03
*** zeddii_home <zeddii_home!~zeddii_ho@CPE002369bcfa62-CMbcc810032faf.cpe.net.cable.rogers.com> has joined #yocto12:12
bluelightningDEPENDS is a build-time dependency, RDEPENDS is runtime12:12
bluelightningthe value of PN is derived from the recipe file name yes12:13
Stygiabluelightning, Thanks. :) Thought so.12:13
bluelightningyou can see how in conf/bitbake.conf, if you're interested12:14
Stygiabluelightning, Immediately, there's no such file in my build/conf directory.12:15
bluelightningStygia: meta/conf/bitbake.conf12:16
bluelightning(sorry, I should be more specific)12:16
Stygiabluelightning, Heh, the more specific version would be sources/poky/meta/conf/bitbake.conf12:17
Stygiabluelightning, I was in the build directory which also has a conf dir, was confused. :) But I'd have lived anway, locate is installed after all.12:17
bluelightningwell, above meta/ it depends on where you've cloned it and what name you've cloned it as :)12:18
Stygiabluelightning, Ah, fair enough. I did not know that. :) My boss set all this up and then set me to work writing recipes.12:19
bluelightningah right, fair enough12:19
*** challinan_ is now known as challinan12:20
Stygiabluelightning, He's really the embedded guy, and I'm the "normal" dev, we're just a busy, tiny company.12:20
*** scot__ <scot__!~scot@client-74-113.natinst.com> has joined #yocto12:26
*** Bagder <Bagder!~daniel@178.174.211.166> has joined #yocto12:29
*** Bagder <Bagder!~daniel@rockbox/developer/bagder> has joined #yocto12:29
Stygiabluelightning, Hey, which is more correct, RPROVIDES, or RPROVIDES_${PN}?12:32
*** zeeblex <zeeblex!apalalax@nat/intel/x-egyfaqzurcstnhlv> has quit IRC12:33
bluelightningStygia: the latter12:34
Stygiabluelightning, Thanks.12:34
bluelightningStygia: you'll get a warning if you use the former since it would apply to all packages in the recipe, which 99% of the time is not what you want12:34
Stygiabluelightning, Ah alright, I did use the latter ,but then I saw a comment on a patch saying the former was wrong (without explaination), and I wondered12:39
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-rchxjcmcjdiiumxm> has joined #yocto12:45
*** davest <davest!Adium@nat/intel/x-gjmvfslazuvtbhwx> has joined #yocto12:49
*** zeeblex <zeeblex!~apalalax@134.134.139.70> has joined #yocto12:52
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-rchxjcmcjdiiumxm> has quit IRC12:52
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-wjhgflvsyncgnrel> has joined #yocto12:57
*** davest <davest!Adium@nat/intel/x-gjmvfslazuvtbhwx> has quit IRC12:59
*** sameo <sameo!~samuel@192.55.54.40> has joined #yocto13:01
*** zenlinux <zenlinux!~sgarman@c-50-139-85-11.hsd1.or.comcast.net> has quit IRC13:03
*** OlivierG` <OlivierG`!~OlivierG@LVelizy-156-44-42-252.w217-128.abo.wanadoo.fr> has joined #yocto13:05
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto13:13
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC13:14
*** addu <addu!~addu@sestofw01.enea.se> has quit IRC13:16
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto13:21
*** behanw <behanw!~behanw@216-58-123-51.cpe.distributel.net> has joined #yocto13:21
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC13:24
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto13:27
*** walters <walters!walters@nat/redhat/x-yyxlgzzaczvzqsjp> has joined #yocto13:28
zeckebluelightning: hi, one more question.. I'm using opkg and I noticed that on rootfs creation the package database didn't make it into the image13:30
*** bluelightning_ <bluelightning_!~paul@83.217.123.106> has joined #yocto13:30
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:30
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:31
zeckebluelightning: hi, one more question.. I'm using opkg and I noticed that on rootfs creation the package database didn't make it into the image. is this known? a feature?13:32
rburtondid you includes package-management in your image features?13:33
zecke /var/lib/opkg is empty in my image. :}13:33
zeckerburton: yeah, but I assume there is probably another variable I need to set. I am slowly upgrading from edison to master13:33
bluelightning_zecke: package-management needs to be in IMAGE_FEATURES and you need to avoid adding remove_packaging_data_files to ROOTFS_POSTPROCESS_COMMAND (as core-image-minimal used to)13:36
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-wjhgflvsyncgnrel> has quit IRC13:37
*** bluelightning_ is now known as bluelightning13:38
zeckebluelightning_: ah yeay, package-management is missing. what is the most sensible place for it? the image.bb?13:39
bluelightningzecke: it's up to you really; it depends on whether package management is something fundamental to the image, or all images in your distro config13:40
*** tinti <tinti!~tinti@maxtrack-F4-0-3-gacc04.bhe.embratel.net.br> has joined #yocto13:41
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto13:41
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-jqbjlkcymysjeudz> has joined #yocto13:43
zeckebluelightning: thanks!13:45
zeckerburton: how open are you to include changes like this? http://lists.freedesktop.org/archives/systemd-devel/2013-July/012115.html?13:46
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC13:47
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has joined #yocto13:48
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-jqbjlkcymysjeudz> has quit IRC13:48
rburtonzecke: seems reasonable13:51
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-dycczehayaakjcxk> has joined #yocto13:56
panda84kdeHi guys. Hello everybody. I've got a problem listed at the end of this paste: http://pastebin.com/afUBJyUs13:58
panda84kdeto sum it up: I have a custom image based on fsl-image-gui on which I added a custom layer to which I added lirc from https://github.com/Guacamayo/meta-guacamayo/blob/master/meta-guacamayo/recipes-support/13:59
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-dycczehayaakjcxk> has quit IRC14:00
panda84kdei'm having this do_rootfs problem, I think due to the fact I added DRIVER ?= "--with-driver=irman" to lirc-config.inc14:00
panda84kdenow I've commented lirc from my image, but still get the error.14:01
panda84kde2 things: 1) how do I clean out the error? bitbake -c my-image-sdk doesn't seem to help. 2) How do I debug do_rootfs fuction? I don't really know what's causing that error!14:02
cristianiorgaNet147: Hello Jonathan14:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC14:04
cristianiorgaNet147: related to http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b52d2bb46ed7c893077ccf9e5a83dc7f11c7f61b14:05
cristianiorgaNet147: boot-directdisk: allow specifying custom MBR disk signature14:05
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto14:05
bluelightningpanda84kde: the issue is in meta/classes/license.bbclass14:05
bluelightningpanda84kde: for some reason it can't find a package directory for the package that's going to be installed14:06
bluelightningpanda84kde: aside from that it shouldn't really be erroring out like that though14:06
panda84kdebluelightning: first of all hi and thank you :)14:07
panda84kdebluelightning: step2: how did you get it's a problem of licence.bbclass? Just because there were warnings about license in the previous lines?14:08
bluelightningpanda84kde: that and I also have seen this error before, although I've never been able to reproduce it14:09
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto14:11
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC14:12
*** bluelightning_ is now known as bluelightning14:12
Net147rburton: should I just remove the added patch for mesa git?14:15
Net147rburton: I was thinking since it is set to 9.1.5 release it should have the same patches14:15
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-luxfvqkzyddqxmyr> has joined #yocto14:16
panda84kdebluelightning: should be this "ls": http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/classes/license.bbclass#n3114:17
rburtonNet147: just sent another mail - the git "upgrade" was actually a downgrade14:17
cristianiorgaNet147: regarding issue https://bugzilla.yoctoproject.org/show_bug.cgi?id=4859; seems to be somehow caused by the aforementioned patch14:17
yoctiBug 4859: major, High, 1.5 M3, cristian.iorga, IN PROGRESS DESIGN , Build Appliance does not boot in vmWare Player14:17
ant_workpanda84kde: which packages have been created by lirc-modules?14:18
*** darknighte_znc is now known as darknighte14:19
Net147cristianiorga: seems odd14:19
cristianiorgaNet147: well; you tested that patch with syslinux as the primary bootloader, right?14:20
Net147cristianiorga: yes14:20
cristianiorgaNet147:  in case of BA, the primary bootloader is the BIOS, which (most probabnly) loads the first 440bytes and executes from MBR14:21
cristianiorgaNet147: but according to wikipedia, the MBR with the disk signature info in it has the first 440 bytes different from the content of the MBR without disk signature14:22
panda84kdeant_work: could you please detail the question a bit further? I have no files generated by lirc-modules, I already have lirc modules in my kernel14:22
Net147christianiorga: parted actually generates a disk signature when I checked it. but it's not really random enough.14:22
cristianiorgaNet147: see https://en.wikipedia.org/wiki/Master_boot_record#PTE, Sector layout section, the two MBR formats, classical generic MBR and Structure of a modern standard MBR14:23
ant_workpanda84kde: I'm afk so cannot check but I see  https://github.com/Guacamayo/meta-guacamayo/blob/master/meta-guacamayo/recipes-support/lirc/lirc-modules_0.9.0.bb14:23
panda84kdeant_work: yes, I have and empty lirc-modules package14:24
Net147christianiorga: yes I consulted that page when writing the patch14:24
*** e8johan <e8johan!~quassel@p5B1526CC.dip0.t-ipconnect.de> has quit IRC14:25
cristianiorgaNet147: yes, but mbr.bin does not change if disk signature is included or not; or I am wrng on that assumption?14:25
ant_workpanda84kde: RDEPENDS_${PN} = "lirc-modules" doesn't pull  kernel-module-lirc-dev14:25
ant_workafais14:25
bluelightningpanda84kde: should lirc-modules even be used now that LIRC Is in the mainline kernel?14:26
Net147cristianiorga: mbr.bin is 440 bytes so it isn't supposed to touch the disk signature14:27
cristianiorgaNet147: Build Appliance is not starting in vmWare Player with a Missing Operating system error; to be honest, I saw that string in mbr.bin file, so ATM I am not sure that is displayed by vmWare emulated BIOS or by syslinux14:28
cristianiorgaNet147: no, but the format of first 440 bytes are different depending if disk signature is present in MBR or not; right?14:28
panda84kdeant_work: yes. I'm wondering why is my do_rootfs failing like that if kernel-module-lirc-dev is not mentioned?14:28
cristianiorgaNet147: that's according to wikipedia14:29
Net147cristianiorga: in my testing, parted creates the disk signature. so the patch doesn't change the fact that a disk signature is being created.14:30
ant_workpanda84kde: you can inspect the dependency chain14:31
panda84kdeant_work: any hint on how to do that?14:31
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC14:32
ant_worktry bitbake -g <foo> -u depexp14:33
cristianiorgaNet147: I might be wrong, but in your patch, the disk signature is not generated with parted, but using uuid module14:33
bluelightningpanda84kde: are you installing the main "kernel-modules" meta-package perhaps?14:33
Net147cristianiorga: parted generates one, but we overwrite it using one generated from uuid module14:34
cristianiorgaNet147: right; on the HW you used for testing, BIOS reads the MBR and starts syslinux, or syslinux is started directly as the initial bootloader? I am asking, because I don't know14:35
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto14:35
Net147cristianiorga: BIOS reads MBR and starts syslinux14:35
Net147cristianiorga: theoretically, changing the disk signature shouldn't affect the bootability unless there it is overwriting outside of the 4 byte range14:37
mulhernWriting a package for a Python script. It RDEPENDS on perl, pretty obviously, but how can I figure out the various Perl libraries that it RDEPENDS on to include them too?14:39
mulhernWhoops, "a Python script" should be "a Perl script".14:40
ant_workpanda84kde: I fail to find a maintainer of the layer but at first sight it needs some love14:41
sgw_Net147: can you do a basic test with your change using vmware player, we clearly are seeing an issue, it might be the bios that vmware uses or ???14:41
Net147cristianiorga: sgw_: what image type?14:42
cristianiorgaNet147: overwriting is a possibility, but does not seem to happen; If I would take a wild guess here, is that the emulated BIOS of vmWare Player machine does not play well with that added disk signature; according to the diagrams, if a disk signature is added, the format of the first 440 bytes changes; this does not happen in our syslinux, which provides the first 440 bytes from mbr.bin14:42
Net147cristianiorga: a disk signature is added regardless because parted adds one14:42
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.85.234.195.229> has joined #yocto14:43
*** e8johan <e8johan!~quassel@p5B1526CC.dip0.t-ipconnect.de> has joined #yocto14:43
fenrigHi how do I enlarge the size of the file system for qemu in yocto14:43
fenrigDo I have to enlarge the rootfs?14:43
fenrigor do I have to modify something in qemu?14:43
sgw_Net147: it uses IMAGE_FSTYPES = "vmdk"14:44
cristianiorgaNet147: yes, but maybe the BIOS of that specific board that you tested with is smarter than the BIOS of vmware and manages the change14:44
Net147cristianiorga: I tested in QEMU as well14:44
*** Stygia <Stygia!~gmpsaifi@0904ds6-noe.0.fullrate.dk> has quit IRC14:44
cristianiorgaNet147: Build Appliance runs in vmWare Player, not qemu; like I said, it might be an issue with vmWare machine BIOS14:45
panda84kdebluelightning: I'm not adding "kernel-modules" in my image. Could it be in "fsl-image-gui"?14:45
*** Stygia <Stygia!~gmpsaifi@0904ds6-noe.0.fullrate.dk> has joined #yocto14:46
Net147cristianiorga: downloading vmware player...14:46
cristianiorgaNet147: thanks a bunch14:47
sgw_fenrig: you can use IMAGE_ROOTFS_EXTRA_SPACE which will add space in your rootfs14:47
panda84kdeant_work: thanks.14:47
fenrigsgw_: is it in kilobytes, megabytes, ...?14:47
rburtonk14:47
cristianiorgafenrig: KB14:47
ant_workpanda84kde: there are machine specific overrides together with lower versions of some packages14:48
sgw_yes KB thanks all14:48
panda84kdeant_work: yeah. I just needed lirc but it seems it has been removed from poky: http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/packages/lirc/?h=elroy14:51
fenrigsgw_: Thx it worked14:52
panda84kdeant_work: is by chace depexp a GUI tool?14:53
panda84kde*chance14:53
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto14:53
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.85.234.195.229> has quit IRC14:54
panda84kdereply-to-self: yes, it is.14:56
Net147cristianiorga: in my testing, if I convert the image I use to vmdk format and boot, it boots syslinux and kernel but fails to find disk by the identifier14:57
Net147cristianiorga: so VMware doesn't boot. VirtualBox boots it fine though.14:57
Net147christianiorga: it would probably boot if using /dev/sda1 though14:58
Net147cristianiorga: I mean /dev/hda215:02
cristianiorgaNet147, sgw_ : So we know that it doesn't work; We don't know why :-) Ok, I will continue the investigation15:07
Net147cristianiorga: probably a start would be to do bitbake -C bootdirectdisk theimage, copy the vmdk somewhere, revert patch, bitbake -C bootdirectdisk theimage, compare the two images15:08
Net147cristianiorga: the differences should only be at offsets 440, 441, 442, 44315:08
cristianiorgaNet147: Do you think that is possible to add the testing steps that you performed in order to test with vmware player in the YB4859 bug report?15:09
Net147cristianiorga: I haven't got image for vmdk set up, so I just replicate command that vmdk class uses to convert the raw image to vmdk15:09
cristianiorgaNet147: Did that; I know what's causing it, I don't know how15:10
Net147cristianiorga: qemu-img convert -O vmdk image.hdddirect image.vmdk is that I did15:10
Net147cristianiorga: so are the differences only in those 4 bytes at most?15:10
cristianiorgaNet147: no, there are other differences, but those other differences might be generated by other factors, like timestamps, etc15:11
panda84kdeant_work: lirc-modules "Runtime Depends" on lirc-modules and lirc-modules-dev. I don't get the meaning of depending on itself, but anyhow I still don't get how kernel-module-lirc-dev gets in...15:12
Net147cristianiorga: well yes there is a disk timestamp that is optional 6 bytes15:12
Net147cristianiorga: but that should have been part of mbr.bin anyway15:12
cristianiorgaNet147: I will continue the investigation tomorrow, I will leave office now15:13
Net147cristianiorga: 0-439 is mbr.bin, 440-443 is disk signature, 444-445 is 0000, 446-509 is partition table (should be same), 510-511 should be 55aa15:14
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-luxfvqkzyddqxmyr> has quit IRC15:14
Net147cristianiorga: any invalidating bootdirectdisk should change the first sector15:14
Net147cristianiorga: the rest same15:15
cristianiorgaNet147: well, disk signature is changing the first 512 bytes, right?15:15
Net147cristianiorga: I only change 4 bytes in at offsets 440, 441, 442, 44315:15
*** zenlinux <zenlinux!~sgarman@c-50-139-85-11.hsd1.or.comcast.net> has joined #yocto15:16
*** darknighte is now known as darknighte_znc15:19
*** pidge <pidge!~pidge@134.134.137.75> has joined #yocto15:21
*** e8johan <e8johan!~quassel@p5B1526CC.dip0.t-ipconnect.de> has quit IRC15:25
*** zeeblex <zeeblex!~apalalax@134.134.139.70> has left #yocto15:26
*** volker__ <volker__!5051131d@gateway/web/freenode/ip.80.81.19.29> has joined #yocto15:29
*** slaine <slaine!~slaine@84.203.137.218> has quit IRC15:29
volker__I'm currently trying to build a yocto image under ubuntu 13.04 x64 for an i.MX6 Q7 module. So far everything is working fine, but I can't figure out how to build gdb-cross with python support. Any help?15:30
*** tbn_ <tbn_!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has joined #yocto15:30
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-yfwbgbkhdpphevvc> has joined #yocto15:32
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto15:33
*** Net147 <Net147!~Net147@60-242-179-244.static.tpgi.com.au> has quit IRC15:33
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC15:33
*** Guest97929 <Guest97929!~tbn@mad27-1-88-172-46-29.fbx.proxad.net> has quit IRC15:34
*** davest <davest!~Adium@134.134.139.74> has joined #yocto15:36
*** belen1 <belen1!~Adium@134.134.137.75> has quit IRC15:38
*** seebs <seebs!~seebs@home.seebs.net> has quit IRC15:47
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto15:48
zeckebluelightning: and another bug.. no one appears to install depmod these days15:49
*** belen1 <belen1!~Adium@134.134.137.75> has joined #yocto15:49
*** Stygia <Stygia!~gmpsaifi@0904ds6-noe.0.fullrate.dk> has quit IRC15:51
kergothSo, I'm working on consolidating volatiles and tmpfiles.d. the approach i'm taking is to add a build of systemd-tmpfiles separate from systemd, and b uild and use it for both systemd and sysvinit builds, have a separate binary package, and create a -native version with --sysroot= support for rootfs build time for read-only-rootfs.15:51
kergothdoes this seem like a sane approach?15:51
bluelightningzecke: I'll admit I don't know how it's normally supposed to be brought in, but it is supposed to be because module package postinstalls expect to be able to run it15:55
kergothdoesn't kmod provide that now? maybe i'm behind15:56
kergothi need to spend more quality time at runtime on real hardware, all i do is builds lately15:56
kergothheh15:56
kergothgetting rusty15:56
bluelightningI think it does, but I'm not able to find how that is normally pulled in as a runtime dependency15:56
kergothhuh15:57
bluelightningbrb changing networks15:58
kergothnot seeing it either, strange15:58
*** belen1 <belen1!~Adium@134.134.137.75> has quit IRC15:58
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC15:59
zeckekergoth: Yeah, module-init-tools-depmod installs depmod.. (depmod.kmod) but I don't know if systemd (linking to kmod) actually needs depmod at all. :}15:59
*** bluelightning_ <bluelightning_!~paul@83.217.123.106> has joined #yocto16:00
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:00
kergothprobably not, unless it wants to run modprobe16:00
kergothor the api function to do a modprobe16:00
* kergoth shrugs16:00
zeckekergoth: it does somehow load modules. I have not looked at the code.. but most likely an api call. :)16:00
* kergoth nods16:01
* zecke looks at this nice Oops in the TCPv4 stack on this v3.4 kernel. :}16:01
kergothouch16:01
zeckekergoth: GCC4.8 made my v3.2er kernel oops in do_loopup.c of namei.c :}16:02
kergothah16:02
zeckebut more often than the tcp crash. :)16:02
zeckeI try to figure out if my move to v3.4 is progress or just change16:03
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:03
erenzecke: oh, debugging gcc and kernel16:03
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC16:03
eren:/ he couldn't stand seeing the words gcc and kernel in the same sentence, I guess16:04
eren:P16:04
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has joined #yocto16:04
*** belen1 <belen1!~Adium@134.134.137.73> has joined #yocto16:04
kergothheheh16:05
*** bluelightning_ is now known as bluelightning16:06
kergothi need to stop missing the yocto technical calls, so i can stay current on 1.5 progress16:06
*** ant_work <ant_work!~ant@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC16:12
*** jackmitchell <jackmitchell!~Thunderbi@host217-34-104-101.in-addr.btopenworld.com> has quit IRC16:13
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-yfwbgbkhdpphevvc> has quit IRC16:27
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-bwboqziaqtfwshrj> has joined #yocto16:29
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:31
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-bwboqziaqtfwshrj> has quit IRC16:32
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-wvevhuvlmsebjbkh> has joined #yocto16:33
*** hollisb <hollisb!~hollisb@nat-wv.mentorg.com> has joined #yocto16:37
*** volker__ <volker__!5051131d@gateway/web/freenode/ip.80.81.19.29> has quit IRC16:38
*** mihai <mihai!~mihai@80.97.15.150> has quit IRC16:41
*** zenlinux <zenlinux!~sgarman@c-50-139-85-11.hsd1.or.comcast.net> has quit IRC16:55
*** dv__ <dv__!~quassel@chello080108009040.14.11.vie.surfer.at> has joined #yocto16:56
*** cetola <cetola!~cetola@74-92-165-193-Oregon.hfc.comcastbusiness.net> has joined #yocto16:57
*** dv_ <dv_!~quassel@chello080108009040.14.11.vie.surfer.at> has quit IRC16:57
*** pidge <pidge!~pidge@134.134.137.75> has quit IRC16:59
*** bluelightning_ <bluelightning_!~paul@83.217.123.106> has joined #yocto17:00
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:00
*** belen1 <belen1!~Adium@134.134.137.73> has quit IRC17:00
kergothCan someone remind me who we contact about ssh keys for git.yoctoproject.org, again?17:01
kergothdrawing a blank17:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:01
rburtonkergoth: halstead17:04
kergothah, right, thanks17:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC17:04
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC17:05
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto17:06
halsteadkergoth, Yep. Just e-mail michael@yoctoproject.org.17:06
*** bluelightning_ is now known as bluelightning17:06
*** pidge <pidge!~pidge@134.134.137.75> has joined #yocto17:18
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC17:20
*** panda84kde <panda84kde!~diego@static-217-133-170-65.clienti.tiscali.it> has quit IRC17:26
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:28
*** exosyst <exosyst!~nick@2.26.109.249> has quit IRC17:31
*** zenlinux <zenlinux!~sgarman@c-50-139-85-11.hsd1.or.comcast.net> has joined #yocto17:33
*** b1gtuna <b1gtuna!~adam@206.116.3.18> has quit IRC17:33
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto17:34
*** b1gtuna <b1gtuna!~adam@206.116.3.18> has joined #yocto17:40
zeckekhem: ping?17:41
*** eren <eren!~eren@unaffiliated/eren> has quit IRC17:43
*** b1gtuna <b1gtuna!~adam@206.116.3.18> has quit IRC17:45
*** atl <atl!~Adium@c-71-193-110-59.hsd1.il.comcast.net> has joined #yocto17:48
atlso close … Computing transaction...error: Can't install qtbase-tools-5.0.2-r2.0@armv7a_vfp_neon: no package provides /usr/bin/perl17:49
*** b1gtuna <b1gtuna!~adam@206.116.3.18> has joined #yocto17:52
*** pidge <pidge!~pidge@134.134.137.75> has quit IRC17:55
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC17:59
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC18:04
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto18:04
kergothso, intercept scripts are teh things that get run once per package manager invocation, or once for the entire rootfs population, rather than repeatedly for each related package, correct? e.g. depmod, ldconfig, ..18:18
*** darknighte_znc is now known as darknighte18:23
*** jzhang1 <jzhang1!jzhang@nat/intel/x-vezbaqanyfyvskgs> has quit IRC18:30
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-wvevhuvlmsebjbkh> has quit IRC18:32
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-cxlhfovbsammawcp> has joined #yocto18:33
*** sameo <sameo!~samuel@192.55.54.40> has quit IRC18:35
*** Garibaldi|work1 <Garibaldi|work1!~andydalt@nat/cisco/x-itvpwfmvbdhuwydk> has joined #yocto18:36
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-cxlhfovbsammawcp> has quit IRC18:37
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC19:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto19:06
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC19:08
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto19:10
*** zecke <zecke!~ich@91-65-247-193-dynip.superkabel.de> has quit IRC19:10
kergothhmm, debian has dpkg set up to support something like our do_rootfs intercepts, i wonder if we support that too, or if all we can handle is do_rootfs time bits right now19:12
kergothi expect the latterp19:12
walterskergoth: we were talking about %posttrans the other day from rpm19:13
kergothah, so taking advantage of such things will likely become a future task19:13
*** Garibaldi|work1 <Garibaldi|work1!~andydalt@nat/cisco/x-itvpwfmvbdhuwydk> has quit IRC19:20
rburtonkergoth: dpkg triggers are nice19:25
rburtonkergoth: just need someone to make opkg do the same ;)19:25
kergothindeed19:26
kergothor just bite the bullet and make a replacement19:27
kergothopkg hurts my head19:27
kergoth:)19:27
rburtonif someones doing that they might as well use dpkg, i suspect19:27
kergothapt-get sucks on embedded. if they don't need network, sure19:27
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC19:29
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto19:32
*** bluelightning <bluelightning!~paul@cpc13-lewi17-2-0-cust74.2-4.cable.virginmedia.com> has joined #yocto19:35
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:35
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-qickockcttdtarep> has joined #yocto19:44
mr_scienceopkg isn't so bad...19:46
mr_sciencei can remember ipkg being a bit wonky at times19:47
*** zenlinux <zenlinux!~sgarman@c-50-139-85-11.hsd1.or.comcast.net> has quit IRC19:59
*** zenlinux <zenlinux!~sgarman@c-50-139-85-11.hsd1.or.comcast.net> has joined #yocto20:01
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has joined #yocto20:06
*** yzhao2 <yzhao2!~yzhao2@128.224.252.2> has quit IRC20:13
*** andyross <andyross!~andy@c-67-171-188-207.hsd1.or.comcast.net> has quit IRC20:24
*** joeythesaint <joeythesaint!~jjm@128.224.252.2> has quit IRC20:27
*** atl <atl!~Adium@c-71-193-110-59.hsd1.il.comcast.net> has left #yocto20:30
*** scot__ is now known as scot20:38
*** agust <agust!~agust@p4FC4641B.dip0.t-ipconnect.de> has quit IRC20:52
*** ant_home <ant_home!~andrea@host96-245-dynamic.48-82-r.retail.telecomitalia.it> has joined #yocto20:58
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC21:10
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto21:20
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-qickockcttdtarep> has quit IRC21:26
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC21:41
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto21:42
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has quit IRC21:46
*** davest <davest!~Adium@134.134.139.74> has quit IRC21:55
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has quit IRC21:58
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC21:58
*** mranostay <mranostay!~mranostay@ec2-54-215-127-238.us-west-1.compute.amazonaws.com> has quit IRC21:58
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto21:58
*** mulhern <mulhern!~mulhern@c-24-128-153-12.hsd1.ma.comcast.net> has joined #yocto21:58
*** walters <walters!walters@nat/redhat/x-yyxlgzzaczvzqsjp> has quit IRC22:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has quit IRC22:04
*** ericben <ericben!~ebenard@pac33-3-88-170-243-169.fbx.proxad.net> has joined #yocto22:06
*** smartin <smartin!~smartin@20-87-190-109.dsl.ovh.fr> has joined #yocto22:23
*** smartin_ <smartin_!~smartin@20-87-190-109.dsl.ovh.fr> has quit IRC22:24
*** b1gtuna <b1gtuna!~adam@206.116.3.18> has quit IRC22:26
*** b1gtuna <b1gtuna!~adam@206.116.3.18> has joined #yocto22:28
*** FlamesOfEternity <FlamesOfEternity!~paradox@s83-179-40-164.cust.tele2.se> has quit IRC22:28
b1gtunaAnyone knowledgeable with wireless-crda? I'm getting a nasty stack trace saying CRDA cannot be updated. This only happened when I have no internet connection22:29
*** zenlinux <zenlinux!~sgarman@c-50-139-85-11.hsd1.or.comcast.net> has quit IRC22:38
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC22:54
*** dv__ is now known as dv_22:54
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC22:55
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has quit IRC22:57
mr_scienceb1gtuna: nope23:01
mr_sciencemaybe if your nick was hottuna...23:01
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has joined #yocto23:03
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has joined #yocto23:03
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has quit IRC23:05
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@autobuilder.yoctoproject.org> has joined #yocto23:05
*** jbaxter <jbaxter!~jbaxter@jimbax.plus.com> has quit IRC23:11
*** zeddii <zeddii!~ddez@128.224.252.2> has quit IRC23:15
*** vmeson <vmeson!~quassel@128.224.252.2> has quit IRC23:17
b1gtunamr_science: LAWL next life i will be23:18
*** vmeson <vmeson!~quassel@128.224.252.2> has joined #yocto23:22
*** zeddii <zeddii!~ddez@128.224.252.2> has joined #yocto23:22
*** cetola <cetola!~cetola@74-92-165-193-Oregon.hfc.comcastbusiness.net> has quit IRC23:33
b1gtunalet me try again, how do I use full (proper tools?) instead of busybox?23:36
b1gtunaThanks in advance :)23:36
*** doerrpau <doerrpau!~doerrpau@cpe-70-124-65-123.austin.res.rr.com> has joined #yocto23:37
b1gtuna(I think udhcpc is conflicting with networkmanager, so I'm trying to get rid of the former)23:37
*** ant_home <ant_home!~andrea@host96-245-dynamic.48-82-r.retail.telecomitalia.it> has quit IRC23:43
*** b1gtuna <b1gtuna!~adam@206.116.3.18> has quit IRC23:58

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!