Friday, 2013-08-30

*** davest <davest!~Adium@> has quit IRC00:05
*** Guest89792 <Guest89792!> has quit IRC00:14
*** tomz <tomz!> has joined #yocto00:14
*** _julian_ <_julian_!> has joined #yocto00:15
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC00:16
*** _julian <_julian!> has quit IRC00:19
*** sameo <sameo!~samuel@> has quit IRC00:21
*** wmat_ is now known as wmat00:22
*** cetola <cetola!> has quit IRC00:43
*** scot_ <scot_!~scot@> has quit IRC00:49
*** embeddedZ <embeddedZ!> has quit IRC00:52
*** Jefro <Jefro!> has quit IRC01:02
*** zenlinux <zenlinux!> has joined #yocto01:08
*** W1N9Zr0 <W1N9Zr0!> has quit IRC01:24
*** W1N9Zr0 <W1N9Zr0!> has joined #yocto01:27
*** Satrukaan <Satrukaan!> has joined #yocto01:30
*** Jefro <Jefro!> has joined #yocto01:47
*** Jefro <Jefro!> has quit IRC01:57
*** silviof1 <silviof1!~silviof@unaffiliated/silviof> has joined #yocto02:01
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC02:04
*** [simar|on] <[simar|on]!> has joined #yocto02:09
*** mitz__ <mitz__!> has quit IRC02:12
*** mitz_ <mitz_!> has joined #yocto02:12
*** brm <brm!da653619@gateway/web/freenode/ip.> has quit IRC02:15
*** davest <davest!~Adium@> has joined #yocto02:19
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto02:31
*** scot_ <scot_!~scot@> has joined #yocto02:35
*** michael_e_brown_ <michael_e_brown_!> has quit IRC02:35
*** mebrown <mebrown!> has joined #yocto02:36
*** GunsNRose <GunsNRose!~GunsNRose@> has joined #yocto03:09
otavio has wrong sabresd directory; it is missing a /q/ ;)03:15
*** Satrukaan <Satrukaan!> has quit IRC03:15
*** [simar|on] <[simar|on]!> has quit IRC03:15
*** [simar|on] <[simar|on]!> has joined #yocto03:19
*** andyross <andyross!> has joined #yocto03:19
*** [simar|on] <[simar|on]!> has joined #yocto03:20
*** amarsman <amarsman!> has quit IRC03:28
*** amarsman <amarsman!> has joined #yocto03:30
*** Anusko <Anusko!~anusko@> has quit IRC03:33
*** davest <davest!~Adium@> has quit IRC03:35
*** davest <davest!~Adium@> has joined #yocto03:35
*** andyross <andyross!> has quit IRC03:36
*** andyross <andyross!> has joined #yocto03:36
*** musdem <musdem!> has quit IRC03:37
*** GunsNRose <GunsNRose!~GunsNRose@> has quit IRC03:53
*** davest <davest!~Adium@> has quit IRC04:07
-YoctoAutoBuilder- build #248 of nightly-fsl-arm is complete: Failure [failed Building Images_1] Build details are at
*** SidH_ <SidH_!~SidH_@> has joined #yocto04:16
*** mario-goulart <mario-goulart!> has quit IRC04:19
*** mario-goulart <mario-goulart!> has joined #yocto04:20
*** smartin_ <smartin_!> has joined #yocto04:20
*** smartin <smartin!> has quit IRC04:21
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto04:54
*** andyross <andyross!> has quit IRC05:10
*** Jefro <Jefro!> has joined #yocto05:14
*** SidH_ <SidH_!~SidH_@> has quit IRC05:29
*** SidH_ <SidH_!~SidH_@> has joined #yocto05:30
*** mebrown <mebrown!> has quit IRC05:39
*** zeeblex <zeeblex!~apalalax@> has joined #yocto05:41
*** qt-x <qt-x!~ionel@> has joined #yocto05:45
*** [simar|on] <[simar|on]!> has quit IRC05:49
*** tor <tor!> has joined #yocto05:51
*** mebrown <mebrown!> has joined #yocto05:52
*** kbart <kbart!~KBart@> has joined #yocto05:52
*** mihai <mihai!~mihai@> has quit IRC05:54
*** mebrown <mebrown!> has quit IRC06:00
*** mebrown <mebrown!> has joined #yocto06:05
*** zecke <zecke!> has joined #yocto06:11
*** swex <swex!~swex@> has joined #yocto06:15
*** swex__ <swex__!~swex@> has quit IRC06:15
*** linu1 <linu1!~linu1@> has joined #yocto06:16
linu1hi i got the below error while compiling kerenel-3.6.9 for arm arch using poky toolchain,my host system is 64-bit ubuntu 12.04 LTS,the erros is,can you help me06:19
*** SidH_ <SidH_!~SidH_@> has quit IRC06:23
*** nitink <nitink!~nitink@> has quit IRC06:27
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC06:36
*** B4gder <B4gder!> has joined #yocto06:39
*** elmi82 <elmi82!> has joined #yocto06:40
*** eballetbo <eballetbo!> has joined #yocto06:42
*** gmacario <gmacario!> has joined #yocto06:45
*** roxell <roxell!~roxell@linaro/roxell> has quit IRC06:45
qt-xhow to clean all built images ?06:45
lpapp-c cleanall?06:46
qt-xthat requires a target06:47
qt-xor not ?06:47
*** roxell <roxell!> has joined #yocto06:47
*** roxell <roxell!~roxell@linaro/roxell> has joined #yocto06:47
*** SidH_ <SidH_!~SidH_@> has joined #yocto06:49
lpappqt-x: so?06:49
qt-xI want to clean all my builds06:49
*** mihai <mihai!~mihai@> has joined #yocto06:49
qt-xI don't think I\m making any sens06:50
lpappwell, you can always rm -rf06:50
qt-xthat was the alternative :D06:50
lpapphow about bitbake world -c cleanall?06:51
qt-xI'have just tried that it did not work for some recipe06:52
lpappwell, rm -rf, then.06:52
qt-xI'have just tried that. It did not work for some recipe06:52
qt-xon build ?06:52
lpappwell, in python: for image in ('core-image-minimal', ...):['bitbake', image', '-c', 'cleanall']) or something like that06:53
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto06:54
lpappyou could get the images dynamically from bitbake-layers06:54
lpappso you could write such a simple script.06:54
lpappbut I guess rm -rf is simpler.06:54
lpappbtw, I created a bugreport for this a while ago... you can vote if you wish. :D06:55
yoctiBug 4922: enhancement, Low, Future, richard.purdie, NEW , There is no clean option for bitbake or a separate util06:56
lpappqt-x: a cleanall option for bitbake would help you without target, right ?06:56
lpappthat is what I wanted to have in there, too.06:56
qt-xI think so.06:57
lpappqt-x: well, comment in there with a +1 then.06:58
lpappqt-x: they will see there is more than just one person interested. :D06:58
*** Saur <Saur!pkj@nat/axis/x-brflixiqhwtscpsi> has joined #yocto07:00
qt-xIt' becomes a feature :D07:02
lpappwell, only if they see there is enough interest, I guess.07:03
lpappqt-x: are you a qt developer?07:05
*** slaine <slaine!~slaine@> has joined #yocto07:05
qt-xI play with qt when the situation requires it.07:07
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC07:08
qt-xlpapp: anyway if added a +1 depending on the implication of such a command they might do'it.07:08
*** mebrown <mebrown!> has quit IRC07:09
lpappqt-x: yes, saw, thanks.07:09
lpappI need to leave now.07:09
qt-xhave a nice day nigth07:09
*** smartin <smartin!> has joined #yocto07:09
*** smartin_ <smartin_!> has quit IRC07:10
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto07:10
*** amarsman <amarsman!> has quit IRC07:11
*** mebrown <mebrown!> has joined #yocto07:13
*** ant_work <ant_work!> has joined #yocto07:14
-YoctoAutoBuilder- build #249 of nightly-fsl-arm-lsb is complete: Failure [failed Building Images_1] Build details are at
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto07:20
linu1hi i have used kernel-3.6.9 and configure for at91_dt_defconfig, and my host is ubuntu 64 bit,i have used the yocto toolchain for cross compilation,i got the below error while compiling kernel can you please tell me that issues07:21
*** amarsman <amarsman!> has joined #yocto07:26
*** florian_kc <florian_kc!> has joined #yocto07:26
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:26
*** florian_kc is now known as florian07:30
*** jeremiah <jeremiah!> has joined #yocto07:31
*** mebrown <mebrown!> has quit IRC07:38
*** itwasntme <itwasntme!~itwasntme@unaffiliated/itwasntme> has joined #yocto07:48
*** itwasntme <itwasntme!~itwasntme@unaffiliated/itwasntme> has left #yocto07:48
*** bluelightning <bluelightning!~paul@> has joined #yocto07:51
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:51
*** mebrown <mebrown!> has joined #yocto07:51
*** mitz_ <mitz_!> has quit IRC07:51
*** SidH_ <SidH_!~SidH_@> has quit IRC07:52
*** mitz_ <mitz_!> has joined #yocto07:52
*** mebrown <mebrown!> has quit IRC07:55
-YoctoAutoBuilder- build #274 of nightly-world is complete: Success [build successful] Build details are at
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC08:04
-YoctoAutoBuilder- build #279 of nightly-x86 is complete: Success [build successful] Build details are at
bluelightningmorning all08:11
*** SidH_ <SidH_!~SidH_@> has joined #yocto08:14
*** mebrown <mebrown!> has joined #yocto08:18
*** Jay7 <Jay7!~jay@> has quit IRC08:20
*** Jay7 <Jay7!~jay@> has joined #yocto08:20
*** sameo <sameo!~samuel@> has joined #yocto08:25
*** Stygia <Stygia!> has joined #yocto08:25
*** JimBaxter <JimBaxter!> has joined #yocto08:26
StygiaHow do people here usually ensure newly-flashed boxes have the correct time set? Do you just set up NTP, or is there some way to ensure that date is set properly when flashing?08:27
tfntp is the way to go, if you are network-connected08:28
Stygiatf, Alright, that's what I'll go for, then.08:29
tfbut you need a sutiable ntp pool08:29
tfparticularly, if you are doing a commercial product08:29
Stygiatf, Yea I saw something mentioned about that very briefly on the wiki.08:29
Stygiatf, Hmm we sorta are. Does that mean we need to buy-in to a NTP server then?08:29
*** belen <belen!Adium@nat/intel/x-fxaezynwwupfitcb> has joined #yocto08:30
*** honschu_ <honschu_!> has joined #yocto08:32
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has joined #yocto08:32
Stygiatf, no prob.08:33
tfStygia: to use ntp, you have to request an ntp pool for your project08:35
Stygiatf, Yea, I saw a page on the wiki (and on to indicate as much. We will do that before deployment, then. :)08:35
-YoctoAutoBuilder- build #274 of nightly-arm is complete: Success [build successful] Build details are at
*** honschu <honschu!~honschu@shackspace/j4fun> has quit IRC08:35
tfStygia: when you have a pool, you can then enable ntp in connman, which JustWorks08:37
Stygiatf, isn't connman a GUI tool?08:37
Stygiatf, But I'll look into it. :) We have a Friday meeting now. Talk to ya later, and thanks.08:38
*** e8johan <e8johan!> has joined #yocto08:38
tfconnman's not well documented, but that settings file has what you need08:38
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto08:41
*** mebrown <mebrown!> has quit IRC08:47
*** sameo <sameo!~samuel@> has quit IRC09:02
*** slaine <slaine!~slaine@> has quit IRC09:05
*** mebrown <mebrown!> has joined #yocto09:09
*** slaine <slaine!~slaine@> has joined #yocto09:11
*** mebrown <mebrown!> has quit IRC09:14
*** pev <pev!~pev@> has joined #yocto09:14
pevMorning all09:14
*** e8johan <e8johan!> has quit IRC09:16
*** mebrown <mebrown!> has joined #yocto09:17
*** panda84kde <panda84kde!> has joined #yocto09:25
pevSo, I've got a recipe that builds fine via bitbake. However, when I build an image that includes it I just get :09:34
pev| Collected errors:09:34
pev|  * opkg_install_cmd: Cannot install package pevs-package09:34
bluelightningpev: was pevs-package created? it may have been defined but empty and thus never produced in the end09:35
pevAh... That to do with the contents of FILES_${PN}? That rings a bell...09:36
bluelightningthat variable is how you influence what goes into each package yes09:36
pevRighto, I'll have a dig, thanks09:36
bluelightningif you want to see the contents of each package you can have a look under packages-split in the workdir for the recipe btw09:36
pevYep, that'll be the problem then :-)09:38
pevHm, would be nice to add a warning into the build system looking for an empty dir there as that would be easy to spot?09:38
*** melonipoika <melonipoika!> has quit IRC09:39
bluelightningI've been thinking about a way to warn if a package depended upon by another package wasn't produced; it would certainly be helpful09:40
bluelightningjust not quite sure how to implement the check09:40
*** JimBaxter <JimBaxter!> has quit IRC09:40
*** SidH_ <SidH_!~SidH_@> has quit IRC09:41
*** melonipoika <melonipoika!> has joined #yocto09:41
pev find /path/name -maxdepth 0 -empty -exec echo {} is empty. \;09:42
pevNot sure where in the build system though - surely at the loop where it's trying to package each test before doing the packaging09:42
bluelightningright, sure :) it's how to find out what depends on each package in the context of the QA checks in do_package that I'm not sure of09:43
pevDo you actually need to care about dependencies?09:45
bluelightningwell yes... a package not being produced that nothing depends on isn't a problem09:47
*** mebrown <mebrown!> has quit IRC09:49
*** michael_e_brown_ <michael_e_brown_!> has joined #yocto09:49
pevOK, another idiot question. My recipie builds my makefiles 'all'  rule by doing "bitbake pevs-test" but what do I do to provoke the install rule to test? Is there a bitbake command to do all the packaging?09:50
bluelightningpev: if it's a pure makefile and not autotools or something similar you need to define a do_install function which will run "make install" (usually oe_runmake install with some arguments to ensure it installs to ${D})09:52
pevAhhh! That's the bit I didn't know09:52
*** JimBaxter <JimBaxter!> has joined #yocto09:52
bluelightningas for packaging, once stuff goes into ${D} (the "image" subdir of the workdir, if you want to examine it) packaging based on the values of FILES and PACKAGES (both of which have sane defaults, but can be extended/overridden) should be automatic09:53
pevOK, I added     oe_runmake install DESTDIR=${D}09:58
pevwhich is used by other recipes09:58
pevnow I get "ERROR: Function failed: split_and_strip_files"10:00
pevand an objcopy error10:00
pevERROR: objcopy failed with exit code 1 (cmd was 'arm-amltd-linux-gnueabi-objcopy' --only-keep-debug '/workdrive/projects/pevtest/src/pevtest_build/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/pevtest-system/1.0-r0/package/usr/bin/pevtest-server' '/workdrive/projects/pevtest/src/pevtest_build/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/pevtest-system/1.0-r0/package/usr/bin/.debug/pevtest-server')10:01
bluelightningso, in current versions we print what the actual error is from that command10:03
bluelightningat least we should be10:03
bluelightningyou could try bitbake -c devshell pevtest and run that command manually in the shell to see what it says10:04
pevarm-amltd-linux-gnueabi-objcopy:/workdrive/projects/pevtest/src/pevtest_p81_build/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/pevtest-system/1.0-r0/package/usr/bin/pevtest-server: File format not recognized10:05
pevfrom the logfile10:06
pevfile /workdrive/projects/pevtest/src/pevtest_p81_build/tmp/work/armv7a-vfp-neon-amltd-linux-gnueabi/pevtest-system/1.0-r0/package/usr/bin/pevtest-server10:06
pevpevtest-server: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=0xa942bef03d9cf29148797302bcd7c7b4bc9e7e68, not stripped10:07
pevI see. It hasn't cross compiled for some reason... :-D10:10
pevHmpf. So what does bitbake do when invoking my makefile that I'm missing...?10:11
bluelightningI suspected as much10:13
bluelightningalthough really it should have warned about this earlier; it's really a bug that you get this error first instead10:14
bluelightningso with makefiles it's hard for us to consistently be able to specify the right options to enable cross-compilation10:14
bluelightningso you basically need to do this yourself10:14
bluelightningoften it's as easy as passing in values for variables such as CC etc.10:15
pevdoesn't bitbake pass in a CROSS variable or overide CC or something similar?10:15
bluelightningit does set those variables, but you may have to tell make to pull them in10:16
bluelightningpev: e.g.
pevI was defining CC=gcc in the Makefile...10:17
pevChanging that to CC?=gcc seems to do the trick. (ish!)10:17
bluelightningright, I suspect forcing it on the command line would do the same thing10:18
ant_workpev: ^^ this is one rich example10:18
pevant_work: That looks interesting, thanks!10:19
ant_workpev: or th esimple one
ant_workpev: sorry not that one for klibc.. this one10:19
pevResult! Thanks for the help guys, got that nailed and in the build finally... Now just have to mess around with creating the modified sysinit files again... Yuck!10:38
pevOh no, spoke too soon10:39
pevstill hasnt cleared the opkg error...10:39
*** sameo <sameo!~samuel@> has joined #yocto10:41
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto10:45
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto10:48
lpappRP: got a clue for this?
yoctiBug 5043: enhancement, Low, Future, richard.purdie, NEW , Extend the layer creation documentation with own bblayers sample creation10:49
lpappis there any good workaround?10:50
lpappor undocumented feature?10:50
bluelightningpev: I'm guessing the output package is still empty10:52
bluelightningpev: you might want to take a look at what it's installing10:52
lpappbluelightning: hey10:52
bluelightningpev: you should be getting warnings if there are unpackaged files though10:52
bluelightninglpapp: hi10:52
lpappbluelightning: is there a way to run ./ (custom shell script) in do_compile before the regular configure/make?10:53
lpappbluelightning: simply putting in there did not work10:53
lpappI think it was looking into the wrong folder.10:53 will be in ..../git/ because the source is fetched from git.10:53
ant_workbluelightning: btw grep reveals an ample range of syntaxes for the vars appended to oe_runmake10:54
bluelightninglpapp: is S set to point to "${WORKDIR}/git" ?10:54
*** linu1 <linu1!~linu1@> has quit IRC10:54
lpappbluelightning: yes10:54
bluelightningant_work: right, probably depends on who wrote it10:54
ant_workbluelightning: it's just about enclosing the vars in '10:54
bluelightninglpapp: then that will be the current directory when do_configure executes10:54
lpappbluelightning: S = "${WORKDIR}/git"10:55
lpappinherit autotools10:55
bluelightninglpapp: what is in anyway?10:55
lpappdo_compile() {10:55
bluelightninglpapp: ./ perhaps?10:55
lpappbluelightning: autoreconf+custom stuff.10:55
bluelightninglpapp: probably you should separate out the custom stuff and do that in do_configure leaving autotools to do the autoreconf10:56
pevbluelightning:  it was because I was doing multiple packages. Swapping it back to a single one sorted it fine - isn't a big deal so have left it that way. Thanks for the advice!10:56
lpappbluelightning: I am just using the upstream software.10:56
bluelightningpev: np10:56
lpappError, TMPDIR has changed location. You need to either move it back to /home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp or rebuild10:57
bluelightninglpapp: having looked in that file just now I can't see anything of value10:57
lpappthere is no way to simply override a variable after a move?10:57
lpappdo I really need to rebuild stuff?!10:57
bluelightninglpapp: just let autotools.bbclass do what is needed10:58
lpappbluelightning: their configure depends on deb stuff10:58
lpapplike it or not.10:58
lpappand that script generates that at the beginning...10:58
bluelightningthat's unfortunate10:58
*** michael_e_brown_ <michael_e_brown_!> has quit IRC10:58
lpappbluelightning: right10:59
bluelightninglpapp: yep, because upstream software hardcodes paths into its executables, not our fault10:59
lpappthat is in reply to TMPDIR?10:59
bluelightninglpapp: yes10:59
lpappwhat is the proper command to rebuild stuff in this case?10:59
lpapprm -rf manually?11:00
bluelightningdelete the entire TMPDIR or move it back11:00
ndecif you have a sstate folder, deleting TMPDIR, isn't such a big deal. takes less than 3 mins for me to 'rebuild' everything, which in turns just uses stuff from sstate11:01
lpapphmm, it is kinda weird I have an image name like this ... uImage--3.2.1-11:03
lpappwhy double dash?11:03
* lpapp has deleted the tmp folder11:04
bluelightningvariable probably not set I'm guessing11:04
lpappwhich is kinda weird because it used to work11:04
* lpapp guesses it is some kernel variable.11:04
lpappI have this11:06
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto11:07
lpappand this, KERNEL_RELEASE = "3.2.1"11:07
lpappand this, KERNEL_IMAGETYPE = "uImage"11:07
lpappis any of those wrong?11:07
lpappand this, KERNEL_RELEASE = "3.2.1"LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"11:09
lpappyocto also uses LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"11:09
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto11:09
bluelightningI'd suggest looking at the bitbake -e output to see what the history for KERNEL_IMAGE_BASE_NAME is11:10
bluelightningthen you'll be able to see which variable is apparently blank11:10
lpappis that ok without cleaning up?11:11
lpappbitbake -e polatis-core-image | grep KERNEL_IMAGE_BASE_NAME11:11
lpappempty output11:11
lpappsame stuff for modules fwiw, modules--3.2.1...11:12
JaMait's from empty PE11:13
*** melonipoika <melonipoika!> has quit IRC11:13
JaMapackage epoch11:14
lpappthe epoch of the recipe. The default value is "0". The field is used to make upgrades possible when the versioning scheme changes in some backwards incompatible way.11:14
lpappyeah, found it.11:14
lpappnot sure why that would be needed.11:14
lpappthe yocto kernel does not seem to use that either.11:14
JaMaKERNEL_IMAGE_BASE_NAME is used by more kernel recipes then linux-yocto11:14
lpapp(it was not like this with denzil btw)11:15
lpapp(denzil generated single dash)11:16
lpappgrep -rn PKGE ./meta-* -> returns empty.11:17
lpapp./meta/conf/bitbake.conf:199:PKGE ?= "${@['','${PE\x7d'][d.getVar('PE',1) > 0]}"11:17
lpappok, that is beyond my league, I am afraid.11:18
-YoctoAutoBuilder- build #275 of nightly-ppc is complete: Failure [failed Running Sanity Tests] Build details are at
lpappso what is causing regression from denzil to dylan update, and how can it be resolved?11:18
bluelightningI just searched the git log for PKGE to find that btw11:20
ant_workthen that11:21
bluelightninggit blame would have also got the answer11:21
ant_workyes, lpapp your0e rather lazy ;)11:21
lpappI really do not know how it is "lazy" to follow the advice of not having a git repository ....11:22
lpappand using a tarball where git is *obviously* out of scope.11:22
ant_workanyway it's not good if you get it empty11:23
lpappwell, that is the default.11:23
lpappactually, I do not see the Yocto kernel setting that either.11:24
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC11:24
lpappthis change should have preserved the compatibility, i.e. single dash is the default if not specified, otherwise double dash11:25
lpappit breaks the interface...11:25
ant_workyou are running a prserver?11:25
ant_workbluelightning: link please ;)11:26
lpappanyway, what is the workaround?11:26
lpappI do not wanna see double dash11:26
lpappthat is silly.11:26
JaMasince when is filename "interface"?11:26
lpappJaMa: since ever11:26
JaMaSRCREVs were also shortened, so it will be different either way11:27
lpappwell, you do not care about that.11:27
JaMaif you want the same then change KERNEL_IMAGE_BASE_NAME or continue to use old version11:27
lpappusually when you archive, SRCREV is blobbed.11:27
lpappnot to mention, the yocto kernel does not change the PE11:27
lpappwell, this looks like a documentation stuff11:27
lpappif it is not in the migration guide yet.11:27
* lpapp is checking11:28
JaMalink to latest is the same11:28
ant_worklpapp: check your local.conf11:28
ant_workPRSERV_HOST = "localhost:0"11:28
ant_workrecommended also11:28
ant_workINHERIT += "buildhistory"11:28
ant_workBUILDHISTORY_COMMIT = "1"11:28
lpappyeah, nothing in here about it:
lpappI will submit a bugreport for it.11:28
lpappant_work: let us stay on topic. ;)11:29
ant_worklpapp: " is obtained from the PR service..."11:30
BCMMwhere should one submit bugs/features for individual recipes?11:32
BCMMi've patched the mpd recipe so it optionally supports MPD's new CD playback features11:32
yoctiBug 5089: normal, Undecided, ---, scott.m.rifenbark, NEW , Missing KERNEL_IMAGE_BASE_NAME in the migration guide11:32
lpappso the next question is: why is the yocto kernel not using this new "feature"?11:33
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC11:33
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto11:33
lpappalso, why is it silly by default with "--"?11:34
lpappif anything, it should be -0- or so11:34
lpapp"--" looks silly, or is it just me?11:34
JaMawith -0- people will ask what's the "0"11:34
JaMaPR is appended to packagename also only when != 011:35
lpappthe default value?11:35
*** roric <roric!> has quit IRC11:35
lpappwell, it should be either single dash, or -0-11:35
lpappdouble dash is silly IMHO11:35
*** roric <roric!> has joined #yocto11:35
lpappit has no any additional value to a single dash11:35
JaMalpapp: the default value for PKGE is empty, same answer as "0"11:35
lpapp'--' is silly11:36
lpappit does not contribute much to '-'11:36
JaMaand -0 does?11:36
lpappbecause that means a number11:36
lpappnot a string placeholder11:36
lpappnot an "enum" etc.11:36
lpappit means the PE "version"11:36
lpappwhich is zero (the default)11:36
lpappso I propose to change it either to '-' or '-0-' unless I am missing something.11:37
lpapphmm, that changed too11:38
lpappthe datum was not there before!11:38
lpappthanks to this, I will be busy today with fixing CI issues. :(11:39
JaMaso finally fix your silli CI scripts11:40
lpapp"silly" CI script because someone decides it is cool to break stuff for many end users due to such a nuance.11:41
lpappactually, for compatibility, I prefer '-' over '-0-'11:41
*** Net147 <Net147!> has joined #yocto11:42
lpappbluelightning: any reason why my generated rpm packages are empty for my own software?12:03
lpappbluelightning: the default do_install does not put things right in there?12:04
*** phdeswer_ <phdeswer_!> has joined #yocto12:16
lpappdo I need to inherit anything for the proper packaging, or is there some documentation about it, and how to avoid empty packageS?12:22
*** phdeswer_ <phdeswer_!> has quit IRC12:27
lpappJaMa: perhaps BUGTRACKER could be added to the qt5 packages?12:36
lpappShall I submit such a change?12:37
*** acidfu <acidfu!~nib@> has joined #yocto12:39
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto12:39
lpappoh, I need FILES for pretty much anything?12:45
lpappbut but but... the debian packaging works the way that if you do not pass anything, you will get one monolithic package. I would be more than happy with that for now. Is there such an option to turn on?12:45
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC12:48
*** cfo215 <cfo215!> has joined #yocto12:53
lpappI see that certain packages do not use the FILES variable, just install in the do_install... are they equivalent?12:57
*** Anusko <Anusko!~anusko@> has joined #yocto12:58
*** kbart <kbart!~KBart@> has quit IRC13:01
lpappwhich way is recommended?13:04
*** Guest37012 <Guest37012!c2881242@gateway/web/freenode/ip.> has quit IRC13:04
*** walters <walters!> has joined #yocto13:05
ndeclpapp: maybe they just rely on the 'default' FILES valueS?13:07
*** acidfu <acidfu!~nib@> has joined #yocto13:08
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto13:08
lpappndec: which is?13:08
ndecin meta/conf/bitbake.conf13:08
lpappI cannot read that13:09
ndecwhat do you mena?13:09
*** ant_work <ant_work!> has quit IRC13:09
lpappright, so installation or FILES are needed13:10
ndecboth are needed13:10
lpappwell, no.13:10
lpappI can work it without FILES13:10
ndecpackages are created by taking files from where they have been installed.13:10
lpappactually, I even think this should be documented.13:10
lpappyou do not necessarily need FILES if you install stuff correctly.13:10
ndecthere are sane default for FILES (for all packages, including -dev, -dgb, ... too). most software would work fine with these default.13:11
ndecyou might to play with FILES if you have more complex packages.13:11
lpappI think this should be documented.13:11
lpappI will open a bugreport13:11
ndecfor what?13:12
lpappthis is not mentioned under the FILES var.13:12
lpappto mention that you do not need it for simple stuff13:12
lpappsimple and sane13:12
lpappyou just need to install is all13:12
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC13:12
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto13:13
ndecwell, most variables have 'sane' default values, if you go this path...13:13
lpappI am not sure about it.13:13
lpappbut when I go to FILES, I would like to read that it is not necessary for simple use cases13:13
bluelightningit's not about FILES so it's not something to add to the variable glossary entry for FILES13:13
lpappyou just need to make it is installed.13:13
lpappsure, it is.13:13
bluelightningyou're missing do_install13:13
lpappI am actually filing a doc bugreport about it.13:13
bluelightningno changing of FILES will help you around that13:14
lpappsure, it will.13:14
erenhow can I force bitbake recipe parsing cache to refresh?13:14
bluelightningI'm sure it won't, not if do_install isn't defined13:14
erenI changed one line in machine config and bitbake uses the old one13:14
lpappbluelightning: you know better what would help me? :D13:15
ndeceren: rm -rf tmp ;-)13:15
bluelightningerr no13:15
bluelightningeren: it should do that automatically, something is not right if it isn't13:15
bluelightningeren: or, you changed it back to a value that you had previously and it's using the cache from the last time you set that13:15
* lpapp has always lacked ldd for the arm toolchain.13:15
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC13:16
erenbluelightning: now it parsed13:16
erenbluelightning: I added one line in IMAGE_FSTYPES, it did not parse the recipes and got directly from cache13:16
ereni removed all the lines except the one I want, it parsed the recipes13:17
lpappbluelightning: I am not disagreeing about missing do_install13:21
lpappbut I disagree about not making a reference and a note about default to FILES13:21
lpappreference to do_install13:21
bluelightningthere's only so much you can put in a glossary entry13:21
bluelightningwe're planning an expanded section on how to write new recipes to be written in 1.613:21
bluelightningthat's where that kind of thing belongs, IMO13:22
*** Guest26644 <Guest26644!c2881242@gateway/web/freenode/ip.> has quit IRC13:22
lpappit belongs to there, too13:22
lpappone is glossary, the other is example put up with glossary entries.13:22
bluelightningthere is also a new section coming in the 1.5 manual explaining how the build system generally operates and points to variables used during each stage of the build13:22
bluelightningyou can even look at it in the "latest" version of the manuals on the website13:23
lpappI do not dare. :D13:23
*** Krz_ <Krz_!c0c6972c@gateway/web/freenode/ip.> has joined #yocto13:24
ndecbluelightning: in which manual is that new section?13:25
Krz_hi there, in plenty or recipes people use 'install' to copy files to image. i tried rsync instead and Yocto says : WARNING: QA Issue: galileo-target: Files/directories were installed but not shipped13:25
bluelightningndec: the ref manual I believe13:26
Krz_is rsync not liked by Yocto?13:26
bluelightningKrz_: forgive me for asking but why would you need to use rsync in do_install?13:27
Krz_sorry, I used rsync in Makefile, to let non-Yocto users have the same as Yocto users13:28
Krz_and in do_install I just call make install-mytarget13:28
Krz_which call rsync from Makefile13:28
Krz_does that make sense?13:28
bluelightningKrz_: I'm understanding a little more but still not why rsync would be useful in that particular context13:29
Krz_so basically in my source package I created whole directory tree instead of hiding instructions on how to build it inside Makefile13:30
Krz_so then non-Yocto users can just copy whole tree to the image13:30
*** zeeblex <zeeblex!~apalalax@> has left #yocto13:30
*** Anusko <Anusko!~anusko@> has quit IRC13:31
*** Anusko <Anusko!~anusko@> has joined #yocto13:31
bluelightningKrz_: there's nothing inherent about do_install that would prevent rsync being used, but remember that do_install is just about installing files to the holding area in ${D} before packaging, not actually into the image13:32
StygiaAnd wouldn't something that used rsync to (presumably) fetch files be better placed in do_fetch or something? This statement has the caveat that I haven't been following Krz_ 's usecase.13:33
*** mulhern <mulhern!> has joined #yocto13:34
Krz_in my source package I have: *.c files to create binary and few *.sh scripts just to be copied over13:35
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC13:36
Krz_now when I do 'make install'  it rsyncs source-package/my/tree/*.sh13:36
Krz_and rsyncs binary as well13:36
Krz_thanks to that someone without Yocto can just go to my package, do 'make install DESTDIR=/path/to/my/image'13:37
bluelightningI'm still confused13:38
bluelightningmake install can always do that without rsync13:38
bluelightningso what does rsync enable here?13:38
Krz_my tree looks like: src-package/etc/my/directory/few-scripts.sh13:39
Krz_root directory is src-package13:39
Krz_rsync just takes whole tree and copies it13:40
Krz_wheres using 'install' for that is more compilicated13:40
Krz_so I used rsync - one liner13:40
bluelightningKrz_: if it's only because you're wanting to copy a full directory tree, surely cp -r would work and be much simpler?13:42
Krz_yeah, but cp does not preserve attributes13:43
bluelightningit has an option to do that...13:43
Krz_hmm, I can try that13:44
Krz_will not cp issue the same QA WARNING?13:44
bluelightningI mean, rsync will work, it just seems like overkill for this13:44
bluelightningwhatever technique you use, you absolutely must install to ${D}13:44
bluelightningwithin do_install13:44
bluelightningand secondarily, the value of FILES for each package must be set to match whereever you are installing things to13:45
bluelightningbut FILES_${PN} already includes ${sysconfdir} which is /etc13:45
bluelightningso I wouldn't have thought it necessary to touch FILES just for stuff in /etc13:45
Krz_my do_install look like that: oe_runmake install-scripts DESTDIR=${D}/13:46
Krz_then Makefile picks up $DESTDIR and rsyncs the tree (which I might switch to cp -p as well)13:47
Krz_the main problem is with Yocto QA WARNING which causes files not to be installed in image13:47
bluelightningKrz_: the QA warning is not what causes files not to be installed in the image13:48
bluelightningKrz_: it's warning you that you haven't done the right thing to have those files end up in a package such that they can get in the image - there's a difference :)13:48
bluelightningFWIW, that line looks normal, so it must be where it is putting things under ${D}13:48
bluelightningI'd suggest looking in ${D} for the recipe13:49
bluelightningthis will tell you where that is exactly: bitbake -e recipename | grep ^D=13:49
Krz_ok I understand it more now :)13:50
*** Stygia <Stygia!> has quit IRC13:51
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ncxdbbiiuscpvmld> has quit IRC13:54
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-gprvaeggwizddwln> has joined #yocto13:55
*** B4gder <B4gder!> has quit IRC13:56
erenit seems that I cannot run a python function inside bbclass file14:00
erensimply calling "build_syslinux_cfg()" gives me parse error14:01
*** wmcdevel <wmcdevel!> has joined #yocto14:01
*** Net147 <Net147!> has quit IRC14:03
bluelightningeren: how have you defined the function?14:03
*** W1N9Zr0 <W1N9Zr0!> has quit IRC14:03
wmcdevelgood morning ... anyone around that could assist with a couple of BSP/Kernel-related questions?14:04
*** W1N9Zr0 <W1N9Zr0!> has joined #yocto14:04
erenbluelightning: IMAGE_CMD_alix-hddimage() {14:05
Garibaldi|workHi all, I'm trying to build a minimal image for MIPS with DEFAULTTUNE = "mips64-n32", and I get a failure when building busybox:  mips64-poky-linux-gnun32-ld: Attempt to do relocatable link with elf32-ntradbigmips input and elf64-tradbigmips output; mips64-poky-linux-gnun32-ld: applets/applets.o: file class ELFCLASS32 incompatible with ELFCLASS6414:05
erenbluelightning: I called the python function with @{'build_syslinux_cfg', d)}14:05
Garibaldi|workI started with a clean workspace.  Am I doing something wrong?14:06
erenbluelightning: it returns None and build halts. Then I decided RETVAL="${}"14:06
erenhowever, now syslinux config is not created14:06
*** jeremiah <jeremiah!> has quit IRC14:07
bluelightningeren: er, but those are two different functions14:08
erenso should I call ${@build_syslinux_cfg(d)} ?14:08
bluelightningwell you wouldn't just state it like that in the recipe14:09
*** darknighte_znc is now known as darknighte14:09
*** elmi82 <elmi82!> has quit IRC14:09
bluelightningin a variable value, yes, but then this doesn't sound like the kind of function that should be called that way14:09
JaMathat reminds me that with new syslinux bbclass it's impossible to disable console, I should file a bug about that14:10
erenactually what I am trying to do is to have image creation just like raspberry. I am editing boot-directdist.bbclass14:10
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto14:10
*** qt-x <qt-x!~ionel@> has quit IRC14:10
bluelightningeren: basically then you need to have that function called from a task function14:11
erenI put that into IMAGE_CMD_alix-hddimage() {}, added initrd support. However, boot-directdisk.bbclass calls'build_syslinux_cfg') before creating the image14:11
JaMaeren: I haven't read backlog yet, but please see my comments in
yoctiBug 3944: enhancement, Medium, 1.4, jason.wessel, REOPENED , syslinux.bbclass needs some work to add serial support and a real menu14:11
wmcdevelI have an ARM-based development board that used to be supported by OE, and is not part of the Yocto/Poky build. The vendor provides a custom kernel, which I can build outside of Poky without a problem. I'd like to incorporate it into the Poky build and make a BSP for the board, but I'm at a loss on how to get it in there.14:11
erenbluelightning: and yes, it is called from a task function14:12
erenbluelightning: so there is no way to simply call build_syslinux_cfg?14:12
bluelightningwmcdevel: have you looked at the Yocto Project BSP guide and kernel manuals?14:12
bluelightningeren: call in what context?14:12
wmcdevelbluelightning: yes. I have gotten as far as creating the BSP layer and some sample bitbake recipes, but I can't seem to figure out how to get the build to not use the linux-yocto kernel.14:13
erenbluelightning: IMAGE_CMD_foobar() context14:13
bluelightningwmcdevel: PREFERRED_PROVIDER_virtual/kernel = "your-kernel-recipe-name"14:14
bluelightningwmcdevel: that would be set in your machine's conf/machine/xyz.conf file14:14
erenbluelightning: btw, I am working on this:
wmcdevelbluelightning: ok. do I need anything in particular in my kernel recipe? for example, I've seen where Git is used, quilt, etc. I have a plain-old tarball to work with.14:16
bluelightningwmcdevel: not really... but for that though I would suggest using the linux-yocto-custom recipe (under meta-skeleton/recipes-kernel/, also mentioned in the kernel manual) as a template14:18
wmcdevelbluelightning: ok, cool. will fiddle around with that a bit and see where I get. thanks14:19
*** JimBaxter <JimBaxter!> has quit IRC14:22
bluelightningGaribaldi|work: sounds like a question for khem perhaps14:23
*** Net147 <Net147!> has joined #yocto14:24
*** levi <levi!~user@> has quit IRC14:24
lpapprunning this on the host side now, LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. gdb --args14:25
lpappsorry, wrong window.14:25
*** e8johan <e8johan!> has joined #yocto14:27
Garibaldi|workbluelightning: thanks, I'll keep an eye out :-)14:28
*** Saur <Saur!pkj@nat/axis/x-brflixiqhwtscpsi> has quit IRC14:31
*** smartin <smartin!> has quit IRC14:31
bluelightningeren: right14:33
bluelightningeren: but that's a shell function if I'm not mistaken14:33
bluelightningeren: you cannot call python functions from shell functions unless it's something that is appropriate to be run when the function is parsed, which is what will happen if you use ${@...} inside a shell function14:35
*** smartin <smartin!> has joined #yocto14:35
erenbluelightning: I added a new task before do_rootfs14:35
erenit works ok, creates syslinux.cfg but at one time ${S} is deleted14:36
*** JimBaxter <JimBaxter!> has joined #yocto14:36
erenbluelightning: is there any way to see the order of the tasks?14:37
eren-c liststasks does not give me in which order bitbake runs tasks14:38
bluelightningeren: after they've executed you can look at log.task_order next to the task logs for the recipe14:38
Krz_do I need a FILES_${PN} in my recipe to let files be installed into image?14:40
bluelightningKrz_the default value is sane for most recipes but it depends on where files are intended to be installed to within the image14:42
bluelightningKrz_: you may wish to look at the default values for FILES for each package in meta/conf/bitbake.conf14:42
*** Saur <Saur!pkj@nat/axis/x-hodbfywsjwoveoyc> has joined #yocto14:43
Krz_bluelightning: I have custom dir under /opt to install my files - I think in that case I have to specify that in FILES_${PN}...14:44
bluelightningKrz_: right, you would yes, /opt is not part of the default value14:45
Krz_bluelightning: ok, so that was my problem and reason for QA WARNING14:46
bluelightningok, makes sense14:51
*** e8johan <e8johan!> has quit IRC14:53
*** Saur <Saur!pkj@nat/axis/x-hodbfywsjwoveoyc> has quit IRC15:02
*** seebs <seebs!> has quit IRC15:03
*** Net147 <Net147!> has quit IRC15:07
*** Saur <Saur!pkj@nat/axis/x-znrmskrttijavprr> has joined #yocto15:09
*** sameo <sameo!~samuel@> has quit IRC15:10
*** sameo <sameo!~samuel@> has joined #yocto15:10
*** Stygia <Stygia!> has joined #yocto15:11
*** andyross <andyross!> has joined #yocto15:12
StygiaHey. I was under the impression that do_install_append's would stack, so that if I have one in my bbappend, and there is one in the core (ntp in this case), they would be applied in turn. However, my very simple do_install_append function that simply creates a symlink causes the whole mess to fail. What could cause this?15:13
bluelightningStygia: they will stack15:13
bluelightningStygia: what's the failure?15:14
Stygiabluelightning, Just as sec and I'll reproduce it and put in it pastebin15:14
*** johnsoga <johnsoga!4542f923@gateway/web/freenode/ip.> has joined #yocto15:15
Stygiabluelightning, The recipe and the part of the error I think is the relevant bit:
bluelightningStygia: missing ${D} in front of the paths15:16
Stygiabluelightning, Ah shit. Heh I wanted to call in sick today (I'm on like 4 hours sleep), but we're busy, so. Sorry.15:17
bluelightningStygia: nm, I make mistakes like that all of the time :)15:17
kergothStygia: also, use bitbake -e to confirrm what you think is happening is actually happening. you'd see both appends occurred by examining the value of do_install :)15:17
Stygiabluelightning, I just copy-pasted the command I wanted that'd already worked on the box.15:17
kergoththough bb-show makes that a littlel easier since you can't grep out a function definition trivially..15:18
* kergoth yawns15:18
Stygiakergoth, I wish I could say man bitbake.15:18
kergothbitbake -h covers the usage, but admittedly has no examples or anything :)15:18
kergothiirc someone is working on improved bitbake docs for yocto15:18
bluelightningStygia: you can do: man ../bitbake/doc/bitbake.115:19
bluelightningthough it's pretty sparse15:19
kergothhuh, good point15:19
kergothforgot that exised :)15:19
bluelightningI almost did as well until Stygia brought it up :)15:19
StygiaFancy. Wrote that all down, then.15:19
kergothapparently they're using an old man page there, doesn't understand -u :)15:20
kergothinteresting site though,
bluelightningoo fancy15:21
*** munch <munch!> has joined #yocto15:21
bluelightninghmm, seemingly failed on cpio though15:22
kergothindeed. not sure how smart it is, and it can't handle pipelines yet, but i could see it being usefulu for confused users looking at snippets on occasion15:22
johnsogaHello, what is the difference between native and nativesdk?  I have seen BBCLASSEXTEND set to this.15:22
StygiaAnd huh. That looks cool.15:22
bluelightningjohnsoga: native = something to run on the build host; nativesdk = something to go into an installable SDK15:23
*** simar <simar!~simar@> has quit IRC15:24
*** simar <simar!~simar@> has joined #yocto15:24
*** simar <simar!~simar@> has joined #yocto15:24
johnsogabluelighting: is it very often that a package needs to change between the build host and the sdk?15:24
kergoththe sdk can target a different host, e.g. i686 vs x86_64, for one15:25
kergothfor two, nativesdk recipes are packaged15:25
kergothi think those are the main differences, but someone else would know better than i15:25
johnsogakergoth: ah, ok that makes sence15:25
*** simar <simar!~simar@> has quit IRC15:25
*** simar <simar!~simar@> has joined #yocto15:26
StygiaHmm. In a do_install_append, I have this:     ln -s ${D}/usr/share/zoneinfo/Europe/Copenhagen ${D}/etc/localtime15:26
johnsogaSo my next question is what is the best way to determine that a bitbake file is being run as native or nativesdk so that I can change the configuration options?15:26
StygiaIt now runs without errors, but after flashing, the /etc/localtime file doesn't exist.15:26
StygiaWhat do I need to do to effectively symlink /usr/share/zoneinfo/Europe/Copenhagen to /etc/localtime on the produced image?15:27
kergothStygia: that's going to create a link pointing at a path on your buildsystem :P15:27
kergothan absolute path15:27
pevRandom question : Anyone done much system tuning to speed up a full image build? On my machine it's a spritely 63 minutes (using pre-downloaded sources) but was wondering if there were any tricks I'm missing that are worth doing to make speedier?15:27
kergothln -s ${datadir}/zoneinfo/Europe/Copenhagen ${D}${sysconfdir}/localtime15:27
johnsogaI have seen things like <variable>_virtualclass-native but I have also seen <variable>_native15:27
nerdboyin this case you're making abroken symlink...15:27
pev(thats for an imx61 image)15:28
Stygiakergoth, Hmm. Why is having ${D}{sysconfdir} fundementally different from what I did? I don't have a broken symlink, I have no symlink.15:28
kergothjohnsoga: when the recipe is native, 'class-native' is in OVERRIDES, so you can override variables or append/prepend to them15:28
kergothStygia: well, that line will create an existing but broken symlink15:28
kergothso you must have something else going on15:28
Stygiakergoth, Hmm weird. Alright, does it belong in do_install_append, or somewhere else in the process?15:29
kergothusing sysconfdir and datadir is just to enusre the recipe obeys our path variables, it wonto fundamentally change whats happening15:29
kergoththe main change is i didn't use ${D} in the destination of the link15:29
Stygiakergoth, Yea that's exactly what I figured.15:29
kergothonly the path to the link15:29
*** davest <davest!Adium@nat/intel/x-okqpsjlebtsmpqeq> has joined #yocto15:29
* nerdboy set a DEFAULT_TIMEZONE variable in his .conf15:29
kergoththat does sound cleaner15:29
Stygianerdboy, So you're saying I can add DEFAULT_TIMEZONE=Europe/Copenhagen to my local.conf and that'd be it?15:30
nerdboyi hacked it in15:30
Stygianerdboy, Ah. So it's not a feature in vanilla yocto?15:30
lpappis it possible to modify source in the workdir and rebuild that without wiping away?15:31
kergothi wonder if we ever got an overlay recipe to let you just drop files into a mirror filesystem that'd be captured and included in the image15:31
lpappI do not wanna modify the source, generate tarball, ship to yocto, etc15:31
nerdboythe symlink thing *could* go in pkg_postinst15:31
kergothto use for configuration15:31
lpappit is more steps than just modifying in the workdir15:31
Stygianerdboy, Hmm, yea I'm sorta fearing that something removes the symlink after it's created in the do_install_append stage.15:31
kergothpossible, though unlikely15:32
StygiaBut I'm building a new image with kergoth's version of the ln, I'll check my tmp/ to see it's there.15:32
nerdboyStygia: we used to symlink that in default gentoo builds but stopped a while back15:32
Stygiaand ntp does do_package and everything now without having been cleaned, so the bbappend definitively catches on.15:33
Stygianerdboy, Heh, gentoo uses yocto?15:33
nerdboyswitched it to a cp instead15:33
nerdboyno, the symlink method of setting localtime15:33
lpappbluelightning: thanks, is there a global way with yocto to force debug builds?15:33
Stygianerdboy, Oh? I've always ln'd timezones, that's how I've seen it done in every example and tutorial ever.15:33
nerdboy*method even15:33
kergothStygia: you can always examine the actual ipk contents, and the contents of ${WORKDIR}/packages-split/, to see what really went into the binary package, too15:33
lpappbluelightning: pass -g to gcc all the time?15:33
lpappor at least for the selected softwares?15:33
Stygiakergoth, Yea, normally I just do a find tmp/ -name whatever, though.15:34
lpappI am getting a segfault, and would like to debug it.15:34
kergothipkcontents () { ar p $1 data.tar.gz | tar -tvz } # prints the files in the ipk15:34
nerdboyyup, sometimes i download and unpack an ipk to make sure what's in it15:34
bluelightninglpapp: set DEBUG_BUILD in the recipe I guess, haven't ever done it myself15:34
kergothipkinfo () { ar p $1 control.tar.gz | tar -zxO ./control } is also handy from time to time, to see the metadata15:34
bluelightninglpapp: usually you can just install gdb and the debugging symbols for the package into your image and that is enough15:35
bluelightninglpapp: I've definitely done the latter15:35
Stygiakergoth, Ah, hmm. Looks like tzdata sets /etc/localtime, there's a tmp/work/all-poky-linux/tzdata/2013b-r0/packages-split/tzdata/etc/localtime anyway.15:36
kergothahh, that'd explain it15:37
nerdboyapparently i din't need to do too much hacking on that one15:37
nerdboysince this is already in the tzdata recipe => poky/meta/recipes-extended/tzdata/ ?= "Universal"15:37
kergothhah, good to know :)15:38
nerdboyStygia: try setting DEFAULT_TIMEZONE in your image recipe15:38
kergoththat should be in an faq somewhere. how do i set my timezone default15:38
bluelightningnerdboy: er that won't work15:38
lpappbluelightning: DEBUG_BUILD -> -g3 -O0?15:38
Stygianerdboy, Yea, exactly what I did.15:38
Stygianerdboy, I made a bbappend to tzdata15:38
StygiaWhere I did DEFAULT_TIMEZONE = 'Europe/Copenhagen'15:39
StygiaSorta insulting it acts like "Europe" is a country. But whatever.15:39
bluelightningnerdboy: if the tzdata recipe is expecting to read it, setting it in the image recipe won't change the value read15:39
bluelightninglpapp: setting DEBUG_BUILD=1 will use whatever is in DEBUG_OPTIMIZATION15:40
nerdboyshould be able to override it15:40
bluelightningyou can, just not from the image recipe15:40
bluelightningat least not in that way15:40
nerdboymaybe my grep missed something...15:40
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC15:41
Stygiabluelightning, Doing it in a bbappend is logical and sane, though, right?15:41
lpappbluelightning: what is the default?15:41
StygiaA bbappend that only contains "DEFAULT_TIMEZONE = 'Europe/Copenhagen'", then it should be overwrite the value in the main recipe?15:41
StygiaIt uses ?= in the main recipe, btw... whatever that means.15:41
kergothyou could bbappend tzdata, or just set it in your local.conf or distro15:41
kergoth?= means set only if unset15:41
*** belen <belen!Adium@nat/intel/x-fxaezynwwupfitcb> has quit IRC15:41
nerdboyyup, stuck it in local.conf15:41
johnsogakergoth: what does it mean when I see class-native vs virtclass-native?15:41
kergothso if the config metadat set its, it wont override it15:41
kergoththe virt prefix is deprecated, and possibly not even supported anymore, not sure15:42
bluelightninglpapp: bitbake -e | grep ^DEBUG_OPTIMIZATION=15:42
nerdboyStygia: try setting it in local.conf15:42
kergothjohnsoga: some natives are bbclassextended, some are real recipes. we needed an override that'd work for both, hence no 'virt', since tghe real recipe isn't "virtual"15:42
Stygianerdboy, Hmm if it works in the bbappend I'm quite happy with that. And it seems like it did. But thanks. :)15:42
kergoththis seems like the kind of thing thats conceptually better in the config metadata, since its configuration, but either will do :)15:43
erenyeah, I finally did it15:43
lpappbluelightning: but at least -g3?15:43
*** belen <belen!~Adium@> has joined #yocto15:43
* nerdboy needs to clean out some cruft15:44
johnsogakergoth: k thanks, some of this doesn't have good documentation yet so I have been just looking through other bb files and ncurses still uses the virt prefix.15:44
lpappbluelightning: DEBUG_OPTIMIZATION="-O -fno-omit-frame-pointer -g -feliminate-unused-debug-types -pipe"15:44
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto15:44
bluelightninglpapp: if you prefer a different value just set DEBUG_OPTIMIZATION to whatever you want15:44
lpappbluelightning: I need -O0, not -O115:45
bluelightninglpapp: FYI, -g is specified with FULL_OPTIMIZATION (the default) as well, hence how we always have debugging symbols15:45
*** smartin_ <smartin_!> has joined #yocto15:45
lpappbluelightning: what do you mean by default?15:45
lpappby defaul if you specify DEBUG_BUILD=1?15:45
bluelightninglpapp: if you never set DEBUG_BUILD15:45
kergoththe main difference, afaik, is the "debug build" disables optimizations to avoid problems when debugging, other than that, there's no point to it anymore what with the splitting of debug symbols into -dbg15:46
*** zenlinux_ <zenlinux_!> has joined #yocto15:46
lpappbluelightning: so -g3 is the default for any build?15:46
bluelightninglpapp: no, -g is15:46
*** smartin <smartin!> has quit IRC15:46
bluelightninglpapp: see the value of FULL_OPTIMIZATION15:46
lpappbluelightning: ok, that is not good enough.15:47
bluelightningfeel free to do as suggested above then15:48
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC15:50
* nerdboy has another day of hardware shenanigans and system migration15:50
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto15:51
BCMMis there some way to list files belonging to a particular package?15:51
BCMMe.g. see a list of files added to the image by including sysvinit15:52
nerdboywhat kergoth posted for listing ipk contents15:52
kergothbuildhistory has a lot of info as well, both about the package contentsa nd image contents15:54
kergothif you use it, of couse15:54
*** nitink <nitink!~nitink@> has joined #yocto15:54
bluelightningBCMM: yep buildhistory is useful for finding out that kind of information:
StygiaHmm. /etc/localtime doesn't make it into my image at all. I've set DEFAULT_TIMEZONE, and from what I can read in tzdata's do_install (, it should be installed, and generate an error if it isn't installed. Since it wasn't in the FILES_${PN} array I added it in my bbappend, and although tmp/work/all-poky-linux/tzdata/2013b-r0/packages-split/tzdata/etc/localtime exists, it's not part of the image.15:58
StygiaWhat am I missing here?15:58
nerdboythings that make you go "hmm..."15:59
StygiaIt seems like the pkg_postinstall_${PN} thing removes it, but only if it's invalid, and it _should_ at least print it and tell me.15:59
*** Anusko <Anusko!~anusko@> has quit IRC16:00
StygiaAnd this file is in tmp/ after (tmp/work/all-poky-linux/tzdata/2013b-r0/package/usr/share/zoneinfo/Europe/Copenhagen), so it's not that it doesn't exist16:00
*** Anusko <Anusko!~anusko@> has joined #yocto16:00
*** eballetbo <eballetbo!> has quit IRC16:01
bluelightningStygia: anything related in log.do_rootfs?16:01
*** belen <belen!~Adium@> has quit IRC16:01
Stygiabluelightning, Nope, just a single line saying it's executing the shell function do_rootfs16:02
bluelightningthere should be a *lot* more than just that line16:03
Stygiabluelightning, Well in the log.do_roofts returned by my find build/ -name log.do_rootfs16:03
*** smartin <smartin!> has joined #yocto16:03
Stygiabluelightning, Oh... now there is.16:03
Stygiabluelightning, Weird.16:03
*** belen <belen!~Adium@> has joined #yocto16:03
Stygiabluelightning, Maybe less was just teasing me, though, and wanting me to manually press down-arrow... I dunno.16:03
*** smartin_ <smartin_!> has quit IRC16:06
Stygiabluelightning, Nope... nothing that I see that looks relevant.16:07
bluelightningStygia: is it in the rootfs subdir of the image work directory16:08
StygiaI should note, I think, that /etc/localtime is only shown as a subfolder to tzdata*/, not as part of the image...16:08
bluelightningok, then I can only assume either a postinstall script or something in do_rootfs deleted it16:08
Stygiabluelightning, Hmm yup, pkg_postinst_${PN} in the main recipe deletes it if the timezone doesn't exist. However, I did a pkg_postinst_${PN}_append to do it manually, with no luck.16:09
bluelightningStygia: you'd see the output of those echo statements in log.do_rootfs if they were being run16:09
Stygiabluelightning, And hmm, yea they aren't.16:10
*** belen <belen!~Adium@> has quit IRC16:11
Stygiabluelightning, It's here, though: tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/ntp/4.2.6p5-r8.0/image/etc/localtime16:11
bluelightningI thought it was supposed to be tzdata installing this file16:12
nerdboyit is16:12
Stygiabluelightning, It is. It shows up as subdirs tzdata, and _then_ that, too.16:12
*** belen <belen!Adium@nat/intel/x-dakuhtzpxbnhtmvp> has joined #yocto16:12
nerdboytzdata owns both /etc/localtime and /etc/timezone16:12
Stygiabluelightning, Oh wait, shit, that lists ntp. That's just a leftover from my earlier recipe. Never mind.16:12
*** e8johan <e8johan!> has joined #yocto16:13
StygiaBut alright, I'm giving up for now, I'll try again tomorrow.16:14
nerdboyStygia: should look like this on the target:
StygiaMaybe I'll see the error with more than a few hour sof sleep.16:14
nerdboyroot@raspberrypi:~# file /etc/localtime  =>  /etc/localtime: symbolic link to `/usr/share/zoneinfo/PST8PDT'16:14
BCMMbluelightning: thanks16:15
Stygianerdboy, Yea that's exactly what I expected, but it's not part of the image16:15
*** Stygia <Stygia!> has quit IRC16:15
nerdboythat's my default out of the build16:15
nerdboyfrom setting it in local.conf16:15
nerdboyanyway, go sleep on it16:16
BCMMdoes yocto have a network configuration file? by default, it seems to be just doing DHCP on eth016:16
kergoth /etc/network/interfaces16:16
nerdboymy package feed is public if you want to look later...16:16
BCMMkergoth: does that work like the one in debian?16:17
nerdboyBCMM: connman gets pulled in by some images16:17
kergothwe use ifupdown16:17
kergothour distros are debian based originally16:17
kergothnerdboy: good point16:17
nerdboytends to ignore interfaces16:17
BCMMkergoth: thanks. what's the correct way to automatically add my own interfaces file?16:18
nerdboybut yeah, without a network "manager" interfaces is it16:18
BCMMnerdboy: i haven't heard of connman before - basically like network manager with fewer dependancies and bloat?16:19
nerdboyless bloaty but even wonkier16:19
nerdboyif you can believe that...16:19
BCMMnerdboy: heh. any compelling reason not to just use the interfaces file + wpa_supplicant?16:20
nerdboyyou could install_append init-ifupdown if you need to replace the default16:20
nerdboynot at all, that's what i do in the rpi build...16:21
nerdboyworks fine that way16:21
BCMMnerdboy: ah, i'll probably just copy what you've done then. did you do the install_append thing?16:22
nerdboythe only oddity i've seen is the first boot of an image doesn't fire up networking on its own16:22
BCMMnerdboy: ah, that sounds like a problem for me - i'm doing an initramfs, so every boot is the "first boot"16:22
nerdboyifup -a one time and then everything is nominal after that16:22
nerdboyi should add that as a work-around to the configure script if its still there...16:23
kergothBCMM: netbase includes hte deafult interfaces file, you can bbappend it and alter FILESEXTRAPATHS to get it to use yours in your layer16:24
BCMMkergoth: thanks, that sounds like a pretty clean way to do it16:25
nerdboyseems like that file is owned by init-ifupdown...16:25
kergothhuh, guess it got moved16:25
*** belen <belen!Adium@nat/intel/x-dakuhtzpxbnhtmvp> has quit IRC16:25
nerdboylooks like there's a beagleboard append in bsp16:26
kergothhistorically its been in netbase, which is why so many layers broke when it was updated from 5.0 to 6.016:27
kergothnot that it really matters :)16:27
*** e8johan <e8johan!> has quit IRC16:27
* kergoth sighs and waits on another qt5 build16:28
BCMMnerdboy: last time i looked at your repo i didn't really understand how recipes work - why do you have your own mpd recipe?16:28
nerdboyhey, i can't be the only one getting corrected around here...16:28
*** sameo <sameo!~samuel@> has quit IRC16:28
nerdboyit's an append to add some config/packaging stuff16:29
nerdboymostly it adds my own init script16:29
BCMMnerdboy: you have a .bb and a .bbappend - what's the .bb do?16:30
nerdboyalso sets the volatile config and some perms16:30
nerdboyno .bb file for mpd16:30
nerdboywhat are you looking at?16:30
BCMMnerdboy: uh, the bb for mpc... sorry16:31
nerdboythat one didn't exist16:31
BCMMyeah, i just misread a letter16:31
BCMMnerdboy: also i noticed the stock recipe has no init script - i guess i'll use yours16:32
nerdboyi'm not using systemd16:32
nerdboyjust plain old sysvinit16:32
BCMMsame, i think - i meant the mpd recipe doesn't seem to install any kind of init script16:33
nerdboywhich was the initial reason for my bbappend...16:33
BCMMoh i see, you were warning me in case i needed whatever systemd uses instead16:34
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC16:35
*** OSNinja <OSNinja!> has joined #yocto16:36
nerdboysystemd is a distro feature16:37
*** francois99 <francois99!> has quit IRC16:38
BCMMnerdboy: i haven't got it enabled - i'm using sysvinit16:40
nerdboysome packages may not have a fallback init script16:40
nerdboyis there still a one-time configure script if you enable ROOTFS_READ_ONLY ?16:42
*** mihai <mihai!~mihai@> has quit IRC16:42
*** cetola <cetola!> has joined #yocto16:43
BCMMoh i see, stock MPD recipe has systemd configuration, but no sysvinit script16:43
BCMMnerdboy: sorry, i don't understand teh question16:43
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC16:43
nerdboysorry, not for you specifically16:43
BCMMoh ok. there's so much stuff i don't know yet about yocto that i couldn't tell whether it pertained to what i was doing16:44
kergothnerdboy: the read o nly rootfs support has changed substantially recently, though only for sysvinit. see the read-only-rootfs image feature16:44
kergothconfig files control on-boot bind-mounting of volatile paths over r/o locations, with automatic copying of the content in the r/o path into the volatile path16:45
kergothinteresting stuff.16:45
nerdboyso, kinda depends on how much tmpfs you can spare16:46
kergothwell, in theory you should be able to use non-tmpfs "volatile" path, e.g. a writable partition16:47
kergothneed to try doing that one of these days16:47
nerdboyget out of my head...16:49
*** gmacario <gmacario!> has quit IRC16:50
*** panda84kde <panda84kde!> has quit IRC16:53
*** smartin_ <smartin_!> has joined #yocto17:00
*** smartin <smartin!> has quit IRC17:01
*** jeremiah <jeremiah!~jeremiah@> has joined #yocto17:02
Garibaldi|workkhem: are you around — I hear you might be able to help with a problem I'm having building busybox for mips with DEFAULTTUNE = "mips64-n32"17:03
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto17:04
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@> has quit IRC17:04
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto17:05
*** zecke <zecke!> has quit IRC17:08
*** eren <eren!~eren@unaffiliated/eren> has quit IRC17:09
BCMMhow can i modify the behaviour of a .inc from another layer? do bbappends work17:12
BCMM(sorry, spurious newline) or is there some sort of .incappend?17:12
nerdboybbappend should do it, as long as you append the recipe that includes the .inc17:12
BCMMnerdboy: so bbappend the recipe that "require"s it, as if the inc was part of that file?17:17
kergothheh, i see the pr server threading improvements didn't fix the can't get PRAUTO failures17:20
bluelightningkergoth: RP is still working on it17:21
* kergoth nods17:22
*** acidfu <acidfu!~nib@> has joined #yocto17:29
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto17:29
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC17:31
*** slaine <slaine!~slaine@> has quit IRC17:33
mranostaymorning kergoth17:36
kergothdamn, the ruby recipe has a number of problems17:40
kergothmornign mranostay17:40
mranostaykergoth: how are the bits baking today?17:42
kergothanyone know how to print/query ruby's default library search path, ala python's sys.path?17:48
*** amarsman <amarsman!> has quit IRC17:49
*** zecke <zecke!> has joined #yocto17:51
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto17:52
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto17:54
-YoctoAutoBuilder- build #279 of nightly-mips is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #276 of nightly-ppc-lsb is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #118 of minnow-lsb is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #248 of nightly-fsl-ppc is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #289 of nightly-mips-lsb is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #275 of nightly-world is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #250 of nightly-fsl-arm-lsb is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #249 of nightly-fsl-arm is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #276 of nightly-ppc is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #275 of nightly-x86-64-lsb is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #281 of nightly-x86-lsb is complete: Exception [exception interrupted] Build details are at
kergothaha, there we are. ruby -e 'puts $:'17:55
-YoctoAutoBuilder- build #290 of nightly-intel-gpl is complete: Exception [exception Building Images] Build details are at
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC17:56
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto17:56
*** Anusko <Anusko!~anusko@> has quit IRC17:56
*** galak <galak!~galak@> has joined #yocto18:00
mranostayhi galak18:02
galakmranostay: hi, how's the new job?18:02
mranostayhaven't quit yet. so that has to say something :P18:02
mranostaygalak: going to ELCE?18:02
galakI will be18:02
galakreminds I need to register (got travel and hotel room setup)18:03
mranostaythe other hotel block closes today18:04
galakyeah, I got into The Caledonian18:04
galakI assume you'll be there based on asking the question18:05
mranostaygalak: know if beckyb is going as well?18:09
* zeddii still has no approval for elce, if I do go, I'll probably have to sleep on the street18:14
mranostayzeddii: Wind River?18:16
*** mihai <mihai!~mihai@> has joined #yocto18:17
* zeddii nods18:17
*** Krz_ <Krz_!c0c6972c@gateway/web/freenode/ip.> has quit IRC18:17
*** mulhern <mulhern!> has joined #yocto18:18
*** johnsoga <johnsoga!4542f923@gateway/web/freenode/ip.> has quit IRC18:18
kergothaha, confirmed that ruby-native suffers from a relocation bug18:24
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC18:24
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:24
*** zenlinux_ <zenlinux_!> has quit IRC18:28
msmzeddii: no one wants to see your presentation ;-)18:31
msmzeddii: they just want you to drink beer and entertain18:31
msmmranostay: becky's is doing ok.18:33
msmmranostay: as of wed lunch time18:34
zeddiimsm. pretty much, you must have put the word in on me. I keep getting rejected!18:35
* zeddii would go to just drink beer though18:35
msmim sure you would18:41
msmi would too ;)18:41
mranostaylabour day weekend is going to involved fixing my demo :P18:45
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto18:46
cfo215How much does one really learn at ELCE?18:46
wmcdevelis there a way to tell bitbake not to run the do_kernel_checkout task? my kernel source is in a tarball, so git checkout is unnecessary.18:47
kergothsounds like you should look at the linux-yocto-custom recipe, or don't use linux-yocto at all18:47
mranostaycfo215: ssssssh you'll ruin it for us :)18:48
cfo215mranostay, oh, so sorry... I'll keep a lid on it.18:48
wmcdevelkergoth: was basing my recipe on linux-yocto-custom. do I have to use linux-yocto?18:49
mranostaycfo215: you learn some but more networking18:49
cfo215too bad I don't have a corporate sponsor.  I was seriously considering it till I looked at airline tickets...18:50
cfo215I'm saving that cash for my trip to the Italian wine country...18:51
wmcdevelkergoth: essentially what I have in my SRC_URI is the tarball, and a poop-ton of patches from the board vendor. I can always make a git repo if that's the easiest way to get around it, but doesn't make sense to me to have to go that route18:54
zeddiiwmcdevel: what problem is the checkout causing ?18:56
zeddii-custom should have just worked, with no fuss.18:56
* zeddii looks back in history18:57
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-gprvaeggwizddwln> has quit IRC18:57
wmcdevelzeddii: Function failed: do_kernel_checkout .... tells me to look at the log file. Essentially, it's trying to do a git clone, but there is no git repo to clone from18:57
zeddiitgz is supported, what oe-core branch are you using ?18:58
wmcdevelzeddii: er ... not really sure. working with poky dylan18:58
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ogrwnumivzclnqyw> has joined #yocto18:59
zeddiilet me check. I always mess up the code names to version numbers.18:59
* zeddii wonders if that makes him evil18:59
zeddiiif it is dylan, and it isn't working then something broke. tgz should work just fine, or any type of archive that isn't a git repo.19:01
zeddiido you have a reproducer recipe ?I don't need your patches, just the location. I'll cook up my own as well.19:01
wmcdevelum, reproducer recipe?19:02
* mranostay hunts for a printers19:02
wmcdevelsorry, <-- noob19:02
zeddiiwmcdevel. the recipe that you are trying to build that is based on linux-yocto-custom. I'd like to see it break here, so I can debug.19:03
wmcdevelahh .. gotcha19:03
wmcdeveljust a sec ... let me see if I can pastebin it19:03
wmcdevelzeddii: and just for reference sake, building on Ubuntu 12.04 x86_6419:07
*** tor <tor!> has quit IRC19:08
wmcdevelzeddii: recipe name, files stored in linux-friendlyarm-
zeddiinp. firing up a build.19:10
*** mulhern <mulhern!> has quit IRC19:10
wmcdevelkk. gonna reload the caffeine feed then ... brb19:10
*** mulhern <mulhern!> has joined #yocto19:14
wmcdevelzeddii: any luck?19:20
zeddiihah. fat fingered it, was just correcting my recipe. I had started a 3.10 build with a xz.19:22
wmcdevel:) well, at least it isn't the compression scheme that's the problem.19:23
zeddiidefinitely not.19:23
*** simar <simar!~simar@> has quit IRC19:23
* zeddii waits19:24
wmcdevelI really like the build system, but there is so much documentation, it's almost as bad as no documentation. wish there were more concrete snippets for doing certain tasks19:24
zeddiithat's something which is continually improving. meta-skelton, etc. and labs19:25
zeddiibugger. I forgot to put the checksum19:25
*** erbo <erbo!> has quit IRC19:28
*** simar <simar!~simar@> has joined #yocto19:29
*** erbo <erbo!> has joined #yocto19:31
*** cfo215 <cfo215!> has quit IRC19:33
*** JimBaxter <JimBaxter!> has quit IRC19:35
BCMMi'm trying to modify a recipe with a bbappend, and want to add a custom file. how can i modify the path that the recipe looks in for file:// urls?19:36
zeddiiFILESEXTRAPATHS_prepend :=19:37
zeddii(or whatever variant you prefer)19:37
BCMMzeddii: thanks19:38
BCMMzeddii: i guess the _prepend means i can use my layer to override existing files?19:38
zeddiiit means that whatever directories you add would just be first in the search path.19:38
zeddiiwith the obvious addition that FILESEXTRAPATHS is already in addition to the system / built in search dirs19:39
zeddiiwmcdevel, my test on master worked. I'm checking out dylan to see if it was broken then.19:39
*** mulhern <mulhern!> has quit IRC19:40
wmcdevelzeddii: ok19:40
*** simar <simar!~simar@> has quit IRC19:41
zeddiigive me a few mins, fetching linux-
BCMMzeddii: uh, what is FILESEXTRAPATHS_prepend := relative to?19:42
wmcdevelok. not sure if that was on or if I got it from the vendor's DVD19:42
zeddiiwmcdevel, I found it, no worries.19:42
zeddiias an example: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"19:42
zeddii${THISDIR} is the directory of the recipe19:43
zeddiiPN is the recipe name (typically).19:43
zeddiiso if it is relative to the recipe, anchor it with ${THISDIR}19:43
BCMMzeddii: if i'm in a bbappend, does THISDIR refer to the append or the original recipe?19:43
BCMMthanks, that should solve my issue19:44
kergothTHISDIR is the dir of the currently parsed file. if you forget to use :=, it'll be the recipe directory rather than the bbappend directory, since it forces it to get the *current* value then and there, rather than expanding lazily as usual19:45
* zeddii nods. kergoth has all the details19:46
*** mulhern <mulhern!> has joined #yocto19:46
zeddiiI didn't point out the significance of := in the example.19:46
* zeddii is the laziest checksum updater around. fetch. fail. cut and paste.19:46
*** cfo215 <cfo215!> has joined #yocto19:50
wmcdevelis there a way to clean the build directory of a given recipe without affecting anything else?19:52
kergothzeddii: hey, lazy can be a good thing :)19:53
kergothbitbake -c clean recipe19:53
kergothwell, taht *removes* the build dir, the entire workdir19:53
kergothso depend son what you want19:53
wmcdeveljust want to remove the build directory for my kernel19:54
BCMMuh, really stupid question: what language are .bb recipes in?19:55
zeddii"bitbake", python, shell (depending on the function you are looking at).19:59
BCMMah, i'd sort of assumed it was all a shell script20:00
zeddiia lot is.20:01
zeddiidepends on who writes a recipe I suppose20:01
zeddiiwmcdevel, isn't a shell sript, but functions/tasks defined in it can be20:01
zeddiithat recipe worked for me. I think you are missing some required elements that led to an error that looked like a git clone/fetch20:02
zeddiiwmcdevel, I'll add some extra checks.20:02
wmcdevelzeddii: cool ... trying now20:03
zeddiiyou can convert it back to your local file:// variant .. but I fetched right from korg.20:03
wmcdevelok. will I need an md5/sha256 checksum for all my patches as well?20:04
zeddiiprobably not if you switch to file://, I'm not a fetcher wizard.20:05
zeddiiwmcdevel, the big missing line was S="${WORKDIR}/linux-"20:05
wmcdevellol ... ok20:05
zeddiiassuming that vendor tgz hasn't done something crazy with the directory names20:05
* zeddii mutters about shooting them if they did20:05
wmcdevelha ... I'm right with ya on that one. don't even get me going on "vendor support" ... *grumble grumble grumble*20:06
wmcdevelok, well it didn't bork right away on the do_kernel_checkout, so let's see if it completes the build this time20:09
wmcdevelstill patching ... will have to combine a number of them to not have patch called 150+ times20:14
*** OSNinja <OSNinja!> has quit IRC20:16
*** cfo215 <cfo215!> has left #yocto20:18
*** ant_home <ant_home!> has joined #yocto20:18
* zeddii heads out for the weekend.20:20
wmcdevelzeddii: thanks for the help :)20:20
zeddiino problem. I've added a check to give a decent error message for the case you hit.20:20
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ogrwnumivzclnqyw> has quit IRC20:20
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto20:23
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC20:25
kergothHmm, I'm a little concerned about _remove's semantics. If a low priority bbappend removes something, and then a higher priority bbappend appends something, the lower priority removal will win, as far as I can tell from the implementation20:25
j8|awayi grabbed a fix for the kernel configuration in linux-yocto by specifying a SRC_REV_meta... it grabs the fix and a few other changes, but now the kernel configuration says 3.8.11 whereas it was 3.8.4 (and the kernel remains 3.8.4). anyone foresee problems?20:26
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto20:27
mranostaygalak: btw that block just sold out20:28
galakglad I booked it when I did20:29
*** cetola <cetola!> has quit IRC20:29
*** cetola <cetola!> has joined #yocto20:29
wmcdevelstill patching ... "validating against known patches (icp-arm-standard-meta)" coming up on about 20 minutes, and only 27% along. is that normal? what known patches would it be validating against?20:32
BCMMhow would i go about making a PACKAGECONFIG key control more than one ./configure option?20:35
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-rkihrmaysgdgxoto> has joined #yocto20:36
kergothBCMM: there's nothing anywhere in packageconfig that says you can only use one option20:36
kergothit just uses strings, it doesnt' care waht they contain20:36
BCMMoh right, just strings that are concatenated to teh command?20:36
kergothPACKAGECONFIG[foo] = "--enable-something --enable-something-else,--disable-something --disable-something-else,somedep,"20:37
kergoththere are multiple examples of this in oe-core20:37
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-rkihrmaysgdgxoto> has quit IRC20:40
*** j8|away is now known as j820:42
*** Garibaldi|work1 <Garibaldi|work1!~andydalt@nat/cisco/x-nzghhcljlxynusnj> has joined #yocto20:43
*** Jefro <Jefro!> has joined #yocto20:45
*** bluelightning <bluelightning!> has joined #yocto20:47
*** bluelightning <bluelightning!> has quit IRC20:47
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:47
*** pidge <pidge!> has joined #yocto20:48
*** jmdelos_ <jmdelos_!> has quit IRC20:50
*** jmpdelos <jmpdelos!> has joined #yocto20:50
*** galak <galak!~galak@> has quit IRC20:53
*** OSNinja <OSNinja!> has joined #yocto20:57
*** eren <eren!~eren@unaffiliated/eren> has quit IRC21:10
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto21:22
sgw_halstead: time to update the bugzilla with 1.5.1, 1.5.2 and 1.6 M1-M521:33
halsteadsgw_, Shall do.21:35
*** challinan <challinan!> has quit IRC21:36
halsteadsgw_, Do we need a 1.7?21:37
sgw_halstead: sure21:41
RPkergoth: "database table is locked"?21:41
*** silviof1 is now known as silviof21:46
halsteadsgw_, I think it's all set. 1.5.1 was already in there so my script failed. But I fixed it by hand.21:46
*** OSNinja <OSNinja!> has quit IRC21:47
sgw_halstead: sorry I should have checked those first.21:47
halsteadsgw_, I should have too.21:48
*** j8 <j8!~IceChat9@> has quit IRC21:48
*** seebs <seebs!> has joined #yocto21:49
halsteadsgw_, Let me know if you notice any problems.21:49
halsteadI'm heading into to Portland. I'll be back online in a bit.21:49
sgw_halstead: later21:51
*** zecke <zecke!> has quit IRC21:54
* kergoth wonders why the omap5 evm bits in the meta-ti-glsdk repo arent' in the main meta-ati repo21:55
*** cfriesen <cfriesen!> has joined #yocto22:07
cfriesenI just tried building current poky master branch and it failed on the subversion package...looks like version 1.7.10 is no longer available from the mirrors.  Can anyone point me to what needs to be changed, I'm brand new at yocto.22:08
*** Garibaldi|work1 <Garibaldi|work1!~andydalt@nat/cisco/x-nzghhcljlxynusnj> has quit IRC22:09
RPhmm, have a lovely reproducer for PR server issues. Add in logging and it stops reproducing22:20
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC22:23
*** OSNinja <OSNinja!> has joined #yocto22:37
wmcdevelcfriesen: haven't tried anything with the master branch, but if you check out the dylan release/tag, that does work22:47
bluelightningRP: damned heisenbugs22:51
wmcdeveljust in case zeddii reads through the logs later, a major thank you for the help today ... kernel recipe builds now without error. w00t!22:53
wmcdevelhave a great weekend all22:53
*** wmcdevel <wmcdevel!> has left #yocto22:53
*** davest <davest!Adium@nat/intel/x-okqpsjlebtsmpqeq> has quit IRC22:54
*** tomz <tomz!> has quit IRC22:56
RPI've figured out part of the problem. In my tests, my PR server process is using 4GB of VM :/22:58
*** davest <davest!~Adium@> has joined #yocto22:58
RPwell, the part I figured out is the sqlite retry upon locked code is broken (the count to 500)22:58
RPThe 4GB of VM usage is due to forking the server off bitbake. I suspect it would be nicer to exec() it and be done22:59
RP(we end up with a server waiting in memory just in case the function exits which it can't)22:59
RPMy test case is 500 processes (48 at any one time) each making 5 calls to the PR server. Longest latency is 12 seconds23:01
kergothwouldn't the vast majority of that 4gb be shared, since its COW anyway?23:04
kergothhave you checked smem rather than ps/top?23:04
kergothits proportional set size is handy23:04
RPkergoth: the vast majority should be but its still a crazy size for the PR server considering what it does23:05
RPkergoth: Tried the standalone one and it also hits crazy sizes...23:05
kergothIt sounds quite unlikely that it'd dirty that much of the memory unless it's doing something crazy23:07
* kergoth shrugs23:07
kergothpython memory profiling time? :)23:07
*** davest <davest!~Adium@> has quit IRC23:08
RPkergoth: yes, time to get the profiler and look at this I think. Something just feels wrong...23:09
* kergoth nods23:10
kergothi found it helpful to inject an interactive python debugger session and inspect with meliae, though that'd be of limited use in the server without listening on a socket23:10
*** tomz <tomz!> has joined #yocto23:12
RPkergoth: I probably can just send it a dump command...23:13
kergoth looks promising23:13
* kergoth nods23:14
RPkergoth: it does look good, yes23:14
RPkergoth: and I have the code to launch an interactive python shell in task context too23:15
RPanyhow, Zzzz for now...23:15
* kergoth wonders why he never tried to get merged23:16
-YoctoAutoBuilder- build #280 of nightly-x86 is complete: Failure [failed Running Sanity Tests] Build details are at
*** smartin <smartin!> has joined #yocto23:20
*** smartin <smartin!> has quit IRC23:40
*** munch <munch!> has quit IRC23:45
-YoctoAutoBuilder- build #275 of nightly-arm is complete: Failure [failed Running Sanity Tests] Build details are at
*** ant_home <ant_home!> has quit IRC23:49

Generated by 2.11.0 by Marius Gedminas - find it at!