Friday, 2013-09-27

*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:05
*** jkridner <jkridner!> has joined #yocto00:05
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto00:05
*** flihp <flihp!> has quit IRC00:06
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto00:11
*** flihp <flihp!> has joined #yocto00:13
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC00:26
*** Jefro <Jefro!~jefro@> has joined #yocto00:29
*** RP <RP!> has quit IRC00:51
*** RP <RP!> has joined #yocto00:51
jwesselsgw_: I found the problem with the negative sized partition.00:55
jwesselTurns out if the disk initially has a bad label there is a bug in mkefidisk.sh00:55
jwesselIt will just write a msdos partition that is toast.00:56
*** Jefro <Jefro!~jefro@> has quit IRC01:04
sgw_jwessel: so there really was an issue, or just if I had a bad label?01:13
*** mebrown <mebrown!> has quit IRC01:19
*** mebrown <mebrown!> has joined #yocto01:19
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:22
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto01:23
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:24
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC01:27
*** silviof1 <silviof1!~silviof@unaffiliated/silviof> has joined #yocto02:02
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC02:04
*** nerdboy <nerdboy!> has joined #yocto02:10
*** seebs <seebs!> has quit IRC02:11
*** seebs <seebs!> has joined #yocto02:18
*** kmscherer <kmscherer!> has quit IRC02:25
*** nerdboy <nerdboy!> has quit IRC02:36
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto02:36
*** [simar|on] <[simar|on]!> has quit IRC02:45
*** andyross <andyross!> has joined #yocto03:10
*** Jefro <Jefro!> has joined #yocto03:27
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC03:38
*** Jefro <Jefro!> has quit IRC03:40
*** jackmitchell <jackmitchell!> has joined #yocto04:20
*** amarsman <amarsman!> has joined #yocto04:28
*** e8johan <e8johan!> has joined #yocto04:30
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC04:38
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto04:38
*** nrossi <nrossi!~nrossi@> has quit IRC04:52
*** nrossi <nrossi!~nrossi@> has joined #yocto04:54
*** andyross <andyross!> has quit IRC04:57
*** smartin_ <smartin_!> has joined #yocto04:57
*** andyross <andyross!> has joined #yocto04:59
*** mihai <mihai!~mihai@> has quit IRC05:04
*** silviof1 is now known as silviof05:06
*** andyross <andyross!> has quit IRC05:34
*** Jefro <Jefro!> has joined #yocto05:34
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC05:37
*** qt-x <qt-x!~ionel@> has joined #yocto05:51
*** tor <tor!> has joined #yocto06:01
*** eballetbo <eballetbo!> has joined #yocto06:12
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC06:24
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto06:25
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC06:25
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC06:28
*** mitz_ <mitz_!> has quit IRC06:36
*** Jefro <Jefro!> has quit IRC06:37
*** fpaut_ is now known as fpaut06:39
*** JaMa <JaMa!> has joined #yocto06:42
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto06:43
*** smartin_ <smartin_!> has quit IRC06:45
*** mitz_ <mitz_!> has joined #yocto06:48
*** ant_work <ant_work!> has joined #yocto06:49
*** B4gder <B4gder!> has joined #yocto06:53
*** mckoan|away is now known as mckoan06:57
mckoangood morning06:57
*** elmi82 <elmi82!> has joined #yocto07:04
*** zeeblex <zeeblex!~apalalax@> has joined #yocto07:04
*** blitz00 <blitz00!~stefans@> has joined #yocto07:07
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto07:07
*** pirut <pirut!~Pirut@> has quit IRC07:12
*** n01 <n01!> has joined #yocto07:12
*** slaine <slaine!~slaine@> has joined #yocto07:13
*** pirut <pirut!Pirut@nat/intel/x-jnvldzboikkfmvmo> has joined #yocto07:14
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC07:19
*** Zagor <Zagor!> has joined #yocto07:22
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto07:22
TuTizzHi, I wrote my own recipe, it source had to be download from a svn, each time I update my revision number I modify the bbfile with the new revision number but it look like nothing append to my final image. Should I do something more to specify my update?07:22
*** bluelightning <bluelightning!~paul@> has joined #yocto07:25
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:25
*** sameo <sameo!~samuel@> has joined #yocto07:25
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:26
ndecTuTizz: did you add your package in the image?07:26
TuTizzndec, yes I did07:29
ndecTuTizz: when you rebuilt your image after the REV update, does it actually re-fetch, and re-build your recipe?07:29
ndecTuTizz: also, this is obvious, but you need to bitbake the image not the recipe when you update the REV.07:30
TuTizzfor a concret example, I moved my LICENSE.LGPL to a different folder and specify his new position with LIC_FILES_CHKSUM = "file://LICENSE.LGPL;md5=fbc093901857fcd118f065f900982c24"07:31
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto07:32
TuTizzbitbake end with the same previous error and trying to find the file on the old position07:32
*** smartin <smartin!~smartin@> has quit IRC07:33
ndecTuTizz: and you changed SRCREV too?07:33
*** smartin <smartin!~smartin@> has joined #yocto07:34
TuTizz:( I don't have any SRCREV07:34
ndechow do you set PV?07:35
TuTizzI believed that it was automatic07:38
ndecTuTizz: no, it is not.07:40
ndecin general if you get from svn or git, you need to add SRCREV (the revision) to PV.07:40
ndecso that bitbake will detect when it needs to re-fetch from svn07:40
ndecthere are many example of SRCREV usage in tree.07:41
TuTizzok thank you ndec :)07:42
ndecTuTizz: btw, you can to SRCREV="${AUTOREV}", in which case bitbake will automatically pick the last revision (or commit).07:43
ndecby quering the svn (or git) repo when 'parsing' the recipes.07:44
TuTizzndec, I saw I can do it in my local.conf, can I do it in my recipe directly?07:44
ndecyou need to set PV in your recipe ,for sure.07:45
ndecthen SRCREV can either be in recipe or in a conf file.07:45
ndecif you do it in a conf file, you need to do SRCREV_pn-<recipe> = "xxx"07:46
*** mihai <mihai!~mihai@> has joined #yocto07:47
*** e8johan <e8johan!> has quit IRC07:53
bluelightningmorning all07:56
TuTizzndec, perfect that exactly what i want to do :) that works with SRCREV="${AUTOREV}"08:00
TuTizzPV = "0.0.3"08:00
TuTizzPR = "r0"08:00
RagBalOn my first boot I'm getting a lot of these errors: ERROR: postinst /etc/rpm-postinsts/kernel-module-zte-ev failed.08:00
RagBalAll related to kernel modules08:00
RagBalSeems like depmod/depmodwrapper aren't shipped with the image, what recipe provides these?08:03
*** dany <dany!~Thunderbi@> has joined #yocto08:08
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC08:12
*** JimBaxter <JimBaxter!> has joined #yocto08:15
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto08:16
*** dany <dany!~Thunderbi@> has quit IRC08:29
RagBalAh found out it needs "kmod" =)08:41
-YoctoAutoBuilder- build #163 of minnow is complete: Success [build successful] Build details are at
*** markos_ <markos_!> has left #yocto08:42
RagBalBut I don't understand why it executes this on the first boot08:42
*** volker_ <volker_!~quassel@> has quit IRC08:51
*** volker <volker!> has joined #yocto08:51
*** yzhao2 <yzhao2!~yzhao2@> has quit IRC08:52
*** yzhao2 <yzhao2!~yzhao2@> has joined #yocto08:52
*** jackmitchell <jackmitchell!> has quit IRC08:58
bluelightningRagBal: have a look at your log.do_rootfs for the image, if they're running on first boot it means they failed to run during do_rootfs09:01
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto09:01
*** jackmitchell <jackmitchell!> has joined #yocto09:05
RagBalAhhh ok, I didn't get a warning about it during the build09:05
*** hugh_ <hugh_!43a16395@gateway/web/freenode/ip.> has quit IRC09:06
*** dany <dany!> has joined #yocto09:13
*** fpaut <fpaut!> has left #yocto09:33
*** fpaut <fpaut!> has joined #yocto09:40
mckoando we have a recipe for sftp in dylan? is openssh-sftp the right choice?09:45
bluelightningmckoan: it's what most people use AFAIK09:51
mckoanbluelightning: thx, and can openssh-sftp co-exist with dropbear?10:06
bluelightningmckoan: yes10:06
mckoanbluelightning: fine thx10:06
RagBalbluelightning, install/tmp/rpm-tmp.651: line 6: depmodwrapper: command not found << is in the log, so it indeed can't install the rpms10:07
RagBaldepmodwrapper is indeed not installed on my host system, it is Ubuntu 12.0410:08
bluelightningRagBal: it's not supposed to be on your host system, it's build by the build system10:09
*** elbc <elbc!2e12602e@gateway/web/freenode/ip.> has joined #yocto10:09
*** jackmitchell <jackmitchell!> has quit IRC10:09
RagBalHmm, not by my build =(10:09
bluelightningRagBal: can you please do bitbake -e your-image | grep ^DEPENDS= and tell me what the output is?10:10
RagBalDEPENDS="gzip-native qemuwrapper-cross depmodwrapper-cross"10:11
bluelightningok, so that bit is correct10:11
*** melonipoika <melonipoika!> has quit IRC10:12
bluelightningRagBal: you haven't been using the -b option have you?10:12
RagBalTo build the image? Nope10:13
*** jackmitchell <jackmitchell!> has joined #yocto10:13
bluelightningok, just checking10:13
RagBalbluelightning, this is the image recipe I use10:14
bluelightningRagBal: if you change that "include" to "require" does it still work?10:15
*** fpaut is now known as fpaut_10:15
RagBalbluelightning, yes it is building the image10:16
*** michael_e_brown_ <michael_e_brown_!> has joined #yocto10:17
TuTizzI want to create a new directory in /home/root how can I do? I tried install -d -m 755 ${D}/home/root/.debug but not sure10:18
TuTizz(during a do_install() { }10:18
*** mebrown <mebrown!> has quit IRC10:19
bluelightningRagBal: if you look in the path given by this command, does it contain depmodwrapper-cross? : bitbake -e | grep ^STAGING_BINDIR_CROSS=10:20
bluelightningRagBal: actually depmodwrapper not depmodwrapper-cross10:20
*** thaytan <thaytan!> has quit IRC10:21
*** thaytan <thaytan!> has joined #yocto10:21
RagBalNo such file or directory10:21
RagBalDoesn't exist10:22
*** dany <dany!> has quit IRC10:25
*** fpaut_ is now known as fpaut10:28
bluelightningRagBal: that directory ought to exist... is there anything unusual about this build?10:34
bluelightningRagBal: are there any depmodwrapper-cross files under /ssd/yocto/projects/smarct335x/tmp/stamps/ ?10:39
ant_workthe cross files are under host sysroot10:45
ant_worknot in target10:45
ant_worksmthg wrong there10:46
bluelightningant_work: bitbake -e depmodwrapper-cross | grep ^STAGING_BINDIR_CROSS= for MACHINE=qemux86 shows /path/to/tmp/sysroots/qemux86/usr/bin/crossscripts here10:51
bluelightningand that directory does contain depmodwrapper (and a load of other scripts)10:52
ant_workI see, it isn't a typical -cross recipe10:55
ant_workI'm always thinking about toolchains and crosscompilers.. I'm biased, sry10:56
bluelightningok, np10:56
ant_workthe recipe doesn't inherit cross10:56
ant_workso there isn't any magic with sysroots10:56
ant_workwhy is it called -cross btw?10:57
bluelightningnot entirely sure10:57
bluelightningwe do prefix it for multilib, FWIW10:57
*** abc <abc!c0c6972b@gateway/web/freenode/ip.> has joined #yocto10:58
bluelightningwell, without anything more to go on I'm not sure I can help....10:59
*** melonipoika <melonipoika!> has joined #yocto11:01
RagBalbluelightning, sorry I was eating my lunch11:03
bluelightningRagBal: sorry if I already asked previously, which branch is this? master/dylan/... ?11:03
RagBalI'm trying to build the BeagleBone Black kernel with Yocto11:04
bluelightningRagBal: what do you have set for DISTRO?11:04
*** rodgort <rodgort!> has quit IRC11:05
*** rodgort <rodgort!> has joined #yocto11:08
bluelightningRagBal: so you're using meta-beagleboard ?11:08
RagBalNo I'm a dirty boy, I copied the kernel recipe in my own layer11:09
bluelightningah ok11:10
bluelightningany other modifications?11:10
RagBalA few patches to the kernel, but nothing strange11:10
RagBalIt works fine with angstrom11:10
bluelightningok, it won't be an issue with the kernel recipe11:10
RagBalI'm not fond of my imge recipe11:11
RagBalDid you check the link I sent earlier?11:11
RagBalPerhaps I'm doing something wrong there11:11
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC11:14
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto11:14
*** michael_e_brown_ <michael_e_brown_!> has quit IRC11:15
*** mebrown <mebrown!> has joined #yocto11:15
bluelightningRagBal: I did have a look at it; apart from the IMAGE_INSTALL the rest shouldn't be needed since you're including/requiring core-image-minimal recipe11:19
bluelightningbut that shouldn't cause the problem you're seeing11:19
bluelightningFWIW, I am running a dylan build here with your image recipe, but to be honest I don't expect it will reproduce the problem; we'll see11:21
bluelightningRagBal: did you see my question above re stamps?11:22
RagBal./smarct335x-poky-linux-gnueabi/depmodwrapper-cross <<< Yes11:24
RagBalAnd some task files11:24
bluelightningok, so it does think that it built11:25
bluelightningwhich is what youd expect given that it apparently hasn't tried to build it11:25
bluelightningyou haven't used any scripts to delete parts of tmp/ or deleted any part of that by hand?11:25
RagBalWouldn't dare to taint it =)11:26
bluelightningwell I need to grab some food and I'll be back in a bit11:26
RagBalI can completely rebuild the entire thing11:26
bluelightningone thing to try might be to move the tmp directory out of the way and then rebuild, yes11:26
RagBalWill do11:26
bluelightning(move rather than delete so we still have it for reference)11:26
RagBalRoger, enjoy your food, and thanks so far11:27
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC11:31
*** michael_e_brown_ <michael_e_brown_!> has joined #yocto11:36
*** mebrown <mebrown!> has quit IRC11:37
*** volker <volker!> has quit IRC11:38
-YoctoAutoBuilder- build #280 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at
elbcrburton: hi ! I have my image working pretty good now, but I recently saw that it was still the libx11.rpm present in the installed packages. so my question is : how to remove a package from my image or how to know which package has needed it when built ?11:53
rburtonelbc: did you remove x11 from your distro features?11:53
rburtonthen it didn't work as if you did, it will *refuse* to build libx1111:54
rburtonrun bitbake -e |grep DISTRO_FEATURES=11:54
elbcrburton:  no trace of x11 at all11:56
rburtonwhat's your evidence that libx11 is in your image?11:58
rburtoni.e. do you have /usr/lib/*11:58
elbcrburton: I did gedit tmp/work/chiefriver-poky-linux/core-image-weston/1.0-r0/installed_pkgs.txt and I found libx11 in it11:59
rburtoncheck the rootfs too in that directory12:00
rburtonits possible that it found the packages hanging around from when you didn't have it enabled, and they got pulled in through recommends12:00
elbcrburton:  no traces at all of x11 in /usr/lib but there is in /media/sda1/usr/lib/12:02
elbcrburton:  does it mean it is not efficient ?12:03
rburtonwhat? there's a /media/sda1/usr/lib path inside the rootfs?12:03
elbcit seems to be yes12:04
rburtonwell that's messed up12:05
elbcrburton:  ?12:05
*** mebrown <mebrown!> has joined #yocto12:05
elbcrburton:  sorry my english is not very good12:05
rburton /media is for mounting media on, so it should be an empty directory in the rootfs12:05
elbcrburton:  oh sorry12:05
*** michael_e_brown_ <michael_e_brown_!> has quit IRC12:06
elbcrburton: in the rootfs yes it is empty12:06
elbcrburton: but when I do a find . -name "*x11*" or "*X11*" on my target12:06
rburtonright, so its picking up whatever you plugged in12:06
elbcit founds some X11 file in /media/sda1/usr/lib/12:06
elbcrburton: sorry ?12:07
elbcrburton: does it mean libx11 is not really installed ?12:07
rburtonif there's not a /usr/lib/* in your target filesystem, then its not installed.12:09
elbcrburton:  ok ! thank you very much12:09
rburtonelbc: hm, are you booting from eg usb on a machine that has a different distro on the harddisk?12:11
bluelightningRagBal: back12:11
RagBalbluelightning, the image is still building. Takes longggg12:11
RagBal(996 of 2336)12:11
bluelightningRagBal: in your old tmp directory do you have work/smarct335x-poky-linux-gnueabi/depmodwrapper-cross/ ?12:11
bluelightningRagBal: ok, what does it have in it?12:12
RagBalFolders: "deploy-rpms depmodwrapper-1.0 image license-destdir package packages-split pkgdata pseudo sysroot-destdir temp"12:13
RagBalAnd a file depmodwrapper-cross.spec12:13
*** fenrig <fenrig!c1bf9602@gateway/web/freenode/ip.> has joined #yocto12:16
*** fenrig <fenrig!c1bf9602@gateway/web/freenode/ip.> has left #yocto12:16
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto12:17
bluelightningRagBal: ok, could you pastebin temp/log.do_populate_sysroot from there assuming that exists?12:19
RagBalThe logfile is dated yesterday12:23
*** vmeson <vmeson!~quassel@> has quit IRC12:23
bluelightningRagBal: and presumably sysroot-destdir contains usr/bin/crossscripts/depmodwrapper ?12:25
*** vmeson <vmeson!~quassel@> has joined #yocto12:26
*** qt-x <qt-x!~ionel@> has quit IRC12:28
bluelightningwell, that is strange12:30
bluelightningso it definitely did stage the file, and yet not only is it not there, the entire directory is missing12:30
*** qt-x <qt-x!~ionel@> has joined #yocto12:31
RagBalIn the new build the folder is created12:32
bluelightningright... I think it was created in the previous build and somehow it was removed after that12:33
RagBal/ssd/yocto/projects/smarct335x/tmp/sysroots/smarct335x/usr/bin/crossscripts <<< that is12:33
bluelightningI don't know how that could happen though12:33
RagBalVery weird indeed12:33
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC12:33
RagBalPerhaps I messed stuff up when I forgot to "inherit image" in the recipe yesterday12:34
*** melonipoika <melonipoika!> has quit IRC12:34
bluelightningI don't see how that could cause this12:34
bluelightningif depmodwrapper hadn't been built at all it might have helped explain it, but it did build12:35
RagBalI did clean/cleansstate on the recipe12:35
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC12:41
*** jkridner <jkridner!~jkridner@> has joined #yocto12:46
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto12:46
elbcrburton:  I have some build errors when trying to build libva-intel-driver : (and I'm sure to know what is expected)12:55
elbc(not sure sorry)12:55
*** kmscherer <kmscherer!~kscherer@> has joined #yocto12:55
rburtonnothing i've seen before, you'll have to debug that yourself.12:56
Krz-I have a simple recipe to copy grub.conf over to tmp/deploy/images/.. :
Krz-I used suggested by bluelightning do_deploy[nostamp] = "1"13:01
Krz-but 'bitbake grub-conf' just does not kick my do_deploy function13:01
Krz-I have to cleanall and then bitbake once again13:01
Krz-so basically do_deploy[nostamp] = "1" doesn't do what I would like it to do - kick off do_deploy function ALWAYS13:02
bluelightningthat is exactly what nostamp is supposed to do13:02
bluelightninghave you tried moving nostamp after the function definition?13:03
Krz-bluelightning, yes, I tried it does not change anything13:04
Krz-bluelightning: maybe I have some other settings in my layer wrong? like layer priorites, BBPATH, etc?13:04
bluelightningok, changing the order wouldn't help looking at examples we have13:05
bluelightningnope, that wouldn't be able to influence this I don't think13:05
Krz-bluelightning: maybe it doesn't like the fact, that do_deploy is non-standard function, but manually added?13:06
bluelightningKrz-: do_deploy isn't a "standard" function, everywhere it's used it's added in this manner13:06
elbcrburton: ok thanks13:07
Krz-bluelightning: yeah, that's my point. greping for do_deploy[nostamp] in poky/ shows zero results13:07
bluelightningtypically we would not make that function nostamp13:07
bluelightningthat doesn't mean it shouldn't work though13:08
Krz-bluelightning: maybe nostamp works only for functions like install/compile/build which are standard functions13:08
bluelightningno, I know that it works for any function13:08
Krz-bluelightning: ok13:08
Krz-bluelightning: I know Yocto can create somehow grub.conf as well. If that mechanism can put my grub.conf under tmp/deploy/images/... then I might switch to it13:09
Krz-bluelightning: I just need any working solution which will place valid grub.conf there13:10
bluelightningKrz-: ok having just tried it, I can see what is going on13:12
bluelightningKrz-: nostamp is working; however deploy.bbclass marks this as an sstate task so it tries to run it, sees that none of its inputs have changed and therefore just restores it from sstate-cache13:13
bluelightningKrz-: why do you need this to run every time?13:13
Krz-bluelightning: it needs to be created everytime user builds an image, even after wipeing-out images/ directory13:14
bluelightningKrz-: ok... well, unintentionally this recipe is both poking into DEPLOY_DIR and expecting sstate to manage files it puts there13:16
bluelightningKrz-: so you have two choices, either change your do_deploy to put things in DEPLOYDIR (as defined by deploy.bbclass) instead of DEPLOY_DIR_IMAGE, or don't inherit deploy13:18
*** abelloni <abelloni!> has quit IRC13:19
*** kmccombe <kmccombe!> has joined #yocto13:19
*** panda84kde <panda84kde!> has joined #yocto13:20
Krz-bluelightning: not inheriting deploy works perfect13:26
RagBalbluelightning, working perfectly now thank you!13:27
RagBalbluelightning, it's not giving the rpm installation during boot13:27
*** abelloni <abelloni!> has joined #yocto13:28
bluelightningRagBal: I'm still confused about how it got into that state though13:29
*** dany <dany!> has joined #yocto13:33
*** Crofton <Crofton!> has quit IRC13:40
*** B4gder <B4gder!> has quit IRC13:41
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-qehtovrlsmxwryte> has joined #yocto13:45
*** belen1 <belen1!Adium@nat/intel/x-kwvpfquqgvtovttm> has joined #yocto13:51
*** mihai <mihai!~mihai@> has quit IRC13:53
*** volker <volker!> has joined #yocto13:54
*** kmccombe <kmccombe!> has quit IRC13:55
*** belen1 <belen1!Adium@nat/intel/x-kwvpfquqgvtovttm> has quit IRC13:56
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto13:59
*** kmccombe <kmccombe!> has joined #yocto14:01
*** belen1 <belen1!~Adium@> has joined #yocto14:03
*** dany <dany!> has quit IRC14:04
*** eren <eren!~eren@unaffiliated/eren> has quit IRC14:09
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC14:10
*** vmeson <vmeson!~quassel@> has quit IRC14:12
*** qt-x <qt-x!~ionel@> has quit IRC14:12
*** kmccombe <kmccombe!> has quit IRC14:14
*** vmeson <vmeson!~quassel@> has joined #yocto14:20
*** slaine <slaine!~slaine@> has quit IRC14:22
*** munch <munch!> has joined #yocto14:23
*** fpaut is now known as fpaut_14:23
*** slaine <slaine!~slaine@> has joined #yocto14:23
*** Jefro <Jefro!> has joined #yocto14:36
*** vducuy <vducuy!734e07cb@gateway/web/freenode/ip.> has joined #yocto14:41
vducuyhi all, i got error when use Linux-yocto-3.1014:42
vducuyFetcher failure for URL: 'git://;bareclone=1;branch=standard/base,meta;name=machine,meta'14:42
vducuywith linux-yocto-3.8 it is ok14:42
vducuydoes it mean failure from git server?14:43
*** mckoan is now known as mckoan|away14:43
bluelightningvducuy: which machine are you building for?14:51
bluelightningzeddii: ^14:51
*** nrossi <nrossi!~nrossi@> has quit IRC14:51
*** nrossi <nrossi!~nrossi@> has joined #yocto14:52
zeddiifetcher failure. smells like infrastructure on the servers. unless there's a bitbake error about branches missing, etc.14:54
Krz-can I change the order of evaluating variables from: my.conf files?14:58
*** eballetbo <eballetbo!> has quit IRC14:59
jwesselant_work: ping15:02
*** belen1 <belen1!~Adium@> has quit IRC15:02
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC15:03
*** TuTizz <TuTizz!~TuTizz@> has quit IRC15:03
*** michael_e_brown <michael_e_brown!~michaeleb@> has quit IRC15:03
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto15:04
*** belen1 <belen1!Adium@nat/intel/x-wpbmiaeodqhmbboh> has joined #yocto15:04
vducuybluelighting: i tried my own machine and also beagleboard.15:06
vducuythe same problem15:06
*** andyross <andyross!> has joined #yocto15:11
*** tor <tor!> has quit IRC15:16
*** forcev <forcev!> has joined #yocto15:17
*** galak <galak!> has joined #yocto15:18
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC15:19
*** elmi82 <elmi82!> has quit IRC15:19
ant_workjwessel: pong15:22
jwesselzeddii sent me your conf.tar.gz and I was going to have a look at the failure.15:23
jwesselI assume I Just have to build: linux-yocto-tiny-kexecboot  ?15:23
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:23
jwesselok.  The build in progress in that case.  I imagine we'll either use your patch or at least get to the stage where all the various cases work again.15:24
ant_workjwessel: I'm maybe retarded but cannot yet grasp the real issue with signed modules you have :)15:25
jwesselI doubt that.15:25
jwesselIt is quite possible that the module singing is not working in the first place with the monolithic kernel.15:26
ant_worktbh I avoid signed mods like pest  ;)15:26
jwesselIt is not so much module signing as it is modversions being in use.15:26
jwesselThis prevents the modules from loading if they are not the right ones for the kernel.15:27
ant_workjwessel: yes, sorry for the imprecision15:27
jwessel|   /space/jw/yocto/oe-core/andrea/build/tmp-eglibc/work/c7x0-oe-linux-gnueabi/linux-yocto-tiny-kexecboot/3.10.11+gitAUTOINC+dad2b7e1ce_e1aa804148-r0/linux/scripts/ Cannot open 'initramfs.cpio.lzma'15:27
jwesselIs that the typical failure you see?15:27
ant_workyes, is the patch for kernel_do_configure()15:28
ant_works/is/is solved by/15:29
ant_workjwessel: I have tried the two steps builds but I didn't set INITRAMFS_IMAGE in local.conf. I just cannot do that, it would pollute any other kernel/image15:30
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has quit IRC15:30
jwesselI believe you can set the INITRAMFS_IMAGE else where.15:30
ant_workjwessel: try to remove CONFIG_INITRAMFS_SOURCE from the config: the error would disappear but the image would not be embedded, not built15:32
*** hollisb <hollisb!> has joined #yocto15:32
ant_work(well, if youeven remove INITRAMFS_TASK ofc)15:32
*** Stygia <Stygia!> has joined #yocto15:34
jwesselOf course because the CONFIG_INITRAMFS_SOURCE is what causes it to merge the image in.15:35
jwesselI'll get back to you in a few hours.  I plan to get to the bottom of this today, but also have some other things going on.15:36
ant_workwell, it should be triggered by INITRAMFS_IMAGE_BUNDLE15:36
*** joeythesaint <joeythesaint!~jjm@> has joined #yocto15:36
jwesselNow that I have the problem sitting on my desk as well as the other use cases, we should be able to make it work.15:36
ant_workjwessel: thx in advance15:37
Krz-I'm totally lost with fighting with IMAGE_FSTYPES = "live" declared inside image recipe. It is just not picked up even if bitbake myimage -e says it's there.15:37
Krz-Tried setting this inside python __anonymous inside the same image recipe - doesn't get picked up as well15:38
Krz-I just have two different images, and one must be "live ext3", second must be "cpio.lzma cpio.gz".15:38
jwesselKrz-: I had only ever used the IMAGE_FSTYPES += "live" in the local.conf15:38
Krz-it looks like live works only from conf file15:39
jwesselI have had all sorts of problems trying to build "live vmdk"  for example.15:39
jwesselOne completely pollutes the other.15:39
Krz-so it means either I build live for both images, or not at all :|15:39
*** hollisb <hollisb!> has quit IRC15:40
jwesselI am not sure if you can set it in the image recipe or not.  It was never entirely clear to me how this part of bitbake was intended to actually work.15:40
jwesselIt might also be the case that the various inherits cause the breakage as well.15:40
Krz-whatever value of IMAGE_FSTYPES I set in myimage recipe: bitbake myimage -e shows correctly and builds wrongly15:41
jwesselI had always thought you could just set the as many fstypes as you want and get certain images.  In reality I came to the conclusion of just using multiple build directories.15:41
ant_workjwessel: I guess we have INITRAMFS_FSTYPES for the same reason15:41
jwesselKrz-: Perhaps open a bug on it and send some mail to the list.  I am not sure if it is a bug or "feature".15:42
*** Stygia <Stygia!> has quit IRC15:43
*** ScriptRipper1 <ScriptRipper1!> has joined #yocto15:43
vducuyzeddii: can we check if any problem at server site? tried and see no problem with linux-yocto-3.815:43
Krz-can I kick off 'live' image build other than by specyfing 'IMAGE_FSTYPES' ?15:53
Krz-like IMAGE_EXTRADEPENDS = "core-image-minimal-rootfs" ?15:54
*** belen1 <belen1!Adium@nat/intel/x-wpbmiaeodqhmbboh> has quit IRC15:56
bluelightningFWIW, I just set IMAGE_FSTYPES += "tar.gz" in an image recipe on dylan and it worked15:57
bluelightningjust trying with live now15:57
*** belen1 <belen1!~Adium@> has joined #yocto15:59
zeddiivducuy, just a manual clone should test it. I just tried one and it looks to be cloning fine, with some throttling, but otherwise fine.15:59
Krz-bluelightning: all but live inside image recipe works for me16:00
ant_workKrz-: pls use IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"16:00
ant_workand define the latter in your machine.conf16:00
ant_workso i.e. the image will have only cpio's16:00
Krz-ant_work: my machine.conf applies to both images16:00
ant_workyes, but one image uses INITRAMFS_FSTYPES16:01
ant_workit works here16:01
Krz-well, right, the second image uses cpio.lzma and cpio.gz16:01
Krz-so I can do that for one image16:01
*** kspr <kspr!> has joined #yocto16:03
Krz-ant_work: but... does INITRAMFS_FSTYPES affect live image? since live image I need only in .cpio.gz version :)16:03
*** n01 <n01!> has quit IRC16:03
*** Stygia <Stygia!> has joined #yocto16:05
ant_workKrz-: in our machine conf we have INITRAMFS_FSTYPES ?= "cpio.gz cpio.lzma" and in our image IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"16:06
ant_workso if you want you can have an higher policy16:06
ant_worklike defining in local.conf16:06
ant_worktbh I never tried 'live' as well ;)16:07
Krz-ant_work: I can always tweak in core-image-minimal... bbappend, so that's not a problem16:07
ant_workah ha16:08
*** Stygia <Stygia!> has quit IRC16:11
*** hollisb <hollisb!> has joined #yocto16:12
ant_workback then the problem was 'live' and core-image-minimal-initramfs16:13
*** Stygia <Stygia!> has joined #yocto16:14
*** hollisb <hollisb!> has quit IRC16:15
bluelightningKrz-: I think I've figured out what might be going wrong - try moving the IMAGE_FSTYPES assignment above the "inherit image" or "inherit core-image" line in your image recipe16:15
jwesselant_work: I have the patch for your use case.16:15
jwesselI'll send it shortly.  I saw the problem right after we chatted but had to go to a meeting.16:16
jwesselI just tested the patch and it worked, so perhaps you can give it a spin too.16:16
*** hollisb <hollisb!> has joined #yocto16:16
ant_worksure, in a couple of hours16:16
jwesselNo worries.  :-)16:16
ant_workjwessel: eh.. we have to hurry up or the merge windows will be closed :/16:17
ant_workRP: ^^ ;)16:17
jwesselWell this is a regression.16:17
jwesselIt would be fixed as a defect, with high priority, which is what I am doing.16:17
ant_workthx, it needs at least one autobuilder run says RP16:18
jwesselNone of the autobuilders will hit this code, but what he said is also true.16:18
jwesselWe simply don't have a test case for this in what the autobuilder line up executes.16:18
jwesselOr it would have been found already.16:18
ant_workI think we and zeddii are the only knoen users...16:19
ant_workoh, JaMa's autobuilder as well16:19
abcbluelightning: it's Krz here, moving IMAGE_FSTYPES above inherits works perfect16:20
ant_workrighto, it was redefined by the include16:20
bluelightningabc: ah ok... the way live images are implemented internally is kind of weird, so they are a bit special16:20
ant_worksry wrong windows16:21
*** francois99_ <francois99_!> has quit IRC16:21
* ant_work lured an arm-soc kernel to OE/Yocto today16:23
ant_workkernel-dev even16:23
ant_workwhat's the reward ?;)16:24
jwesselant_work: The patch is sent to oe-core, thanks for sending the failure case to zeddii, who sent it to me.16:24
*** abc <abc!c0c6972b@gateway/web/freenode/ip.> has quit IRC16:24
jwesselIt made it very easy to diagnose how to fix it.16:24
bluelightningant_work: if he gets h3600 going on a modern kernel, I owe you both beers16:25
ant_workjwessel: did he send you the pic of the 20Mib kernel embedding core-image-base16:25
jwesselant_work: No, I didn't see any pic's.16:25
*** belen1 <belen1!~Adium@> has quit IRC16:27
ant_workbluelightning: he didn't know about kernel-tools16:27
bluelightningant_work: I'd settle for mainline as well16:28
ant_workupstream they are trying to unify: less kernels and devicetrees16:28
ant_workmaybe he'll convert old PXA16:28
bluelightningthat would be neat too16:30
ant_workjwessel: one question about cpio compression: why do you need to handle it?16:30
*** zenlinux <zenlinux!> has quit IRC16:31
jwesselant_work: No idea.  Someone on zeddii's team wrote that patch.16:31
ant_workold code could manage .gz and .lzma w/out issues16:31
jwesselI had to clean it up and make it work with the dependency stuff.16:31
jwesselIf zeddii says it is not needed, lets dump it.  I don't like keeping kruft.16:31
ant_workiirc RP asked about it as well16:32
jwesselSame answer was provided too.  All my test cases passed with and without that part.16:32
*** zenlinux <zenlinux!> has joined #yocto16:32
*** zeeblex <zeeblex!~apalalax@> has left #yocto16:33
ant_workok, I'll test with and without once more16:33
ant_workheading home now, be back later16:33
*** ant_work <ant_work!> has quit IRC16:33
*** jackmitchell <jackmitchell!> has quit IRC16:34
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC16:39
*** Stygia <Stygia!> has quit IRC16:41
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:43
*** pev <pev!~pev@> has joined #yocto16:48
pevAfternoon! Hopefully an easy question - I've added in an SPI flash MTD driver, seems to detect flash OK, /proc/mtd lists the partitions but yocto doesnt create /dev/mtdX for me. What's the standard way of going about creating hte mtd devnodes under yocto?16:51
*** acidfu <acidfu!~nib@> has joined #yocto16:52
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto16:52
*** belen1 <belen1!~Adium@> has joined #yocto16:55
*** fenrig <fenrig!> has joined #yocto16:56
*** sameo <sameo!~samuel@> has quit IRC16:58
*** seebs <seebs!> has quit IRC17:14
*** seebs <seebs!> has joined #yocto17:17
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:24
*** belen1 <belen1!~Adium@> has quit IRC17:28
*** andyross <andyross!> has quit IRC17:36
*** andyross <andyross!> has joined #yocto17:37
-YoctoAutoBuilder- build #277 of nightly-fsl-ppc is complete: Failure [failed Building Images] Build details are at
*** dv__ <dv__!> has joined #yocto17:44
*** dv_ <dv_!> has quit IRC17:45
*** fenrig <fenrig!> has quit IRC17:50
*** n01 <n01!> has joined #yocto17:51
*** dany <dany!~Thunderbi@> has joined #yocto17:53
*** panda84kde <panda84kde!> has quit IRC17:59
*** kmccombe <kmccombe!> has joined #yocto18:05
-YoctoAutoBuilder- build #309 of nightly-mips is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #306 of nightly-ppc is complete: Exception [exception Building Images_1] Build details are at
-YoctoAutoBuilder- build #308 of nightly-non-gpl3 is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #306 of nightly-ppc-lsb is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #308 of nightly-x86 is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #55 of nightly-qa-extras is complete: Exception [exception Building Images_1] Build details are at
-YoctoAutoBuilder- build #302 of nightly-x86-64 is complete: Exception [exception interrupted] Build details are at
-YoctoAutoBuilder- build #304 of nightly-world is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #281 of nightly-fsl-arm-lsb is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #306 of nightly-arm-lsb is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #305 of nightly-multilib is complete: Exception [exception Building Images_4] Build details are at
-YoctoAutoBuilder- build #147 of minnow-lsb is complete: Exception [exception Building Images] Build details are at
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC18:13
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto18:13
frayOne of our testers was verifying the PACKAGE_EXCLUDE functionality, and ended up removing the passwd and group files.. well needless to say other things in the system (post install scripts) started failing..18:21
frayI'm guessing the right answer for this is that we need to check if a passwd/group file was installed (ROOTFS_POST_COMMAND_prepend?)18:22
frayand then print a nice error that hey you don't have a passwd/group file18:22
*** mebrown <mebrown!> has quit IRC18:26
Krz-what does INSANE_SKIP do?18:31
Krz-it's in opencv recipe: INSANE_SKIP_python-opencv = "True"18:32
frayINSANE_SKIP_<package>  will skip one or more sanity checks..18:32
frayI don't think 'True' is valid18:32
mr_sciencenot vaild in oe-core?18:33
mr_scienceit's all over the place in oe-classic...18:33
fraycontents of INSANE_SKIP_<package> is which sanity checks to skip18:33
frayI think the union of:18:34
frayWARN_QA ?= "ldflags useless-rpaths rpaths staticdev libdir xorg-driver-abi \18:34
fray            textrel already-stripped incompatible-license files-invalid \18:34
fray            installed-vs-shipped compile-host-path install-host-path \18:34
fray            pn-overrides infodir \18:34
fray            "18:34
frayERROR_QA ?= "dev-so debug-deps dev-deps debug-files arch pkgconfig la \18:34
fray            perms dep-cmp pkgvarcheck perm-config perm-line perm-link \18:34
fray            split-strip packages-list pkgv-undefined var-undefined \18:34
fray            version-going-backwards \18:34
fray            "18:34
frayis all of them18:34
*** dvhart <dvhart!> has joined #yocto18:35
*** mebrown <mebrown!> has joined #yocto18:36
*** drasko <drasko!> has quit IRC18:42
*** dany <dany!~Thunderbi@> has quit IRC18:47
Krz-basically I have it in opencv package and I have a problems with opencv19:13
Krz-it compiles, but the python module does not work19:13
Krz-when I do 'import cv' on target (uclibc) I receive symbol 'th_comment_query_count': can't resolve symbol in lib '/usr/lib/'19:14
Krz-I checked libtheoraenc and it contains that symbol :(19:14
Krz-will see what INSANE_SKIP for opencv tries to hide19:15
-YoctoAutoBuilder- build #278 of nightly-fsl-ppc is complete: Success [build successful] Build details are at
Krz-Commented out whole INSANE_SKIP and builds fine. It's probably some leftover.19:24
*** galak <galak!> has quit IRC19:28
seebsSo, I have painted myself into a shiny new corner.19:34
seebsI'm working on updates to meta-sourcery, and to get around problems with not being able to compute HOST_PREFIX for multilibs outside of a recipe, I moved some setup stuff into a recipe.19:35
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC19:35
seebsAnd long story short: If there's no sstate cache in sight, the dependency chain results in the extra little bits of code getting run, and all is well. But if the things which depend on this code are in cache, it doesn't get run.19:35
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto19:35
seebsAnd I may be going about this the wrong way. But what I end up wanting is a way to say "if you even THINK about this recipe, then you must execute this code before you do it, whether you then end up building the recipe or using sstate stuff instead". And I don't know of one.19:36
-YoctoAutoBuilder- build #318 of nightly-x32 is complete: Exception [exception interrupted] Build details are at
seebs(Reason it has to be in a recipe is that if you are not inside a parsed recipe, the multilib fixups for HOST_PREFIX aren't done, so you end up with -vendor- instead of -vendormllib32- in HOST_PREFIX.)19:37
*** ant_home <ant_home!~andrea@> has joined #yocto19:37
*** JimBaxter <JimBaxter!> has quit IRC19:38
-YoctoAutoBuilder- build #286 of nightly-oecore is complete: Exception [exception interrupted] Build details are at
*** smartin_ <smartin_!> has joined #yocto19:44
*** slaine <slaine!~slaine@> has quit IRC19:50
*** dv__ is now known as dv_19:53
*** kmccombe <kmccombe!> has quit IRC19:55
*** kmccombe <kmccombe!> has joined #yocto19:56
*** dv_ <dv_!> has quit IRC19:58
-YoctoAutoBuilder- build #306 of nightly-multilib is complete: Exception [exception interrupted] Build details are at
-YoctoAutoBuilder- build #310 of build-appliance is complete: Exception [exception interrupted] Build details are at
*** joeythesaint <joeythesaint!~jjm@> has quit IRC19:59
*** dv_ <dv_!> has joined #yocto20:00
-YoctoAutoBuilder- build #311 of nightly-x86-lsb is complete: Exception [exception interrupted] Build details are at
*** kmccombe <kmccombe!> has quit IRC20:11
vducuyzeddii: the fetch failure because my company internet policy blocked session that connect to linux-yocto-3.1020:12
*** amarsman <amarsman!> has quit IRC20:12
vducuyafter fix the fetch in-progress now20:13
zeddiigood news. my ran to completion here, so we are good to go. gotta love IT departments :)20:13
-YoctoAutoBuilder- build #310 of nightly-mips is complete: Exception [exception interrupted] Build details are at
vducuynew policy need to "click" a button to continue for almost new web terrible for yocto likes development20:18
*** vducuy <vducuy!734e07cb@gateway/web/freenode/ip.> has quit IRC20:25
*** n01 <n01!> has quit IRC20:30
*** n01 <n01!> has joined #yocto20:31
*** mebrown <mebrown!> has quit IRC20:32
*** smartin_ <smartin_!> has quit IRC20:37
*** mebrown <mebrown!> has joined #yocto20:39
*** mebrown <mebrown!> has quit IRC20:46
*** mebrown <mebrown!> has joined #yocto20:49
ant_homejwessel: ping20:55
*** musdem <musdem!~Zack@> has joined #yocto21:05
frayhe's been struggling to figure this out..21:05
ant_homenow I'll play with MODVERSIONS21:09
*** j8 <j8!~IceChat9@> has quit IRC21:15
*** sameo <sameo!~samuel@> has joined #yocto21:19
jwesselant_home: With the way I changed things you won't have a problem with modversions.21:21
jwesselYou'll only have a problem with modversions if you have kernel specific modules in the initramfs, in your case as far as I could tell you don't.21:22
ant_homeI'm trying to build your usecase but 'old-style'21:22
jwesselWell you'll get the circular dependency issue then when you use the INITRAMFS_TASK21:23
ant_homewell, no21:23
ant_homethe container is another recipe21:23
jwesselThe use case I have is building an initramfs for the same kernel I am booting (with kernel modules).21:24
jwesselPerhaps in your case you have a secondary kernel and hense no problem no dependency21:24
*** darknighte is now known as darknighte_znc21:25
ant_homeif you see my kernel recipes just requires a linux-yocto so it will be the same kernel21:26
jwesselWhat is the image showing me that you sent?  Not sure what I am supposed to glean from it.21:27
ant_homeand the external kernel doesn't build the modules but uses the ones in the image21:27
ant_homethat you can embedd a full image and its virtual/kernel + modules in one pass w/out circular deps issues21:28
ant_homeeven old-style21:28
jwesselI'll make a change to the INITRAMFS config you sent me to test it.21:29
jwesselFirst I'll send a v2 patch.21:29
*** gjohnson <gjohnson!> has left #yocto21:31
*** amarsman <amarsman!> has joined #yocto21:35
ant_homejwessel: casually I'm researching about "[RFC PATCH] Signed kexec support"21:36
ant_homeso secureboot and enforced signing21:37
jwesselThat isn't quite the same thing as MODVERS :-)21:37
ant_homeheh, it's the same paranoia ;)21:37
jwesselAh. so you cannot have a dependency loop in your configuration. You have no kernel modules!21:39
jwessel% grep =m tmp-eglibc/work/c7x0-oe-linux-gnueabi/linux-yocto-tiny-kexecboot/3.10.11+gitAUTOINC+dad2b7e1ce_e1aa804148-r0/linux-c7x0-tiny-build/.config21:39
jwesselIf you take for example the qemux86-64 bsp it has some kernel modules.  And if I add to the IMAGE_INSTALL += "kernel-module-bonding" for example21:41
jwesselIt will implode because of the circular dependency of need the kernel to be built but waiting for the module from the kernel compile.21:42
jwesselThat is why we have to "2nd stage it"21:42
jwesselSigning a kernel and the modules for a trusted OS however can be done in the 1st pass.21:43
*** andyross <andyross!> has quit IRC21:43
jwesselLike in your case if you wanted to sign everything for what ever reason.21:43
jwesselAt any rate, your use cases should no longer be broken once RP merges the patch.21:43
ant_homejwessel: I did understand that the first kernel has just to boot and mount the initramfs, init then loads the modules21:44
*** andyross <andyross!> has joined #yocto21:44
jwesselant_home: Sure that will work fine for a single pass if klibc doesn't need the modules.21:45
ant_homethat image doesn't use modules21:45
ant_hometry core-image-base as I did21:45
ant_homeas cpio21:45
jwesselYou mean your config + core-image-base ?21:45
ant_homewe even have the kernel inside21:45
ant_homeyes as INITRAMFS_IMAGE21:46
ant_homenote we did it with tiny but feel free to require -standard21:46
*** W1N9Zr0 <W1N9Zr0!> has quit IRC21:52
Krz-how do I build debug version of python into image?21:52
*** W1N9Zr0 <W1N9Zr0!~W1N9Zr0@> has joined #yocto21:52
*** challinan_ <challinan_!> has joined #yocto21:52
*** challinan <challinan!> has quit IRC21:55
*** Sput <Sput!~sputnick@quassel/developer/sput> has quit IRC21:55
jwesselKrz-: You mean like python-dbg kind of thing?21:55
*** Sput <Sput!~sputnick@quassel/developer/sput> has joined #yocto21:55
jwesselCurrently the oe-core doesn't have a recipe for that.21:55
ant_homejwessel, our klibc image needs a monolithic kernel ofc, it has to scan and detect the block devices and the filesystems21:57
ant_homeit's a 'bootloader'21:57
ant_homethe same kernel can reside on SD/CF/MMC/USB so the drivers must be built in21:57 least during development...21:57
ant_homejwessel: in other words the external kernel does not install nor packages anything. You are supposed to use the modules in the cpio21:57
*** otavio <otavio!~otavio@debian/developer/otavio> has quit IRC21:59
*** elbc <elbc!2e12602e@gateway/web/freenode/ip.> has quit IRC21:59
*** otavio <otavio!> has joined #yocto21:59
*** otavio <otavio!~otavio@debian/developer/otavio> has joined #yocto21:59
Krz-jwessel: yeah, but if I do 'bitbake python-dbg' it doesn't do anything21:59
Krz-jwessel: is it enough if I do 'IMAGE_INSTALL +="python-dbg" ?22:00
jwesselI don't think you are getting what you want there.22:00
jwesselthe python-dbg package is just the debug symbols for python.22:00
jwesselIt is not /usr/bin/python-dbg like say ubuntu.22:00
Krz-jwessel: I want symbols for gdb for python :)22:01
jwesselSo you'll have the symbols, but if you are looking for a higher level trace of where python is, using the py extensions in gdb this is not what you want.22:02
jwesselIf you are just debugging the python interpreter, yes you got what you are looking for.22:02
Krz-I have a 'unknown dlopen() error' from python, just looking for any debug info on that22:02
Krz-the error comes just after 'import cv' from opencv library22:03
jwesselI would imagine simply strac'ing it will tell you what it tried to open22:03
jwesselstrace -f -o log python...22:03
jwesselSure you could debug it as well, but I don't think you need to.22:04
jwesselThere is probably an implicit or explicit load of a c library by the class you are pulling in and it isn't there or is linked with other libraries you don't have.22:05
ant_homehm, I thought this was fixed: "The recipe shadow-native is trying to install .."22:26
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto22:30
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-qehtovrlsmxwryte> has quit IRC22:32
*** n01 <n01!> has quit IRC22:38
*** challinan_ <challinan_!> has quit IRC22:42
*** zenlinux <zenlinux!> has quit IRC22:43
*** zenlinux <zenlinux!> has joined #yocto22:44
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC22:45
*** seebs <seebs!> has quit IRC22:54
*** seebs <seebs!> has joined #yocto22:58
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto22:58
lpapprburton: ping22:58
*** jzhang-laptop <jzhang-laptop!jzhang16@nat/intel/x-ofztrwxudodfqvow> has joined #yocto23:16
jzhang-laptophalstead: ping23:16
halsteadHi jzhang-laptop. :)23:17
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto23:17
jzhang-laptophalstead: sent u an email, can you reply?23:18
halsteadjzhang-laptop, Just got it.23:18
mr_sciencei'm more than happy to come in on a weekend for a real emergency, but what do you say when someone only *thinks* it's an emergency?23:19
*** mulhern <mulhern!> has joined #yocto23:25
*** andyross <andyross!> has quit IRC23:40
mranostaymr_science: no? :)23:48
mr_sciencei was thinking of something more delicate...23:52
mr_sciencejust can't think of *what* exactly...23:52
*** hollisb <hollisb!> has quit IRC23:57

Generated by 2.11.0 by Marius Gedminas - find it at!