Wednesday, 2013-12-11

*** davest <davest!Adium@nat/intel/x-ytgcrwfqrdemmjoz> has joined #yocto00:00
*** [simar|on] <[simar|on]!> has joined #yocto00:08
-YoctoAutoBuilder- build #40 of nightly-fsl-arm is complete: Success [build successful] Build details are at
*** ant_home <ant_home!> has quit IRC00:27
*** sameo <sameo!~samuel@> has quit IRC00:34
*** dany <dany!> has quit IRC00:47
-YoctoAutoBuilder- build #42 of nightly-oecore is complete: Failure [failed] Build details are at
*** dany <dany!> has joined #yocto00:47
*** hollisb <hollisb!> has quit IRC00:51
*** JaMa <JaMa!> has joined #yocto00:55
*** davest <davest!Adium@nat/intel/x-ytgcrwfqrdemmjoz> has quit IRC00:58
*** davest <davest!Adium@nat/intel/x-wgyrxoginxldizvz> has joined #yocto00:58
*** walters <walters!> has quit IRC01:07
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:29
*** _tid <_tid!> has quit IRC01:32
*** [simar|on] <[simar|on]!> has quit IRC01:34
*** nitink <nitink!~nitink@> has quit IRC01:35
*** _tid <_tid!> has joined #yocto01:44
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC01:46
*** fusman <fusman!~fahad@> has joined #yocto01:47
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:53
*** bingbu <bingbu!~mars@> has joined #yocto02:03
*** fusman <fusman!~fahad@> has quit IRC02:05
*** nitink <nitink!nitink@nat/intel/x-zwjuaapgqqgxzqfw> has joined #yocto02:23
*** dvhart <dvhart!dvhart@nat/intel/x-xqfwbhpwodpfofja> has quit IRC02:31
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto02:39
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC02:44
*** silviof2 <silviof2!> has joined #yocto03:01
*** silviof1 <silviof1!~silviof@unaffiliated/silviof> has quit IRC03:04
*** fusman <fusman!~fahad@> has joined #yocto03:10
*** zeddii_home <zeddii_home!> has joined #yocto03:17
*** fusman <fusman!~fahad@> has quit IRC03:17
*** fusman <fusman!~fahad@> has joined #yocto03:17
*** fusman <fusman!~fahad@> has quit IRC03:20
*** fusman <fusman!~fahad@> has joined #yocto03:21
*** fusman <fusman!~fahad@> has quit IRC03:27
*** [simar|on] <[simar|on]!> has joined #yocto03:27
*** fusman <fusman!~fahad@> has joined #yocto03:28
-YoctoAutoBuilder- build #42 of nightly-qa-systemd is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #42 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #43 of buildtools is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #42 of poky-tiny is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #42 of minnow is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #43 of nightly-non-gpl3 is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #41 of nightly-x32 is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #42 of nightly-x86-64 is complete: Failure [failed] Build details are at
*** [simar|o1] <[simar|o1]!> has joined #yocto04:01
*** Jefro <Jefro!> has joined #yocto04:01
-YoctoAutoBuilder- build #40 of nightly-arm is complete: Failure [failed] Build details are at
*** [simar|on] <[simar|on]!> has quit IRC04:04
*** silviof3 <silviof3!> has joined #yocto04:11
*** silviof2 <silviof2!> has quit IRC04:14
*** Squix__ <Squix__!> has joined #yocto04:21
*** abelloni_ <abelloni_!> has joined #yocto04:24
*** silviof3 <silviof3!> has quit IRC04:24
*** abelloni <abelloni!> has quit IRC04:24
*** Squix <Squix!> has quit IRC04:24
*** dzoe <dzoe!> has quit IRC04:24
*** silviof3 <silviof3!> has joined #yocto04:29
*** dzoe <dzoe!> has joined #yocto04:31
-YoctoAutoBuilder- build #41 of nightly-fsl-ppc is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #41 of nightly-x86 is complete: Failure [failed Building Images_1] Build details are at
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto04:52
*** sunfunbaby <sunfunbaby!> has joined #yocto04:56
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC05:01
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto05:03
*** Jefro <Jefro!> has quit IRC05:07
*** [simar|on] <[simar|on]!> has joined #yocto05:08
*** [simar|o1] <[simar|o1]!> has quit IRC05:12
*** Jefro <Jefro!> has joined #yocto05:20
*** Jefro <Jefro!> has quit IRC05:20
-YoctoAutoBuilder- build #43 of nightly-fsl-ppc-lsb is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
*** [simar|o1] <[simar|o1]!~simar@> has joined #yocto05:30
*** [simar|on] <[simar|on]!> has quit IRC05:33
*** [simar|on] <[simar|on]!~simar@> has joined #yocto05:37
*** [simar|o1] <[simar|o1]!~simar@> has quit IRC05:40
*** GusBricker <GusBricker!> has quit IRC06:16
*** SorenHolm <SorenHolm!> has joined #yocto06:20
*** SorenHolm <SorenHolm!> has quit IRC06:25
-YoctoAutoBuilder- build #43 of poky-tiny is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #44 of nightly-non-gpl3 is complete: Success [build successful] Build details are at
*** Squix__ <Squix__!> has quit IRC06:57
*** g1zer0 <g1zer0!> has joined #yocto07:03
*** g1zer0 <g1zer0!> has joined #yocto07:03
*** silviof3 is now known as silviof07:10
*** SorenHolm <SorenHolm!> has joined #yocto07:32
*** agust <agust!> has joined #yocto07:33
*** ak77 <ak77!c12e4b04@gateway/web/freenode/ip.> has joined #yocto07:42
ak77is there a way to compile qt console application, and not import whole qt4x11 ?07:42
*** ant_work <ant_work!> has joined #yocto07:44
LetoThe2ndak77: have you looked into the qt4e examples?07:45
*** e8johan <e8johan!> has joined #yocto07:47
ak77LetoThe2nd: where would that be? (looking in /yocto/poky/meta/recipes-qt/)07:49
LetoThe2ndak77: ./meta/recipes-qt/images/qt4e-demo-image.bb07:50
LetoThe2ndand whatever it pulls in, of course.07:50
*** Zagor <Zagor!> has joined #yocto07:56
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto07:56
*** [simar|on] <[simar|on]!~simar@> has quit IRC07:57
*** [simar|on] <[simar|on]!~simar@> has joined #yocto07:57
*** bingbu <bingbu!~mars@> has quit IRC08:05
*** n01 <n01!> has joined #yocto08:05
*** roric <roric!~roric@> has joined #yocto08:07
*** [simar|o1] <[simar|o1]!> has joined #yocto08:12
*** eballetbo <eballetbo!> has joined #yocto08:14
*** [simar|on] <[simar|on]!~simar@> has quit IRC08:16
*** kbart <kbart!~KBart@> has joined #yocto08:18
kbartCan somebody please tell me, what's wrong with this line: SRC_URI = "git@;protocol=git"?08:19
kbartI get an error: MalformedUrl: The URL: 'git@;protocol=git' is invalid and cannot be interpreted08:19
kbartI've tried "protocol=ssh", but it's still the same08:20
*** _tid <_tid!> has quit IRC08:24
*** bingbu <bingbu!~mars@> has joined #yocto08:25
erbokbart: I think you should have a / instead of : after the ip/host, try git@;protocol=git"08:25
erboand protocol ssh if that's what you want08:25
*** [simar|on] <[simar|on]!~simar@> has joined #yocto08:29
*** [simar|o1] <[simar|o1]!> has quit IRC08:30
*** GusBricker <GusBricker!> has joined #yocto08:31
kbarterbo, still the same. But if I do "git clone git@" manually, it works perfectly..08:33
*** [simar|on] <[simar|on]!~simar@> has quit IRC08:34
erbokbart: oh, you miss the git:// in the beginning08:34
erboSRC_URI = "git://git@....."08:34
*** panda84kde <panda84kde!> has joined #yocto08:35
*** _tid <_tid!> has joined #yocto08:37
kbartAh, that was it! Thank you erbo.08:37
*** fpaut_ is now known as fpaut08:38
*** jamestunnicliff_ <jamestunnicliff_!~quassel@linaro/jamestunnicliffe> has quit IRC08:38
*** jamestunnicliffe <jamestunnicliffe!~quassel@linaro/jamestunnicliffe> has joined #yocto08:40
-YoctoAutoBuilder- build #41 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at
*** g1zer0 <g1zer0!> has quit IRC08:48
*** tasslehoff <tasslehoff!~tasslehof@> has joined #yocto08:53
*** e8johan <e8johan!> has quit IRC08:53
*** g1zer0 <g1zer0!> has joined #yocto08:58
*** e8johan <e8johan!> has joined #yocto08:58
*** bingbu <bingbu!~mars@> has quit IRC09:14
-YoctoAutoBuilder- build #42 of nightly-fsl-arm-lsb is complete: Failure [failed Building Images Building Images_1 Building Images_2 Publishing Artifacts] Build details are at
*** sameo <sameo!~samuel@> has joined #yocto09:18
*** mihai <mihai!~mihai@> has joined #yocto09:26
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:34
bluelightningmorning all09:34
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto09:38
*** florian_kc is now known as florian09:39
*** zeddii_home_ <zeddii_home_!> has joined #yocto09:42
*** zeddii_home <zeddii_home!> has quit IRC09:42
*** zeddii_home_ is now known as zeddii_home09:42
*** rainerschuster <rainerschuster!> has joined #yocto09:43
*** rainerschuster <rainerschuster!> has left #yocto09:43
-YoctoAutoBuilder- build #43 of nightly-qa-systemd is complete: Failure [failed Running Sanity Tests Running Sanity Tests_2] Build details are at
-YoctoAutoBuilder- build #42 of nightly-ppc is complete: Failure [failed Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** seebs <seebs!> has quit IRC09:50
-YoctoAutoBuilder- build #44 of buildtools is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #44 of nightly-intel-gpl is complete: Failure [failed Building Images] Build details are at
*** GusBricker <GusBricker!> has quit IRC09:54
*** GusBricker <GusBricker!> has joined #yocto09:55
*** seebs <seebs!> has joined #yocto09:57
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC09:59
*** GusBricker <GusBricker!> has quit IRC10:00
*** GusBricker <GusBricker!> has joined #yocto10:01
-YoctoAutoBuilder- build #42 of nightly-fsl-ppc is complete: Failure [failed Building Images Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** drasko <drasko!> has quit IRC10:14
*** kbart <kbart!~KBart@> has quit IRC10:17
*** kbart <kbart!~KBart@> has joined #yocto10:18
*** oswin <oswin!> has joined #yocto10:18
oswinHi, does anyone use icecc with yocto ?10:19
bluelightningoswin: I think JaMa has been or at least knows people who have10:19
bluelightningactually I'd be interested to know what the performance benefits of using it are (i.e. numbers) especially with the new blacklisting10:20
oswinbluelightning, I've heard that is wasn't that advantageous, but in which case and with how many computer, I don't know...10:23
bluelightningoswin: I'd heard the same in the past, in that the overhead of sending out the compile jobs meant that there wasn't much of an improvement; however nobody has come up with any numbers recently10:24
bluelightningI have to assume that people who are using it have measured the improvement :)10:24
oswinI hope so ^^10:24
*** linu <linu!~linu@> has joined #yocto10:25
linuhi all i have been using poky with meta-atmel and when i try  to load multi gadget,it shows the following error can you tell me what is that issues10:28
*** mckoan|away is now known as mckoan10:37
mckoangood morning10:37
*** zeddii_home <zeddii_home!> has quit IRC10:37
*** GusBricker <GusBricker!> has quit IRC10:39
gagioswin: the last time i tried it with about 40 cores the benefit was perhaps getting 1/3 - 1/4 less buildtime10:39
gagioswin: but that was almost a month ago10:40
oswingagi, did you put the scheduler on the fastest computer ?10:44
gagioswin: yes, we are using icecc for almost all of our non-yocto builds in our office and it runs on a 8-core xeon server10:45
oswingagi, and what's the usual benefit ? 1/2 ?10:46
gagioswin: i think the problem is/was that many packages don't accept the parallel build10:46
*** linu <linu!~linu@> has quit IRC10:47
gagioswin: it depends on how many machines  you have, i would say > 1/210:47
oswingagi, (i mean on non yocto)10:47
oswingagi, ok good, thanks!10:47
*** JimBaxter <JimBaxter!> has joined #yocto11:00
*** belen <belen!Adium@nat/intel/x-jyiqakdgsenralyb> has joined #yocto11:07
-YoctoAutoBuilder- build #42 of nightly-x32 is complete: Success [build successful] Build details are at
*** sunfunbaby <sunfunbaby!> has quit IRC11:20
*** sunfunbaby <sunfunbaby!> has joined #yocto11:21
*** belen <belen!Adium@nat/intel/x-jyiqakdgsenralyb> has quit IRC11:33
*** mulhern <mulhern!> has joined #yocto11:39
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto11:47
*** GusBricker <GusBricker!> has joined #yocto11:49
*** gonzzor <gonzzor!> has left #yocto11:54
JaMaoswin: bluelightning: yes I don't use it personally, because I work from home, but people in office are using that11:54
JaMaoswin: bluelightning: with a lot of computers connected to icecc and very big builds it gets really useful, building qt with -j 150 is a lot faster :)11:55
*** oswin <oswin!> has quit IRC12:00
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC12:01
*** belen <belen!~Adium@> has joined #yocto12:03
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto12:04
-YoctoAutoBuilder- build #43 of minnow is complete: Success [build successful] Build details are at
bluelightningJaMa: right, with monsters like qt and webkit there ought to be some pretty big gains12:06
bluelightningJaMa: btw, among other things Scott has just documented icecc.bbclass in the manual; perhaps I should get him to add a hint or two like that as well12:07
*** belen <belen!~Adium@> has quit IRC12:08
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC12:09
*** belen <belen!Adium@nat/intel/x-jrlcwrwnucdjaqdf> has joined #yocto12:11
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto12:12
ak77I had working recipe with some compilation and installation. Then I added a single file I want to get deployed to the device ( for this extra file it claims it was isntalled but not shipped, any clues?12:13
JaMabluelightning: I have few comments, is there open bug for this or can I say them here and you'll proxy them?12:14
bluelightningJaMa: I can proxy them, but it may be better for you to email to scott directly about it (cc me if you like)12:15
bluelightningJaMa: I think he prefers srifenbark at FYI12:16
bluelightningak77: basically you need to add something appropriate to FILES so that the additional file gets picked up12:17
*** erbo <erbo!> has quit IRC12:17
bluelightningak77: and put into the appropriate package (probably the main package, so I'm guessing you want FILES_${PN} += "${base_libdir}/firmware/"  )12:18
*** drasko <drasko!> has joined #yocto12:19
*** erbo <erbo!> has joined #yocto12:22
*** Net147 <Net147!> has joined #yocto12:22
*** pidge <pidge!~eflanagan@> has quit IRC12:23
JaMabluelightning: ups already sent to, but will bounce12:24
ak77bluelightning: that did the trick.. but what added compiled file implicitly to FILES ?12:24
bluelightningak77: there's a default value for FILES for a number of standard packages in PACKAGES; these are set in meta/conf/bitbake.conf12:25
ak77bluelightning: i see. thank you.12:26
*** GusBricker <GusBricker!> has quit IRC12:27
ak77bluelightning: i have another problem with that recipe, if you can take a look... do_rootfs fails due  to bluez4 (>= 4.101) dependancy (i use bluez5), where does that dependancy come from?12:28
*** erbo <erbo!> has quit IRC12:29
*** erbo <erbo!> has joined #yocto12:43
*** jean <jean!c02401fc@gateway/web/freenode/ip.> has joined #yocto12:46
*** jean is now known as Guest236812:46
-YoctoAutoBuilder- build #44 of nightly-mips is complete: Failure [failed Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** abelloni_ is now known as abelloni12:49
*** ddalex <ddalex!~ddalex@> has quit IRC12:51
*** GusBricker <GusBricker!> has joined #yocto12:52
*** drasko <drasko!> has quit IRC12:55
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC13:00
*** sunfunbaby <sunfunbaby!> has quit IRC13:04
*** Denwid <Denwid!c2cc4226@gateway/web/freenode/ip.> has joined #yocto13:07
*** e8johan <e8johan!> has quit IRC13:07
DenwidHi everyone. I really can't figure out how to use PREMIRRORS to circumvent our firewall. The problem is git. PREMIRRORS_prepend = "git://.*/.* \n" does not work. I would like to just set protocol=http for all the git:// repos. Is this not possible?13:11
*** zeddii <zeddii!~ddez@> has quit IRC13:12
*** zeddii <zeddii!~ddez@> has joined #yocto13:13
*** _tid <_tid!> has quit IRC13:20
*** GusBricker <GusBricker!> has quit IRC13:23
*** erbo <erbo!> has quit IRC13:23
*** Guest2368 <Guest2368!c02401fc@gateway/web/freenode/ip.> has quit IRC13:25
ak77my recipe compiles .c files and has -lbluetooth, where does information which package provides this library is hold? generated?13:28
*** joeythesaint <joeythesaint!> has joined #yocto13:28
*** erbo <erbo!> has joined #yocto13:29
ak77it keeps pulling bluez4, altough i have bluez5, which provides same library (
*** e8johan <e8johan!> has joined #yocto13:30
*** _tid <_tid!> has joined #yocto13:33
bluelightningak77: well, when your application is being packaged the system will just look at what libraries it links to and then what package(s) those libraries are provided by, and set the dependencies accordingly13:33
bluelightningak77: if you have bluez4 in your sysroot (because you built it at some point before), or it's linking to bluez4 from the host, you can get problems like the one you are having13:34
*** erbo <erbo!> has quit IRC13:34
*** erbo <erbo!> has joined #yocto13:35
*** erbo <erbo!> has quit IRC13:44
*** erbo <erbo!> has joined #yocto13:46
*** sroy_ <sroy_!~sroy@2607:fad8:4:6:3e97:eff:feb5:1e2b> has joined #yocto13:48
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:56
Xzhi there13:57
Xztrying to send a patch to openembedded-core13:57
Xzusing git send-email13:57
XzHowever i'm being given a response 'the mailinglist requires people to subscribe before posting' :|13:58
XzI'm subscribed13:58
rburtonXz: your mails are not coming from the email that is subscribed13:58
rburton(my .gitconfig sets my from address)13:58
*** alex_kag <alex_kag!~alex_kag@> has quit IRC14:00
Xzrburton: I have exactly same address in git14:00
DenwidXz: use git format-patch and send the email with your email client to check if that works14:03
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC14:04
*** challinan__ <challinan__!> has quit IRC14:06
*** vicenteolivert <vicenteolivert!57c2b5c3@gateway/web/freenode/ip.> has joined #yocto14:06
*** challinan <challinan!> has joined #yocto14:07
DenwidWith yocto 1.4 there seem to be http mirrors out of the box for everything but yocto 1.5 doesn't work behind the firewall, nothing but trouble with some packages...14:08
vicenteolivertIs there a way to build only the rootfs and not the rootfs + kernel?14:10
*** erbo <erbo!> has quit IRC14:11
Xzthere must be somethig wrong with my git configration14:12
*** erbo <erbo!> has joined #yocto14:13
ak77bluelightning: i'm not linking to bluez4 from the host, where is this sysroot, and how can I rebuild it completly14:16
XzI have and sendemail.from set to my email which is subscribed (tried subscribing again - message back, that I'm already subscribed)14:17
Xzstill cannot send email from git14:17
XzI must be missing some other settings maybe?14:17
Xzgit version
*** sroy_ <sroy_!~sroy@2607:fad8:4:6:3e97:eff:feb5:1e2b> has quit IRC14:19
*** riskable <riskable!~quassel@2601:e:8c00:7e:14e5:db88:6c42:3878> has joined #yocto14:19
*** swex <swex!~swex@> has joined #yocto14:20
*** erbo <erbo!> has quit IRC14:27
*** sroy_ <sroy_!> has joined #yocto14:31
*** OlivierG_ is now known as OlivierG14:35
*** OlivierG <OlivierG!> has left #yocto14:35
*** Net147 <Net147!> has quit IRC14:38
*** walters <walters!> has joined #yocto14:50
*** SorenHolm <SorenHolm!> has quit IRC14:53
bluelightningak77: you shouldn't need to rebuild it completely; if bluez4 has been built cleaning it out would just be a matter of bitbake -c clean bluez414:59
bluelightningak77: the sysroot is at tmp/sysroots/<machinename>/14:59
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto15:06
*** fpaut is now known as fpaut_15:15
*** Leo___ <Leo___!> has joined #yocto15:15
*** fpaut_ is now known as fpaut15:16
Leo___Hi, quick question. I'm trying to compile fsl-image-gui for freescale imx53qsb, but it fails with "ERROR: Task 437 (/media/yocto/yocto/poky-dora-10.0.0/fsl-community-bsp/sources/poky/meta/recipes-qt/qt4/, do_compile) failed with exit code '1'" Any tips on where to go from here?15:18
*** kbart <kbart!~KBart@> has quit IRC15:21
bluelightningLeo___: can you pastebin the full error?15:21
Leo___blue lightning, yea of course, one second15:21
ak77bluelightning: thank  you15:22
Leo___hope this is what you need, just started out playing with all this today15:24
bluelightningLeo___: that is an odd error, I haven't seen that before15:27
Leo___bluelightning: Ah, just my luck haha. should i file a bug report somewhere?15:28
bluelightningLeo___: well, I'd suggest maybe asking about this on the meta-freescale mailing list15:28
bluelightningthe first error is definitely specific to meta-fsl-arm15:28
*** hollisb <hollisb!> has joined #yocto15:28
Leo___bluelightning: ok, will do. thank you15:29
*** e8johan <e8johan!> has quit IRC15:29
*** belen <belen!Adium@nat/intel/x-jrlcwrwnucdjaqdf> has quit IRC15:30
*** alex_kag <alex_kag!~alex_kag@> has quit IRC15:30
*** belen <belen!~Adium@> has joined #yocto15:32
*** pidge <pidge!~eflanagan@> has joined #yocto15:32
XzDenwid: I tried using email as well - the same problem15:35
*** ak77 <ak77!c12e4b04@gateway/web/freenode/ip.> has quit IRC15:40
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC15:40
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto15:40
*** Leo___ <Leo___!> has quit IRC15:49
*** Leo___ <Leo___!> has joined #yocto15:49
*** B4gder <B4gder!> has quit IRC15:50
*** weebet <weebet!> has joined #yocto15:51
*** belen <belen!~Adium@> has quit IRC15:53
weebetHello I would like to understand a little something before digging in the creation of one recipe. My custom software needs the library libpq (from postgresql 9.2 which is not yet available in yocto/open embedded) and libpqxx (which is also not available). To compile my software in bitbake system do I need to add recipe for libpqxx and postgresql or as soon as those library are available on my15:54
weebetlocal system it will compile correctly ?15:54
ndecweebet: you need recipe for your dependencies.15:55
ndecthe build won't use any 'local' libraries, without doing very dirty hacks...15:55
weebetndec : thank you . this is bad news, I tried to create recipe for postgresql but I was not able to be successfull to create the recipe.15:55
*** belen <belen!~Adium@> has joined #yocto15:56
bluelightningweebet: there is a postgresql 9.2 recipe btw:
ndeci was about to say the same thing ;-)15:56
weebetI am surprised, the last time I have looked, it was for 8.4 or something like this15:56
bluelightninglooking at the git history it was upgraded in August of this year15:57
*** Leo___ <Leo___!> has quit IRC15:57
weebetGreat :-) Thank you15:58
*** jchonig <jchonig!> has quit IRC15:58
*** g1zer0 <g1zer0!> has quit IRC16:00
*** jchonig <jchonig!> has joined #yocto16:00
weebetI would have another question, when I log onto poky, it will only take care of the 8 first character. is there any plan to solve this issue ? I have seen that there were a lot of patch to apply to solve this, but never found any howto to correct this.16:00
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC16:00
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto16:01
*** michael_e_brown_ <michael_e_brown_!> has joined #yocto16:02
*** jkridner <jkridner!> has joined #yocto16:03
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto16:03
*** davest <davest!Adium@nat/intel/x-wgyrxoginxldizvz> has quit IRC16:04
*** erbo <erbo!~erik@> has joined #yocto16:04
erboI noticed that module_strip.bbclass is empty, is there some other way to make sure kernel modules are stripped?16:05
jkridner19 degrees here. ;-)16:06
*** Zaif <Zaif!> has quit IRC16:06
kergotherbo: iirc its automatically handled by package.bbclass now, nothing you need to do16:06
kergothafaik anyway16:06
* Crofton|work curses kit kat and bluetooth headset16:07
Crofton|workah turning it on is a big help16:07
*** Jefro <Jefro!> has joined #yocto16:08
bluelightningerbo: coincidentally I'm about to send a patch to drop that empty class16:09
zibrirp: i believe i just found another bug, thanks to the verify commit on branch change. git ls-remote <url> <tag> lists both refs/tags/<tag> and remotes/head/foo/bar/<tag>. do you have any ideas on how to solve that?16:12
erbokergoth: I'll have to look through package.bbclass, because my modules are not stripped :)16:13
zibrii.e., when what i was looking for was the sha1 of refs/tags/<tag>, instead i get back the sha1 of some random branch that happens to end with the same string as the tag i was looking for.16:13
*** erbo_ <erbo_!> has joined #yocto16:14
RPzibri: hmm, that could be quite nasty :/16:14
*** mckoan is now known as mckoan|away16:14
*** erbo <erbo!~erik@> has quit IRC16:14
*** erbo_ is now known as erbo16:14
bluelightningweebet: it seems you just need to set ENCRYPT_METHOD in /etc/login.defs16:18
bluelightningI wonder if there's a good reason why we don't do that by default...16:18
*** alex_kag <alex_kag!~alex_kag@> has quit IRC16:18
weebetThank you bluelightning16:19
*** ant_work <ant_work!> has quit IRC16:20
kergothzibri: git ls-remote <url> refs/tags/<tag>16:21
kergothafaik that should work fine, no?16:21
kergothoh, i'm guessing in this case it's from srcrev, so we don't know what it's referring to?16:22
zibrikergoth: yes, indeed. but this is in the git fetcher. i'm not sure that change is fine there16:22
zibribut maybe try that first, if nothing comes out, try refs/head/<string>.16:22
zibrirefs/heads/<string> even16:23
kergothhmm yes, thats's an idea16:23
zibrinot the prettiest, i'll admit :/16:23
kergothnot many other options if the user gives us something ambiguous, other than to just fail :)16:25
vicenteolivertIs anyone else having problems with m4-native package? It always fails at configure phase for me.16:26
bluelightningweebet: actually that only applies if you have "shadow" in your image; if you're using busybox's version of login/passwd then it should be supporting >8 char passwords out of the box16:26
rburtonvicenteolivert: pastebin the problem please16:26
vicenteolivertconfigure: error: C compiler cannot create executables16:26
rburtonvicenteolivert: pastebin the config.log please :)16:26
*** sgw_ <sgw_!> has quit IRC16:29
*** sgw_ <sgw_!> has joined #yocto16:29
zibrikergoth, rp: thanks for your input! i'll try to prepare a patch and send it tomorrow16:30
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto16:31
*** JaMa <JaMa!> has quit IRC16:33
vicenteolivertrburton: Ok, it's failing because the CFLAGS I have passed. But those CFLAGS should be valid...16:33
weebetbluelightning : how to know if I use shadow / busybox ?  also, I am not using the latest repo how to checkout only the postgresql recipe ? I tried to git clone git:// but I have a remote error: acces denied or repository not exported /meta-openembedded/meta-oe/recipes-support/postgresql16:34
sgw_Folks, can someone with a redhat bugzilla account see if they can access:, we are seeing an userspace nfs readdir issue that is referenced in here possibly.16:34
yoctiBug 813070: was not found.16:34
*** eballetbo <eballetbo!> has quit IRC16:34
vicenteolivertrburton: it looks like it was compiling for i686 instead of mips.16:35
rburtonvicenteolivert: you did ask for m4-native16:35
rburtonor at least, it's building m4-native16:35
rburtonso where you specified those cflags, you need to use them for just target builds and not native16:35
bluelightningweebet: git can't be used to fetch individual files like that, but you can fetch / check out the latest branch, copy the files out (or clone the repository again in a separate directory)16:36
vicenteolivertrburton: I have specified those cflags in my local.conf16:36
vicenteolivertrburton: is not correct?16:36
bluelightningweebet: re shadow / busybox, you can do: ls -l `which passwd`16:36
-YoctoAutoBuilder- build #43 of build-appliance is complete: Failure [failed Building Images] Build details are at
rburtonvicenteolivert: extend TARGET_CFLAGS so you're not changing native CFLAGS16:37
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC16:37
weebetbluelightning : no shadow in (... PATH ...) so I uses busybox16:37
-YoctoAutoBuilder- build #44 of nightly-oecore is complete: Success [build successful] Build details are at
weebetand when I do : passwd it tells me that the password must have minimum of 5, maximum of 816:38
weebetI work with gumstix layer under danny. I guess I work with an old repo16:39
vicenteolivertrburton: TARGET_CFLAGS_append = " -mmicromips -mno-jals" , is that the right way to do it?16:39
rburtonvicenteolivert: that should work. yeah.16:40
vicenteolivertrburton: ok, thanks. I'll let you know if it works.16:40
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto16:40
michael_e_brown_I NEED STICKERS!16:40
vicenteolivertrburton: quick question. Is it possible to build only the rootfs image and not the kernel image?16:41
bluelightningweebet: if it used shadow, it would definitely say /usr/bin/passwd -> /bin/busybox (or busybox.suid)16:41
bluelightningweebet: er, I mean if it used busybox16:41
*** davest <davest!~Adium@> has joined #yocto16:43
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC16:43
weebet"/usr/bin/passwd -> /bin/tinylogin"16:44
vicenteolivertOr better..., is there a way to simply use my own ".config" file to build the kernel?16:44
bluelightningweebet: ah of course, tinylogin16:45
rburtonvicenteolivert: you can build your own kernel if you don't like the yocto kernel config thing16:46
vicenteolivertrburton: ok, but how can I avoid building the yocto kernel?16:46
rburtonvicenteolivert: i recommend getting yocto to build a kernel using your config16:47
bluelightningweebet: in danny we used tinylogin , before we used busybox's integrated version of the same16:47
bluelightningweebet: but it seems that behaved differently w.r.t encryption methods16:47
*** tasslehoff <tasslehoff!~tasslehof@> has quit IRC16:48
bluelightningweebet: to be honest I'm not sure how to fix that; you might try googling "tinylogin 8 character" or something like that16:49
weebetThank you bluelightning. I guess I will work to get the latest16:49
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto16:50
*** belen <belen!~Adium@> has quit IRC16:51
*** belen <belen!~Adium@> has joined #yocto16:51
*** fpaut is now known as fpaut_16:54
*** swex <swex!~swex@> has quit IRC16:58
*** belen <belen!~Adium@> has quit IRC17:00
-YoctoAutoBuilder- build #45 of nightly-intel-gpl is complete: Success [build successful] Build details are at
*** swex <swex!~swex@> has joined #yocto17:07
*** n01 <n01!> has quit IRC17:11
Crofton|workJefro, !17:12
michael_e_brown_OH NOES!17:12
vicenteolivertrburton: despite of using TARGET_CFLAGS_append, eglibc-initial fails anyway:
rburton"mipsel-poky-linux-gcc: error: unrecognized command line option '-mmicromips'"17:15
rburtonare you sure you're using gcc options that the gcc you're building knows about?17:15
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has quit IRC17:16
vicenteolivertrburton: -mmicromips is a valig CFLAGS for a mips gcc.17:18
*** Jefro <Jefro!> has quit IRC17:20
rburtonvicenteolivert: well, clearly not for the gcc that it's running.17:20
vicenteolivertrburton: I don't have any idea about how to fix that :S17:21
*** Jefro <Jefro!> has joined #yocto17:21
*** mr_science <mr_science!> has joined #yocto17:22
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto17:22
rburtonvicenteolivert: says otherwise17:23
rburtonvicenteolivert: i'd guess those variables are mentor/cs specific17:25
rburton(kergoth might know)17:25
kergothnot sure offhand, would have to go pester the folks in that department17:27
rburtonvicenteolivert: so i'd guess either 1) patch your gcc 2) stop using those options 3) use mentor's toolchain layer17:27
*** dlern <dlern!~dlerner@> has joined #yocto17:28
vicenteolivertI'll try removing those options first..., but I guess the board will not boot then.17:28
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto17:29
*** panda84kde <panda84kde!> has quit IRC17:30
* pidge is running the poky-contrib cleanup right now. any deleted branches will be in poky-contrib-archive17:38
*** j8 <j8!~IceChat9@> has joined #yocto17:41
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC17:43
*** florian_kc <florian_kc!> has joined #yocto17:43
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto17:43
*** roric <roric!~roric@> has quit IRC17:44
*** belen <belen!Adium@nat/intel/x-pevcembfespithnt> has joined #yocto17:52
mr_scienceokay, i see no openssh-server in oe-classic DISTRO_FEATURES17:54
mr_sciencewhat's the proper way to punt dropbear in favor of openssh?17:54
mr_sciencemoin, btw...17:54
bluelightningmr_science: OE-Classic questions should really be asked in #oe17:57
bluelightningmr_science: good morning to you also :)17:57
mr_sciencestupid default tab...17:57
kergoth... and the new fetch code explodes if you try to use a tag in SRCREV17:58
kergoththis stupid branch check is really starting to get on my nerves17:58
*** oneQubit <oneQubit!> has joined #yocto18:02
*** davest <davest!~Adium@> has quit IRC18:02
*** mihai <mihai!~mihai@> has quit IRC18:02
*** ddalex <ddalex!~ddalex@> has joined #yocto18:04
j8anybody use smart package manager?18:07
-YoctoAutoBuilder- build #44 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at
*** davest <davest!~Adium@> has joined #yocto18:11
j8i used smart to install a package. subsequent installs error out because e.g. libc6 "is already installed"18:11
*** Leo_ <Leo_!> has joined #yocto18:14
*** swex <swex!~swex@> has quit IRC18:16
bluelightningj8: that is very strange18:16
bluelightningj8: is that something that would be easy for me to reproduce here?18:17
*** munch <munch!> has joined #yocto18:17
*** sameo <sameo!~samuel@> has quit IRC18:23
j8bluelightning: i am on dylan. i installed base-files to test out a fix. that succeeded, so i tried installing packagegroup-core-boot which yielded the error18:24
bluelightningj8: hmm, packagegroup-core-boot itself should already be installed, unless you're building a highly customised image (or you're upgrading...)18:25
j8bluelightning: yea, i'm doing this because i thought the image i got didn't have any smart package data18:29
bluelightningj8: was package-management in IMAGE_FEATURES when this image was built?18:31
_tidhello :)18:31
_tidi was wondering if there was any way to include kernel modules into the ubi image ?18:31
pidgeok, poky-contrib got a first pass cleaning. more cleaning in a bit.18:32
-YoctoAutoBuilder- build #44 of nightly-x86-64 is complete: Success [build successful] Build details are at
*** davest <davest!~Adium@> has quit IRC18:35
-YoctoAutoBuilder- build #43 of nightly-x86 is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #43 of nightly-fsl-ppc is complete: Success [build successful] Build details are at
*** seebs <seebs!> has quit IRC18:39
j8bluelightning: i've got package-management in a IMAGE_FEATURES_append, so now i'm wondering if i'm doing it right18:39
bluelightningj8: with a leading space in the value?18:40
*** davest <davest!~Adium@> has joined #yocto18:41
*** n01 <n01!> has joined #yocto18:42
bluelightningj8: turning this around, if you do "smart query --installed" does it actually show the full list of packages that should be installed on the system or just the few that were installed when you installed base-files?18:43
-YoctoAutoBuilder- build #45 of nightly-mips is complete: Success [build successful] Build details are at
j8bluelightning: can't say right now because i am hacking things right now. should i be seeing a /var/lib/smart directory in the built image?18:53
bluelightningj8: you should yes18:55
*** _tid <_tid!> has quit IRC18:55
*** seebs <seebs!> has joined #yocto18:57
*** Leo_ <Leo_!> has quit IRC18:58
*** Leo_ <Leo_!> has joined #yocto19:02
-YoctoAutoBuilder- build #43 of nightly-ppc is complete: Success [build successful] Build details are at
j8bluelightning: strange, i'm not getting anything  in /var/lib/smart. should i be able to do IMAGE_FEATURES = "x11" and then IMAGE_FEATURES_append = " package-management"19:06
bluelightningj8: you should yes19:07
bluelightningj8: I'd try bitbake -e your-image | grep ^IMAGE_FEATURES=19:08
*** _tid <_tid!> has joined #yocto19:08
*** JaMa <JaMa!> has joined #yocto19:12
*** Xz <Xz!kmsywula@nat/intel/x-ndnlawdcbgfhdznk> has quit IRC19:13
j8bluelightning: IMAGE_FEATURES does have package-management19:16
-YoctoAutoBuilder- build #43 of nightly-fsl-arm is complete: Success [build successful] Build details are at
bluelightningj8: does your image recipe inherit image or core-image?19:18
j8bluelightning: core-image19:18
bluelightningj8: there isn't a line adding "remove_packaging_data_files" to ROOTFS_POSTPROCESS_COMMAND is there?19:19
*** alex_kag <alex_kag!~alex_kag@> has quit IRC19:20
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto19:20
j8bluelightning: that line ended up in my *image*.bb - is that eliminating the smart metadata?19:20
bluelightningj8: yes, it will be19:21
bluelightningj8: you need to remove that19:21
bluelightningmystery solved19:22
*** belen <belen!Adium@nat/intel/x-pevcembfespithnt> has quit IRC19:23
*** alex_kag <alex_kag!~alex_kag@> has quit IRC19:24
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto19:24
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC19:28
*** pidge <pidge!~eflanagan@> has quit IRC19:29
*** dany <dany!> has quit IRC19:33
*** dany <dany!> has joined #yocto19:34
*** mihai <mihai!~mihai@> has joined #yocto19:36
*** Leo_ <Leo_!> has quit IRC19:37
*** rainerschuster <rainerschuster!> has joined #yocto19:40
*** rainerschuster <rainerschuster!> has left #yocto19:41
*** sroy_ <sroy_!> has quit IRC19:56
*** roric <roric!> has joined #yocto19:57
*** ravic <ravic!> has joined #yocto20:06
*** ravic <ravic!> has left #yocto20:09
*** GusBricker <GusBricker!> has joined #yocto20:17
*** SorenHolm <SorenHolm!> has joined #yocto20:17
*** n01 <n01!> has quit IRC20:17
*** n01 <n01!> has joined #yocto20:23
*** davest <davest!~Adium@> has quit IRC20:24
*** davest <davest!~Adium@> has joined #yocto20:28
*** davest <davest!~Adium@> has quit IRC20:33
*** sroy_ <sroy_!> has joined #yocto20:34
*** [simar|on] <[simar|on]!> has joined #yocto20:34
*** davest <davest!~Adium@> has joined #yocto20:41
*** davest <davest!~Adium@> has quit IRC20:47
*** [simar|on] <[simar|on]!> has quit IRC20:47
*** n01 <n01!> has quit IRC20:57
*** davest <davest!~Adium@> has joined #yocto21:01
*** MDR <MDR!~mdrustad@> has joined #yocto21:06
*** Jefro <Jefro!> has quit IRC21:07
*** [simar|on] <[simar|on]!> has joined #yocto21:10
*** GusBricker <GusBricker!> has quit IRC21:14
*** GusBricker <GusBricker!> has joined #yocto21:14
*** GusBricker <GusBricker!> has quit IRC21:19
*** JimBaxter <JimBaxter!> has quit IRC21:28
*** Jefro <Jefro!> has joined #yocto21:28
*** smartin_ <smartin_!> has joined #yocto21:31
-YoctoAutoBuilder- build #43 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at
*** ant_home <ant_home!> has joined #yocto21:37
*** n01 <n01!> has joined #yocto21:43
*** bluelightning <bluelightning!> has joined #yocto21:49
*** bluelightning <bluelightning!> has quit IRC21:49
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:49
*** SorenHolm <SorenHolm!> has quit IRC21:51
*** Jefro <Jefro!> has quit IRC21:56
*** GusBricker <GusBricker!> has joined #yocto21:56
*** davest <davest!~Adium@> has quit IRC21:58
*** sroy_ <sroy_!> has quit IRC22:02
*** Jefro <Jefro!> has joined #yocto22:04
*** roric <roric!> has quit IRC22:10
*** Jefro <Jefro!> has quit IRC22:41
*** n01 <n01!> has quit IRC22:46
*** sameo <sameo!~samuel@> has joined #yocto22:57
*** Jefro <Jefro!> has joined #yocto22:59
*** bfederau <bfederau!> has quit IRC23:01
*** bfederau <bfederau!> has joined #yocto23:01
*** zeddii_home <zeddii_home!> has joined #yocto23:03
*** maharvey <maharvey!~maharvey@> has joined #yocto23:04
*** maharvey <maharvey!~maharvey@> has left #yocto23:04
*** Smitty <Smitty!55b54be1@gateway/web/freenode/ip.> has joined #yocto23:09
*** roric <roric!> has joined #yocto23:10
*** MDR <MDR!~mdrustad@> has quit IRC23:11
SmittyI'd be interested in learning more about Yocto, but I get put off by the naming that is used.  What is Yocto, Poky, sato, etc, etc..  Why are these names being chosen, and what relevance do they have to what they identify23:12
*** smartin_ <smartin_!> has quit IRC23:12
SmittyWhy is the QUick Start Guide such a jumbled mess of information23:12
SmittyShould I really feel confident that anyone other than script kiddies are involved with this project ?23:13
kergothyocto is an umbrella project which includes many things, of which poky is one. poky is its buildsystem23:13
kergothdid you not see all the major corporations which are members of yocto?23:13
kergothgo look at the website23:13
Smittywhat do you mean build system ?   You mean a replacement for unix make, or cmake ?23:13
kergothno, it's higher level than that. it builds an entire linux distribution, all the components involved, bootloader, kernel, gui, everything, giving you a filesystem/image to put on your device23:14
kergothit runs make under the hood to build individual components23:14
kergoth(among other tools)23:14
SmittySo, why is it called Poky ?23:14
kergothyocto is a metric prefix, indicating its use for small systems23:15
kergothno clue what poky originated from, personally23:15
kergothdon't know, don't care23:15
SmittyOK, so Poky is the build system, what's bitbake ?  The executable that actually operates on "the build system"23:16
SmittyIn which case, why isn't the build system called bitbake ?23:16
kergothpoky is yocto's buildsystem, it uses multiple open source components under the hood, of which bitbake is one23:18
kergoththose components existed before yocto or poky, and are used by other projects than just poky23:18
kergothi'll admit it can be confusing, but the decisions weren't made randomly and without reason23:19
SmittyOK, so let's start over.  Poky is the build system, but it uses a variety of tools to accomplish the build.  So, let's clarify what we mean by a 'build'  I regard a build as the process of a 'make' like system working through a set of makefiles and executing toolchain commands such as compile, archive, strip, link, etc.23:21
SmittySo, where does Poky and bitbake fit into that picture23:22
rburtonkergoth: poky is a sweet in japan23:24
kergothi already explained that. it builds an entire linux system for an embedded system23:24
rburton(usually transliterated to pokey, iirc)23:24
kergotha linux distribution consists of a great deal of software, go read up on redhat and the like to get an idea of what all is involved23:24
Smittybut so does make, or cmake.23:25
kergothit builds everything obeying their dependencies23:25
kergothno, they don't23:25
kergothwell, in rare cases. buildroot is a make based system which is similar, but much less flexible23:25
kergothmake is generally used to build one piece of software23:25
kergothnot the hundreds of pieces of software involved in an entire linux distribution23:25
kergothevery distro has their own high level tools for this23:25
kergoththis is no different than those, other than goals and embedded focus23:26
*** Jefro <Jefro!> has quit IRC23:27
Smittyso, Poky is the equivalent of something like 'standard' linux make menuconfig ?23:27
kergothmake menuconfig is how you configure the build of a linux kernel23:28
kergoththat's one of many components in a linux distribution23:28
kergotha kernel is just one small piece of a distro23:28
rburtonstrictly speaking Poky is a reference distribution, showing how to assemble the pieces in Yocto (bitbake, oe-core, etc) into a distribution.23:28
kergothwell put23:28
rburtonits also the distribution that Yocto does QA on23:28
rburtonbitbake is the tool that decides what to build, and how.23:29
Smittyso bitbake is like cmake23:29
rburtonoe-core is the "core" metadata, linux, glibc, gcc, etc.23:29
kergothcmake is a buildsystem used to build a single piece of software, not unlike autoconf/automake/make/etc23:30
rburtonSmitty: its not a great comparison but bitbake/oe-core == make/makefiles23:30
kergothits similar, but at a different scope23:30
kergothwhat it does is similar, in that it runs tasks, obeying inter-task dependencies23:30
kergothbut tools like make/cmake are oriented toward building individual source files. make is file-oriented23:30
SmittyCMake, by reading CMakeLists.txt (and other cmake files) can build anything from a single object file to a library, a suite of libraries, or an entire distribution.  It just depends upon how complicated you want it to be.  How is that any different from bitbake23:31
rburtonSmitty: good luck building a distribution with cmake.23:31
rburtonSmitty: maybe you can - as kergoth said, the buildroot project builds distros using mostly Makefiles23:32
kergothagain, its a matter of scope and focus. yes, its theoretically possible to build a distro with such tools, and i already pointed out one example of this, but they don't tend to scale well, nor are they as flexible23:32
kergoththe reason we started openembedded and bitbake is that make was not doing the job23:32
rburtonSmitty: the difference to anyone who isn't a random hacker looking for a pet project is that bitbake exists, and lets-build-a-distro-using-cmake doesn't.23:33
rburtonanyway, it's just a tool, move on.23:33
rburtonnext question?23:33
kergothif it doesn't meet your needs, there are plenty of alternatives, but this meets our needs, and that of many other companies. yocto is a way for those companies to work together on a solid well tested core for their distributions, so they can focus on what really differentiates them23:34
SmittyOK, fine, I can understand that.  I wouldn't want to try to build an entire distro with CMake, or make.  So, Yocto provides the infrastructure and tools for building a distro.  Poky is a reference distribution created by Yocto.23:34
rburtonthere are plenty of others: angstrom is a popular example of a distro built using yocto pieces23:36
Smittybitbake is a tool which can process 'recipes'  and construct a set of commands to compile, link, etc23:36
rburtonbuild file systems, construct package feeds, etc23:37
kergotheach recipe tells it how to build a particular piece of software. glibc, busybox, bash, whatever. they define dependencies between them, so it can build them in the right order23:38
* rburton -> bed23:38
kergothit's also capable of cross-compilation, which is an important feature23:38
*** roric <roric!> has quit IRC23:38
Smittywhat's what's the sato part of core-image-sato trying to convey ?23:39
kergothsato is a particular GUI environment. scroll down to SATO on
kergothgnome mobile based gui for embedded devices23:40
kergothone of many UIs which are used in embedded systems23:40
kergothsee also
kergoth(which was the original announcement, from ages ago)23:42
Smittyso, core-image-sato shoudl perhaps be called sato-core-image, since the image contains sato on top of core.23:43
SmittyNow, I get really confused by the quick start guide when I read this "By default, the target architecture for the build is qemux86, which produces an image that can be used in the QEMU emulator and is targeted at an IntelĀ® 32-bit based architecture"23:44
kergothit's a convention for all the core images to be named core-image-<thing>23:44
kergothminimal, base, sato, etc23:45
kergothas i mentioned, it can handle cross-compilation. that is, it targets a platform other than what you're running on23:45
kergothwhether that's a beagleboard, minnowboard, some custom dev board, or whatevewr23:45
kergoththe default config targets qemu, an emulation environment, so you can run it on your build machine under emulation23:45
SmittyWhy would I have to specify qemux86, and not just x86.  Surely the target (x86) can run in any virtual machine which can host an x86.23:46
*** agust <agust!> has quit IRC23:46
kergoththere is a generic x86 target available also. the qemu one will build a kernel configured specifically for use in qemu, with all the drivers that it emulates, and also builds the tools necessary to run the output of hte build, including qemu itself23:48
kergothand you don't have to specify it, qemux86 is default :)23:49
*** _tid <_tid!> has quit IRC23:50
Smittyhow does one target a virtual machine ?  Surely you target a real architecture like x86, ARM, whatever23:50
kergothno, you specify a specific "machine", not a generic architecture23:50
kergothas i mentioned before, it builds the entire distro, including bootloader(s) and kernel23:50
kergothwhch aren't generic23:50
kergothparticularly in embedded23:50
Smittyare you sayng that the compiler is emitting different instructions for qemu hosted x86 than for true x86 ?23:52
kergoththat's not what i said, though it could be optimizing differently sure. the main thing i said was that the kernel was configured differently, among other things23:53
Smittythere are kernel compile options for running within a virtual machine as apposed to native hardware ?23:54
kergothnot generally, no, but what drivers are enabled can be different, as qemu only emulates certain hardware23:54
SmittyOK, so really this qemux86 target is a subset of a generic x86 target I would imagine.23:55
kergothdon't really know, i've never tested the generic x86 stuff, it's a relatively recent addition. embedded tends to be quite specific, not building generic kernels that work on any system, though that's changing somewhat23:56

Generated by 2.11.0 by Marius Gedminas - find it at!