Friday, 2013-03-08

*** agust1 <agust1!> has quit IRC00:08
ftonelloevanp: ok.. thanks00:09
*** flynn378 <flynn378!~AndChat27@> has joined #yocto00:12
evanpftonello: I'd think about whether it really matters before bothering, though00:14
*** andyross <andyross!> has quit IRC00:22
*** ynezz <ynezz!> has quit IRC00:29
*** mshakeel <mshakeel!~mshakeel@> has quit IRC00:29
*** jwessel <jwessel!~jwessel@> has quit IRC00:29
*** grifter188 <grifter188!> has quit IRC00:29
*** ericben <ericben!> has quit IRC00:30
*** ericben <ericben!> has joined #yocto00:30
*** ant_home <ant_home!> has quit IRC00:34
*** jackmitchell1 <jackmitchell1!~Thunderbi@> has quit IRC00:39
*** feydrautha80 <feydrautha80!~ovidiu@> has joined #yocto00:39
*** ynezz <ynezz!> has joined #yocto00:39
*** mshakeel <mshakeel!~mshakeel@> has joined #yocto00:39
*** jwessel <jwessel!~jwessel@> has joined #yocto00:39
*** grifter188 <grifter188!> has joined #yocto00:39
*** jackmitchell <jackmitchell!~Thunderbi@> has joined #yocto00:39
*** jackmitchell <jackmitchell!~Thunderbi@> has joined #yocto00:39
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:42
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto00:46
*** blloyd_ <blloyd_!> has quit IRC00:46
feydrautha80hello guys , I'm doing something wrong and I can't understand what exactly00:53
feydrautha80i got yocto from git and is master branch00:54
feydrautha80and then I got raspberrypi meta layer00:54
feydrautha80in the rasberrypi metas there is a recipe that brings the hardware up00:54
feydrautha80( and it works in qemu )00:54
feydrautha80attempted to add python to the recipe00:55
feydrautha80IMAGE_FEATURES+= ...00:55
feydrautha80then after i build the image ... there is no python there00:55
*** eren <eren!~eren@unaffiliated/eren> has quit IRC00:56
feydrautha80if i try to make the python recipe .. it builds and work ..00:56
ftonellofeydrautha80: there is no python IMAGE_FEATURE00:57
feydrautha80this means that I understood something wrong..00:57
feydrautha80i thought if i want to add packes to the image .. i need to add them there00:58
kergothIMAGE_FEATURES is used to install groups of packages, not individual packages00:58
kergothyou want IMAGE_INSTALL00:58
kergothor, from local.conf, CORE_IMAGE_EXTRA_INSTALL00:58
ftonelloyou need to add python to CORE_IMAGE_EXTRA_INSTALL00:58
feydrautha80aww ..00:59
feydrautha80ok thanks00:59
feydrautha80this should be somewhere in the bitbake documentation right ?00:59
ftonellofeydrautha80: read the quick start and developer manuals01:00
ftonellokergoth: it seems that AUTO_LIBNAME_PKGS = "" does the job01:01
feydrautha80thank ftoneelo and thank you kergoth01:03
kergothftonello: cool, so it was debian.bbclass causing the confusion. glad to hear you found a workaround01:04
ftonellokergoth: yes.. debian.bbclass checks for this AUTO_LIBNAME_PKGS.. and by default AUTO_LIBNAME_PKGS="${PACKAGES}"01:07
davestzenlinux: ping01:07
kergothI really don't see what the problem with it is though. It doesn't hurt having it renamed, and IMAGE_INSTALL, etc can use the pre-rename names01:09
kergothbut either way01:09
*** davest <davest!Adium@nat/intel/x-neqgprlirtjwyaue> has quit IRC01:09
*** himamura <himamura!~himamura@> has joined #yocto01:10
*** sameo <sameo!~samuel@> has quit IRC01:29
feydrautha80so if i want to add python to a image :)) do i need to add "nativesdk-python" ?01:33
*** zenlinux_ <zenlinux_!~sgarman@2001:470:e962:b01:90f5:c7ac:479b:910> has joined #yocto01:34
feydrautha80where can I ask around about the recipes ?01:34
feydrautha80or read :)01:34
ftonellokergoth: becasuse its doing it wrong. its renaming the main package for something that I don't want.. im trying to split the package like the qt4 recipes does..01:37
ftonelloso I did a allow_empty to the main package, and just added RDEPENDS to it01:37
ftonelloit seems its working01:37
ftonelloactually its not a problem with debian.bbclass its just that I don't want to use it01:37
kergothfeydrautha80: you were just told, add python to CORE_IMAGE_EXTRA_INSTALL.01:38
kergothfeydrautha80: nativesdk is for sdks, not images/rootfs01:38
feydrautha80i added "python" to CORE_IMAGE_EXTRA_INSTALL01:38
feydrautha80but when i try to build the image fails because says : | Error: python not found in the base feeds (raspberrypi armv6-vfp armv6 armv5e-vfp armv5e armv5-vfp armv5 armv4 arm noarch any all).01:39
feydrautha80therefore i thought python might be called diffently01:39
kergothtry python-core instead01:40
feydrautha80aha :)01:40
kergothsee also bitbake -e python | grep \^PACKAGES=01:40
* kergoth forgot about that01:40
feydrautha80i found python with bitbake -s01:40
kergothbitbake -s shows recipes, not packages. recipes can emit any number of packages :)01:40
feydrautha80... i see .. and shouldn't "python" recipe .. contain all i need to basic python .. and even more ?01:42
kergothit does. but you dont add recipes to IMAGE_INSTALL, you add packages.01:42
kergothpython is broken up into highly granular packages so we can keep images small01:42
kergothso you can add just the packages/modules you want01:43
kergothrather than the whole standard library01:43
feydrautha80so .. if i would need aaalll python .. i should add the packed with everythong to IMAGE_INSTALL01:44
*** kmacleod <kmacleod!> has quit IRC01:44
feydrautha80if i want only the core .. i should add python-core to CORE_IMAGE_EXTRA_INSTALL01:44
kergothi can't recall offhand if there's a meta-package to install all the individual python packages or not. check the bitbake -e command i gave, and also check for packagegroup- recipes01:45
feydrautha80i'll do that :) can't for the moment because the build dir is locked01:45
feydrautha80(building )01:46
*** kmacleod <kmacleod!> has joined #yocto01:47
*** scot_ <scot_!> has quit IRC01:49
*** zenlinux_ <zenlinux_!~sgarman@2001:470:e962:b01:90f5:c7ac:479b:910> has quit IRC01:52
* kergoth nods01:53
feydrautha80a wait .. tasks have been renamed packages01:55
*** zenlinux_ <zenlinux_!> has joined #yocto01:56
kergothtasks were renamed to packagegroups, yes01:57
*** andyross <andyross!> has joined #yocto01:59
*** andyross <andyross!> has quit IRC02:05
feydrautha80hey :) it finished .. ( with python-core in CORE_IMAGE_EXTRA_INSTALL )02:25
feydrautha80thank your sir ..02:25
*** feydrautha80 <feydrautha80!~ovidiu@> has quit IRC02:26
*** ndec <ndec!~ndec@> has quit IRC02:52
*** ndec <ndec!~ndec@> has joined #yocto02:53
*** ccssnet <ccssnet!~ccssnet@> has quit IRC03:00
*** ccssnet <ccssnet!~ccssnet@> has joined #yocto03:19
*** andyross <andyross!> has joined #yocto03:52
-yocto-ab-bot- build #249 of nightly-meta-intel is complete: Exception [exception interrupted] Build details are at
*** thaytan <thaytan!> has quit IRC05:10
*** zenlinux_ <zenlinux_!> has quit IRC05:14
*** agust <agust!> has joined #yocto05:22
*** himamura <himamura!~himamura@> has quit IRC05:43
*** himamura <himamura!~himamura@> has joined #yocto05:43
*** andyross <andyross!> has quit IRC06:02
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC06:10
*** oe-core_ <oe-core_!cbf79598@gateway/web/freenode/ip.> has joined #yocto06:15
*** mebrown <mebrown!> has quit IRC06:37
*** thaytan <thaytan!> has joined #yocto06:38
*** mebrown <mebrown!> has joined #yocto06:39
*** erbo_ <erbo_!> has quit IRC06:41
*** erbo <erbo!> has joined #yocto06:44
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto06:50
*** tor <tor!> has joined #yocto07:04
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC07:09
*** ka6sox is now known as ka6sox-away07:13
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto07:15
*** sgw1 <sgw1!> has quit IRC07:23
*** eballetbo <eballetbo!~eballetbo@> has joined #yocto07:28
*** Zagor <Zagor!> has joined #yocto07:34
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto07:34
*** sgw1 <sgw1!> has joined #yocto07:34
*** plfiorini <plfiorini!> has quit IRC07:50
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC07:54
*** zeeblex <zeeblex!~zeeblex@> has quit IRC07:57
*** erbo <erbo!> has quit IRC07:58
*** erbo <erbo!> has joined #yocto07:58
*** sgw1 <sgw1!> has quit IRC08:00
*** tor <tor!> has quit IRC08:02
*** slaine <slaine!~slaine@> has joined #yocto08:03
*** tor <tor!> has joined #yocto08:06
*** elmi82 <elmi82!> has joined #yocto08:14
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto08:15
*** bogdanm <bogdanm!~bogdanm@> has joined #yocto08:25
*** ant_work <ant_work!> has joined #yocto08:39
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC08:40
*** Net147 <Net147!> has joined #yocto08:42
*** Jin|away <Jin|away!> has joined #yocto08:50
*** Jin|away is now known as Jin^eLD08:51
*** _Lucretia__ <_Lucretia__!> has quit IRC09:18
*** roric <roric!> has joined #yocto09:19
*** jbaxter <jbaxter!> has joined #yocto09:27
*** sameo <sameo!~samuel@> has joined #yocto09:29
*** mckoan|away is now known as mckoan09:29
mckoangood morning09:30
*** Corneliu <Corneliu!c0c6972b@gateway/web/freenode/ip.> has joined #yocto09:32
*** tonghuix <tonghuix!~tonghuix@> has joined #yocto09:38
*** panda84kde <panda84kde!> has joined #yocto09:40
oe-core_ what are the options to givee to cross-compile openssl09:44
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto09:44
*** florian_kc is now known as florian09:44
*** himamura <himamura!~himamura@> has quit IRC09:51
panda84kdeoe-core_: hi. Do you have poky toolchain installed?09:54
oe-core_no i'm using oe-core toolchain itself09:54
oe-core_but i want openssl to build for qemux8609:55
oe-core_i'm not cloning the code but using my code09:55
panda84kdeMmm. Are you using Yocto?09:56
oe-core_no oe-core build system09:59
*** belen <belen!Adium@nat/intel/x-qbqttqfowgnrinwb> has joined #yocto09:59
*** imolit <imolit!edwardd@nat/axis/x-hvrdmtgcbhzetxsl> has joined #yocto10:00
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC10:00
oe-core_panda84kde: do u have any idea?10:01
panda84kdeI've got some experience with but don't know at what you're referring to10:03
rburtonoe-core_: oe-core is part of yocto10:03
oe-core_when i'm building opensssl, first it builds native, there it configures for native os(x86-64-linux mine), during that it gives compilation failure10:05
panda84kdeoe-core_: to sum it up: if you want to build outside Yocto build system you should use the sdk.10:05
oe-core_saying     ../ undefined reference to `mod_exp_512'10:05
rburtonoe-core_: what version of oe-core/bitbake?10:05
rburtonhm why is it building a native openssl?10:06
oe-core_ BBCLASSEXTEND = native option is specified in bb file10:09
oe-core_rpm-native has dependency on openssl-native10:10
oe-core_even if it is building native no issue, but it is giving compilation error10:11
rburtonah, rpm is pulling it in, fine.10:11
rburtonso what version of oe-core?10:11
oe-core_whatersion of oe-core? i did not get u?10:13
oe-core_why it is giving compilation error?10:15
rburtonyes, what version of oe-core10:17
rburtoni'm trying to find out what you're building10:17
oe-core_i'm trying to build openssl in oe-core(build system) but i'm not cloning the code10:19
oe-core_whose path is specified in SRC_URI because i want to build with the code which i have10:20
oe-core_there when i'm building i get compilation error  as specified above10:20
rburtonyou're swapping the oe-core source for your own openssl source tree?10:22
rburtonare you also ensuring all those patches we apply are being applied?10:23
rburtonif you've just got a new feature or something, it's best to use a patch10:24
rburtonbut i can't really help you with compilation of sources that are not part of oe, or i can't see10:24
oe-core_even after applying all the patches its failing10:24
rburtondoes the proper source uri build fine?  if that does, then it's your changes that are breaking it.10:26
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC10:27
oe-core_so u tell there might be problem with the changes in the source?10:28
*** bluelightning <bluelightning!~paul@> has joined #yocto10:28
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:28
rburtoni'm saying you should verify that the sources urls as we provide them work before trying your modifications10:29
rburtonif a pristine oe-core doesn't build, then someone can help10:29
oe-core_ya its building file10:29
rburtonso it's your changes that are breaking the compile in some form10:30
*** tonghuix <tonghuix!~tonghuix@> has quit IRC10:32
oe-core_k thanks i'll check10:33
*** EsbenH <EsbenH!> has joined #yocto10:33
OlivierGrburton:Hi Ross, could you please have a look at the following changes in neard recipe ? and Does it make sense to you ?10:40
rburtonOlivierG: yes, that10:41
rburtonwhy do you need   oe_runmake DESTDIR=${D} libexecdir=${libexecdir} install?10:41
rburtonsurely that's implied10:41
rburtonas we've already passed libexecdir at configure time10:42
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto10:42
OlivierGbecause libdirexec in Yocto adds /usr/lib/${BPN} as mine, in neard, refers to /usr/lib...10:44
*** pirut <pirut!~Pirut@> has joined #yocto10:44
OlivierG"refers to /usr/lib/nfc" ;)10:45
rburtonyou shoud fix neard10:47
OlivierG;)... well...we had so many discussion with Marcel and Sameo about this point...10:48
rburtonsameo: sounds like you're doing it wrong :)10:49
rburtonwhat's wrong with just installing into libexecdir, which defaults to /usr/libexec i think still, but increasingly is being re-set to $libdir/$packagename10:50
OlivierGhe is not here (back in few minutes)... but we discussed about this issue this morning...10:50
rburtonOlivierG: is he coming to osts?10:50
rburtoni'll throw him into the hot tub clothed unless he sorts this out.10:51
OlivierGgood luck ;)10:51
rburtonyeah i may need a team to assist me10:51
OlivierGbtw, the idea behind all these changes (according to Marcel) is to have the daemons path as /usr/lib/{package} ...10:54
rburtonthat's a packaging choice10:54
rburtonso he's Wrong.10:54
rburtoni won't throw marcel in the hot tub though10:55
OlivierGO:-) so am i....10:55
sameorburton: Hey...So what's wrong with @libexecdir@/nfc ?10:57
rburtonwell, most sane distributions are moving to --libexecdir=/usr/lib/@package@10:57
rburtonso you'll be double-nesting10:57
sameoright, which is why we're overriding poky's install for neard.10:58
bluelightningmorning all11:02
sameorburton: According to the GNU standards: The definition of ‘libexecdir’ is the same for all packages, so you should install your data in a subdirectory thereof."11:03
sameoSo we just do that from the neard Makefile directly.11:04
*** roric <roric!> has quit IRC11:07
rburtonsameo: iirc, FHS disagrees with you11:09
rburtonwell, FHS says don't use libexec11:10
sameorburton: I think they do:
sameorburton: But basically FHS says you can add a subdir to libexec for your program, it doesn't say it must be pkgname11:11
rburtonso as more and more distros move away from libexec, FHS approves it.  epic.11:12
*** mihai <mihai!~mihai@> has joined #yocto11:12
sameoheh :)11:12
sameoalthough more and more distros are moving to /usr/lib/@package@ for libexecdir, this is not something we can take for granted according to the GNU and FHS folks.11:14
sameoI like osts hot tub btw.11:16
sameoJust not clothed though...11:17
*** Net147 <Net147!> has quit IRC11:24
*** Net147 <Net147!> has joined #yocto11:25
*** niteshnarayanlal <niteshnarayanlal!~nitesh@fedora/niteshnarayanlal> has joined #yocto11:36
*** araujo <araujo!~araujo@gentoo/developer/araujo> has quit IRC11:39
*** niteshnarayanlal <niteshnarayanlal!~nitesh@fedora/niteshnarayanlal> has left #yocto11:47
*** niteshnarayanlal <niteshnarayanlal!~nitesh@fedora/niteshnarayanlal> has joined #yocto11:49
niteshnarayanlalhi I was using tcpdump recipe from oe on github but the url mention there seems to be unavailable so I replaced it with another but now its not able to parse11:50
niteshnarayanlalits done thanks anyways :)12:02
*** niteshnarayanlal <niteshnarayanlal!~nitesh@fedora/niteshnarayanlal> has left #yocto12:02
*** mihai <mihai!~mihai@> has quit IRC12:03
*** flynn378 <flynn378!~AndChat27@> has quit IRC12:20
*** lh <lh!~lhawthor@osuosl/staff/lh> has quit IRC12:24
*** roric <roric!> has joined #yocto12:29
*** lh <lh!~lhawthor@osuosl/staff/lh> has joined #yocto12:36
*** oe-core_ <oe-core_!cbf79598@gateway/web/freenode/ip.> has quit IRC12:42
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto12:48
*** belen1 <belen1!~Adium@> has joined #yocto12:59
*** belen <belen!Adium@nat/intel/x-qbqttqfowgnrinwb> has quit IRC13:01
*** markos_ <markos_!> has quit IRC13:01
*** OlivierG <OlivierG!> has left #yocto13:23
*** scot_ <scot_!> has joined #yocto13:27
*** abesis-dev <abesis-dev!~abesis@> has joined #yocto13:35
abesis-devany help for yocto-bsp script around ?13:35
*** Net147 <Net147!> has quit IRC13:38
*** sakoman <sakoman!> has quit IRC13:48
*** mihai <mihai!~mihai@> has joined #yocto13:49
*** sakoman <sakoman!> has joined #yocto13:50
*** walters <walters!> has joined #yocto14:02
*** eballetbo <eballetbo!~eballetbo@> has quit IRC14:04
*** mihai <mihai!~mihai@> has quit IRC14:04
waynrhowdy folks, i have set "PREFERRED_PROVIDER_virtual/kernel = "linux-emac" in my machine configuration file but yocto still gives me linux-dummy whenever I build using 'bitbake -c build virtual/kernel' (this is also after running 'cleanall' for the same package)14:05
waynrwe have a custom kernel version driven by the requirement that it be compatible with Xenomai i-pipe patch14:06
bluelightningwaynr: perhaps that value is being overridden somewhere else?14:06
bluelightningwhat does this report: bitbake -e | grep PREFERRED_PROVIDER_virtual/kernel14:07
waynrhmm if something were wrong with the recipe that i wrote or if the recipe file weren't found shouldn't that cause an error?14:09
*** belen1 <belen1!~Adium@> has quit IRC14:10
bluelightningwaynr: if it was skipped I think it might (e.g. if COMPATIBLE_MACHINE / COMPATIBLE_HOST were not set correctly in the linux-emac recipe)14:11
bluelightningif the recipe wasn't available at all you would get a warning14:11
waynrhmm the build attempt does indicate 4 warnings, only 3 of which stuck on the bitbake console output14:12
waynrah nevermind, the fourth warning is "linux-dummy: No generic license file exists..."14:14
*** belen <belen!~Adium@> has joined #yocto14:16
waynrhmm, I don't see COMPATIBLE_HOST in the yocto documentation, what is that for?14:16
waynrmaybe my bb file patterns are incorrect for this layer14:18
bluelightningwaynr: COMPATIBLE_HOST is similar, it just matches on the full host string e.g. i686-linux14:27
*** bogdanm <bogdanm!~bogdanm@> has quit IRC14:31
waynrokay. looks like my bsp layer's BBFILES was set incorrectly...fixed now, but still not catching that recipe14:31
bluelightningso does bitbake linux-emac work?14:31
waynrnothing PROVIDES linux-emac14:32
waynrmight indicate my problem14:32
bluelightningright, so it's not even seeing the recipe14:37
bluelightningso you still have a problem with your BBFILES14:37
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto14:38
waynrwell I do see the directory in which this bitbake recipe is found in the 'bitbake -e | grep BBFILES'14:38
waynr(I fixed the layer.conf for this bsp (maybe), previously its recipes were not found when running that command)14:39
bluelightningjust to double check, what is the BBFILES line in the layer's layer.conf, and what is the path to the recipe?14:41
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC14:42
waynrokay BBFILES had ${LAYERDIR}/common/recipes-*/*/*.bb but the recipe was in ${LAYERDIR}/recipes-kernel/linux/linux-emac.bb14:43
bluelightningah right yes that would do it14:43
waynrstarting to get messages useful for debugging the actual kernel recipe now14:43
waynrthanks for the help bluelightning :)14:44
bluelightningno worries14:44
*** smartin <smartin!> has quit IRC14:50
*** lh <lh!~lhawthor@osuosl/staff/lh> has quit IRC14:52
*** smartin <smartin!> has joined #yocto14:55
mckoanbluelightning: does exixt a doc explaining how does Yocto branch releases works? (1.3_M5, 1.4_M3, ...)15:09
*** blitz00 <blitz00!~stefans@> has joined #yocto15:12
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto15:12
*** rcw <rcw!~rwoolley@> has joined #yocto15:13
khemmckoan: those are interim release milestones when working towards a release15:13
khemmckoan: e.g. 1.4_M4 is milestone 4 towards 1.4 release15:14
khemsomething equivalent to kernel RC1...15:14
rburtontheres lot of stuff with the schedule and milestone plans on the wiki15:15
khemsystemd 198 is booting here ...15:15
khemrburton: hi15:15
khemrburton: have hashed out the systemd plan to address the meta-systemd concerns yet ?15:15
bluelightningrburton: parts of the wiki are quite out of date though :(15:16
mckoankhem: I have this doubt because usually I use oe-core with origin/master but yocto with danny15:18
rburtonmckoan: do you mean poky with danny?15:18
mckoankhem: makes it sense to work with yocto origin/master too?15:18
rburtonkhem: going to send a rfc series today, i've got hybrid builds working.  annoyingly didn't get to finish it before i go to a conference for a week15:19
khemmckoan: I see why not15:19
khemmckoan: I work with origin/master on yocto/poky15:19
kergothmckoan: poky is just oe-core+meta-yocto+otherbits. using poky with one branch and oe-core with another branch, when one encompasses the other, doesn't make a great deal of sense :)15:20
mckoankhem: hmmm actually I don't understand why I am afraid of this :-) I'll switch to that too15:21
mckoankergoth: BTW I'm using two separate trees the Poky(yocto) way and the raw oe-core way15:23
mckoanwith 2 different builds15:23
kergothI figured, but I'm confused about the issue. You're basically already building poky master if you're bulding oe-core master, all that's missing is meta-yocto & friends15:23
kergothso there's no real reason for worry15:23
mckoankergoth: in fact I was interested to experiment master meta-yocto & friends15:24
* khem off to a F2F15:24
mckoankhem: thx15:24
kergothI'd be more worried about using bleeding edge core classes than a machine .conf ;)15:25
kergothbut fair enough15:25
*** jstashluk <jstashluk!~jstashluk@gateway/tor-sasl/jstashluk> has joined #yocto15:27
rburtonkhem: basically with this branch if you activate both systemd and sysvinit features you'll be able to pick the init manager at image time.15:30
rburtonyour sysvinit one will likely pull in libsystemd-login, but that's a tiny dep.15:31
jstashlukI run into the following when my image recipe does do_rootfs:15:33
jstashluk| Computing transaction...error: Can't install seemore-image-plugin-meta-0.1-r0@armv7a_vfp_neon: no package provides seemore-image-plugin-glib15:33
jstashlukIt seems to pick a random gstreamer plugin to quit on each time i re-run it.  Has anyone else run into something like this?15:34
rburtoni wouldn't be worried about the ordering of the errors15:35
*** mihai <mihai!~mihai@> has joined #yocto15:40
*** Corneliu <Corneliu!c0c6972b@gateway/web/freenode/ip.> has quit IRC15:45
*** michael_e_brown <michael_e_brown!~michaeleb@> has joined #yocto15:47
*** elmi82 <elmi82!> has quit IRC15:48
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC15:56
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC15:56
*** andyross <andyross!> has joined #yocto15:59
*** davest <davest!~Adium@> has joined #yocto16:00
*** mihai <mihai!~mihai@> has quit IRC16:04
*** kmacleod <kmacleod!> has quit IRC16:06
*** kmacleod <kmacleod!> has joined #yocto16:11
*** lh <lh!~lhawthor@osuosl/staff/lh> has joined #yocto16:16
*** zenlinux_ <zenlinux_!> has joined #yocto16:19
*** imolit <imolit!edwardd@nat/axis/x-hvrdmtgcbhzetxsl> has quit IRC16:20
*** tor <tor!> has quit IRC16:21
JYDawg_(good afternoon|goede middag)16:30
*** JYDawg_ is now known as JYDawg16:30
JYDawgwhen I try to compile a package I get this error: libtool: link: cannot determine absolute directory name of `=/usr/lib64'16:31
JYDawgthe intarwebs has little if any usefull info. Any ideas16:32
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC16:32
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto16:33
*** belen <belen!Adium@nat/intel/x-pmkhxzweguvwuglj> has joined #yocto16:36
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto16:39
*** jackmitchell <jackmitchell!~Thunderbi@> has quit IRC16:43
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC16:45
*** mckoan is now known as mckoan|away16:46
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto16:49
*** belen <belen!Adium@nat/intel/x-pmkhxzweguvwuglj> has quit IRC16:52
*** belen <belen!Adium@nat/intel/x-rktifjrqhjhdyofd> has joined #yocto16:52
*** phantoneD <phantoneD!> has quit IRC16:53
*** hollisb <hollisb!> has joined #yocto16:53
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC16:55
*** phantoxeD <phantoxeD!> has joined #yocto16:56
*** hsychla <hsychla!54b363cb@gateway/web/freenode/ip.> has joined #yocto17:01
hsychlahello helpfull yocto-people!17:01
*** Jin^eLD is now known as Jin|away17:02
*** zenlinux_ <zenlinux_!> has quit IRC17:02
hsychlaI added a new layer including conf/distro/<mylayer>.conf, then changed "DISTRO", "DISTRO_NAME" etc. but when I boot the built image, it always tells me the old name (from the distro.conf I copied and changed)... What do I have to change so my image uses the new name?17:03
*** dlewin <dlewin!~davidl@> has quit IRC17:05
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC17:07
*** hsychla <hsychla!54b363cb@gateway/web/freenode/ip.> has quit IRC17:25
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto17:25
*** ant_work <ant_work!> has quit IRC17:26
*** sameo <sameo!~samuel@> has quit IRC17:27
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has quit IRC17:27
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC17:29
*** panda84kde <panda84kde!> has quit IRC17:34
*** mihai <mihai!~mihai@> has joined #yocto17:34
*** francois99 <francois99!~francois9@> has quit IRC17:35
xxiaowhy are there many yocto kernel git repo instead of one with difference branches?17:39
*** ka6sox-away is now known as ka6sox17:41
zeddiixxiao, check the kernel architecture docs, but it's due to transient sets of features over time. just like linux-next, linux-stable, etc, but with more topic branches. you can't maintain a clean set of series that transition to mainline and encompass hundreds of commits over time, unless you can drop them completely and regerate/stack them clean each time.17:41
xxiaosomehow i feel yocto devel is much more complicated than debian...17:46
* zeddii shrugs17:46
zeddiithey are different use cases.17:46
bluelightningxxiao: there are other options for building the kernel if you feel that linux-yocto is more than you need17:48
zeddiiexactly. people can use what they want. linux-yocto-custom, completely custom, etc.17:48
xxiaoneed add a few recipes, kernel patches, external modules to yocto, the document is overwheleming to say the least :)17:50
zeddiiwhich one ? don't read the kernel architecture document as a start.17:50
bluelightningxxiao: we're happy to take suggestions if you have concrete ones17:50
zeddiithere's a new kernel one for 1.4, hands on labs, quickstart guides that are simple enough.17:50
bluelightningright, the labs get good feedback as far as I've seen17:51
zeddiiat the basic level, exactly what you know about patching any package with bitbake/oe-core/yocto works exactly the same way for the kernel.17:51
xxiaoi need add scst to yocto, which itself is a few modules, scripts, and also need patch the kernel17:52
zeddiiit can just grow to suit advanced needs and the chaos that can be vendor patches, upstream releases, out of tree serieris, etc.17:52
xxiaoand some user spaces program to admin it17:52
zeddiixxiao: do you know how to do the userspace parts already ? and the startup scritps ? if so, you have most of the knowledge that you need.17:52
xxiaoi have it working with yocto, just not the 'right' way, i.e. not built with recipes etc, it's done in a hackish way and now i want to clean it up17:53
zeddiithat's all kernel.17:54
zeddiibut you also need to read the other yocto docs for userspace/recipes/packaging, the concepts are the same.17:54
xxiaothanks, yeah...quite some reading to do17:55
zeddiiit gets easier, once the basic concepts become clear.17:56
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:02
*** smartin <smartin!> has quit IRC18:05
*** belen <belen!Adium@nat/intel/x-rktifjrqhjhdyofd> has quit IRC18:09
*** roric <roric!> has quit IRC18:11
*** slaine <slaine!~slaine@> has quit IRC18:15
*** hsychla <hsychla!54b363cb@gateway/web/freenode/ip.> has joined #yocto18:19
hsychlamhh... I wonder if anybody answered my question after my PC crashed... ?18:20
*** scot_ <scot_!> has quit IRC18:20
*** scot_ <scot_!> has joined #yocto18:20
evanphsychla: where exactly are you seeing the old $DISTRO value?18:26
*** plfiorini <plfiorini!> has joined #yocto18:35
*** pidge <pidge!> has joined #yocto18:55
hsychlaevanp: when booting the qemu image. but I got it now, was a stupid mistake after all. did not change the distro parameter in local.conf... but thanks for taking your time!18:57
*** hsychla <hsychla!54b363cb@gateway/web/freenode/ip.> has quit IRC19:01
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has joined #yocto19:07
*** smartin <smartin!> has joined #yocto19:18
*** sh4rm4 <sh4rm4!~sh4rm@gateway/tor-sasl/sh4rm4> has quit IRC19:19
*** paw <paw!> has joined #yocto19:23
*** sh4rm4 <sh4rm4!~sh4rm@gateway/tor-sasl/sh4rm4> has joined #yocto19:24
pawI have a recipe that under certain circumstances may want to add its multilib variant into the final image, I've been trying to do this by trying to append to RRECOMMENDS_${BPN} in my __anonymous() function but it doesn't work. what's the recommended way of doing this?19:26
khemoff late I am seeing hangs when building the final image on poky master19:34
khemit uses systemd19:34
khembut I am just seeing it since couple of days19:34
evanppaw: rather than appending, I'd probably stick a variable reference directly in RRECOMMENDS_${BPN} and then arrange for that variables value to be empty or the list of additional packages19:37
evanppaw: a lot of the task- (v1.3) / packagegroup- (v1.4) recipes do that sort of thing. e.g., look at how FEATURES works19:38
waynri am getting "ERROR: ExpansionError during parsing /opt/ Failure expanding variable do_patch: ExpansionError: Failure expanding variable do_patch, expression was    cd /opt/....19:41
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto19:42
waynris do_patch a template string variable that gets expanded with certain other variables made available somewhere long the recipe? and if so, does this error indicate that I am missing a variable necessary to complete the expansion?19:42
*** feydrautha80 <feydrautha80!~ovidiu@> has joined #yocto19:43
rburtonwaynr: why are you overriding do_patch?19:45
rburtonit's rare to need to do that19:45
waynri'm not doing it on purpose19:45
rburtonwhere's "cd /opt" coming from then?19:46
waynrthat's part of the error output19:46
rburtondo_patch will apply the patches listed in src_uri19:46
rburtonso maybe you've got a messed up src_uri statement19:46
waynrthat is possible19:46
waynri don't have any patches lsted in src_uri19:47
waynrjust a defconfig and a git repository19:47
rburtonwaynr: sounds like you need to share your recipe ;)19:47
*** markos_ <markos_!> has joined #yocto19:47
rburton(yes, the functions are for some time plain text, which are then parsed as python)19:47
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC19:49
*** kmacleod <kmacleod!> has quit IRC19:49
waynrrburton: that is probably a good idea...I am kinda just working in the dark copying existing recipes and making changes necessary to pull source from a git repository that i run19:50
*** kmacleod <kmacleod!> has joined #yocto19:52
*** rcw <rcw!~rwoolley@> has left #yocto19:57
*** zeddii <zeddii!~ddez@> has quit IRC20:10
*** eren <eren!~eren@unaffiliated/eren> has quit IRC20:30
*** _Lucretia_ <_Lucretia_!~munkee@pdpc/supporter/active/lucretia> has joined #yocto20:31
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto20:38
rburtoncan anyone remember when openzaurus was formed?20:42
rburtontrying to put a date on "key components of yocto are X years old"20:42
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC20:45
Crofton|workI think we have been using 200420:47
Crofton|workDomain Name:OPENZAURUS.ORG20:48
Crofton|workCreated On:05-Feb-2002 17:07:13 UTC20:48
rburtonthat's a good idea :)20:48
Crofton|workDomain Name:OPENEMBEDDED.ORG20:48
Crofton|workCreated On:21-Jan-2003 23:58:22 UTC20:48
Crofton|work10 years old is good number20:48
rburtonthanks :)20:48
Crofton|worksomeone at ELC made the remark The Yocto Project hadn't been around long enough to judge20:49
Crofton|workI found that "amusing"20:49
*** W1N9Zr1229 is now known as W1N9Zr020:54
*** mihai <mihai!~mihai@> has quit IRC21:00
*** lh <lh!~lhawthor@osuosl/staff/lh> has quit IRC21:04
Crofton|workI have eclipse making an arm binary of hell world with the toolchain from populate sdk21:05
Crofton|workany hints on how to run this binary on the target hw from eclipse?21:05
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has quit IRC21:12
*** jbaxter <jbaxter!> has quit IRC21:17
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has joined #yocto21:24
khemCrofton|work: you are almost there21:26
khemCrofton|work: if you can compile an app half the battle is won21:26
*** markos_ <markos_!> has quit IRC21:30
*** roric <roric!> has joined #yocto21:33
*** paw <paw!> has quit IRC21:34
Crofton|workhello,world ...21:35
*** davest <davest!~Adium@> has quit IRC21:39
*** bluelightning <bluelightning!> has joined #yocto21:42
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:42
*** nitink <nitink!~nitink@> has quit IRC21:46
*** nitink <nitink!~nitink@> has joined #yocto21:46
Crofton|workI think I ran it. There are way too many things to chose frmo. Seriously confusing21:51
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto21:51
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has quit IRC21:52
*** yocto-ab-bot <yocto-ab-bot!> has quit IRC21:56
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has joined #yocto21:56
*** ant_home <ant_home!> has joined #yocto21:59
*** scot_ <scot_!> has quit IRC22:01
*** scot_ <scot_!> has joined #yocto22:01
*** kmacleod <kmacleod!> has quit IRC22:03
*** kmacleod <kmacleod!> has joined #yocto22:05
*** otavio_ is now known as otavio22:08
*** yocto-ab-bot <yocto-ab-bot!> has joined #yocto22:09
*** Jefro <Jefro!> has joined #yocto22:11
*** wmat_ is now known as wmat22:19
*** darknighte_afk is now known as darknighte22:25
*** andyross <andyross!> has quit IRC22:31
*** abelloni_ <abelloni_!> has joined #yocto22:49
*** darknighte is now known as darknighte_afk22:49
*** abelloni <abelloni!> has quit IRC22:50
*** darknighte_afk <darknighte_afk!~darknight@pdpc/supporter/professional/darknighte> has quit IRC22:54
*** abelloni <abelloni!> has joined #yocto22:55
*** smartin <smartin!> has quit IRC23:05
*** flynn378 <flynn378!~AndChat27@> has joined #yocto23:13
*** plfiorini <plfiorini!> has quit IRC23:35
*** nitink <nitink!~nitink@> has quit IRC23:51
*** nitink <nitink!~nitink@> has joined #yocto23:52
*** andyross <andyross!> has joined #yocto23:55

Generated by 2.11.0 by Marius Gedminas - find it at!