**** BEGIN LOGGING AT Fri Apr 19 02:59:58 2013 Apr 19 05:02:19 hi Jefro Apr 19 08:39:44 morning all# Apr 19 09:39:42 while I can successfully "bitbake core-image-minimal" from scratch, it is not clear to me if you can do it using a pre-built toolchain, thus avoiding to recompile it Apr 19 10:22:38 david-e_: prebuilt from sstate or using an external toolchain? Apr 19 10:22:47 david-e_: you can do both Apr 19 10:26:12 RP: Did someone screw what creating the release tar ball for 8.0.1, or did you consciously change the layout of it? In poky-danny-8.0.tar.bz2 there is a toplevel "poky-danny-8.0/" directory. However, in poky-danny-8.0.1.tar.bz2 there is no toplevel directory matching the name of the tar ball. Rather the contents is directly at the top... Apr 19 10:26:27 *what => up Apr 19 10:26:37 Saur: I suspect someone screwed up Apr 19 10:26:49 Saur: could you file a bug for that please? Apr 19 10:27:06 RP: Will do (after lunch) Apr 19 11:14:09 RP: from sstate I guess: something like compiling it once and installing on a build machine so that others can use it Apr 19 11:19:49 RP: Bug submitted: https://bugzilla.yoctoproject.org/show_bug.cgi?id=4351 Apr 19 11:19:50 Bug 4351: normal, Undecided, ---, jeffrey.osier-mixon, NEW , No top level directory in tar ball for Yocto release 1.3.1 Apr 19 11:20:03 david-e_: just share the sstate cache directory between the machines Apr 19 11:20:20 Saur: thanks! Apr 19 11:21:19 RP: not top prio at the moment, but I'll certainly look at it. Any docs/tutorials/examples I can take as a starting point? Apr 19 11:23:09 david-e_: its covered in local.conf.sample, also more details in the manual http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#shared-state-cache Apr 19 11:23:20 RP: cheers mate Apr 19 14:31:25 hey Apr 19 14:32:02 what would be the reason for getting packages built with -dev and -dbg Apr 19 14:32:12 but no base package being built? Apr 19 14:32:32 i had ${PN}_dev.bb at the start Apr 19 14:32:37 sorry Apr 19 14:32:45 that was ${PN}_git.bb Apr 19 14:32:52 and it didn't set PV Apr 19 14:33:16 then I tried setting PV = "+git${SRCPV}" Apr 19 14:33:23 but that broke it Apr 19 14:33:48 then I tried to pretend that it's ${PN}_0.0.1.bb Apr 19 14:34:07 and removed previous ${PN}_git.bb Apr 19 14:34:26 but still cannot get it to produce the base package Apr 19 14:34:36 only -dev and -dbg get emitted Apr 19 14:35:22 although, I had successfully built an image with the original ${PN}_git.bb which didn't set PVa Apr 19 14:35:35 ah, I'm quite confused now Apr 19 14:35:56 errordeveloper: hmm, maybe leave it as _git and set PV = "0.0.1+git${SRCPV}" ? Apr 19 14:41:21 bluelightning: tried that, didn't work Apr 19 14:41:47 let me try again ... Apr 19 14:44:31 ah, I can see one funny bug Apr 19 14:53:20 was about to gist the actuall recipes, but figured I had a very silly thing there Apr 19 14:53:42 yey, fixed now!! Apr 19 14:53:42 errordeveloper: is this some kind of library called xxx.so? Apr 19 14:54:12 no, I just had a attempt at having x.inc and x-header.inc Apr 19 14:54:28 errordeveloper: glad you got it sorted... Apr 19 14:54:42 which was a bullshit idea Apr 19 14:57:05 so okay, package is built and image is built Apr 19 14:57:40 but I now see the consecuqnce of the warning message I have asked about here: http://stackoverflow.com/questions/16090550/building-python-packages Apr 19 14:57:56 while bitbake only gave me a warning Apr 19 14:58:06 i get an error from opkg Apr 19 14:59:57 i update the SO post now, cause that seems like a potential pitfal ... Apr 19 15:00:09 any clues? Apr 19 15:04:23 errordeveloper: what did you hope to achieve with that that do_install_append fragment? Apr 19 15:05:02 because it's removing /usr/share/share/, which seems a bit odd Apr 19 15:05:42 you want something like rm -f ${D}${libdir}/python*/site-packages/site.py* to delete the overlapping files Apr 19 15:05:50 (python-requests shipping them is also wrong) Apr 19 15:14:57 rburton: no, i actually don't use that one Apr 19 15:15:15 rburton: I see ... Apr 19 15:16:16 afaik, site.py shouldn't be shipped Apr 19 15:16:25 the do_install_append() was in pycurl Apr 19 15:16:35 rburton: ah, so ok then Apr 19 15:22:32 rburton: so I'm guessing it's a kind of a bug in distutils class Apr 19 15:22:50 cause it's supposed to take care of these kind of thing Apr 19 15:23:03 errordeveloper: yeah it probably should ensure that file doesn't get packaged Apr 19 15:28:33 rburton: so you are quite sure that removing site.py will not actually break anything? Apr 19 15:30:03 errordeveloper: an optional module shouldn't be shipping it, python itself should Apr 19 15:30:12 so delete it from your package Apr 19 15:30:41 ok Apr 19 15:35:18 sigh, I guess Ubuntu with encrypted home direcotry (ecryptfs) can not be used to build yocto since filenames are limited to 144 characters, sstate filenames can be longer.. Apr 19 15:35:51 mcfrisk: don't build on cryptfs, its a world of pain, not just that Apr 19 15:37:05 I've never had issues with encrypted lvm, performance is 10% worse but on a laptop I'm not that picky, but this ecryptfs thingy is too much. Apr 19 15:37:43 lvm may be ok, I know ecyrptfs isn't Apr 19 15:37:49 can't have long filenames?! Apr 19 15:38:36 man, failtastic Apr 19 15:38:42 yeah, that's really #wtf Apr 19 15:39:23 oh it's called "The enterprise cryptographic filesystem for Linux Apr 19 15:39:27 " Apr 19 15:39:38 * errordeveloper loves all things enterprise Apr 19 15:40:58 yep, gory details at https://bugs.launchpad.net/ecryptfs/+bug/344878 and http://unix.stackexchange.com/questions/32795/what-is-the-maximum-allowed-filename-and-folder-size-with-ecryptfs Apr 19 15:41:42 that SX answer isn't entirely accurate though Apr 19 15:41:54 the guy talking about normal vs cjk is all confused Apr 19 16:10:27 hm, so this doesn't work as expected: Apr 19 16:10:27 do_install_append() { rm -f ${D}${libdir}/python*/site-packages/site.py[oc] Apr 19 16:10:31 } Apr 19 16:10:44 there is a new line after { Apr 19 16:17:35 you'll want to drop the site.py too? Apr 19 16:20:24 ah, i sort of see what you mean, this doesn't actually match for site.py Apr 19 16:20:25 ... Apr 19 16:20:48 *.py* will Apr 19 16:21:32 ah, sure ... but actually it was wrong path Apr 19 16:22:50 hm, there are /usr/lib/python2.7/site.py* and /usr/lib/python2.7/site-packages/site.py* by the looks of it ... Apr 19 16:23:42 another thing, how do you force package rebuild properly? Apr 19 16:26:07 ah, I see it's `bitbake -c cleansstate` and then `bitbake -c package` Apr 19 16:28:21 _not really_ Apr 19 16:28:34 that didn't actually give the package Apr 19 16:28:57 i was doing find . -iname '*python[-_]requests*' | xargs rm -fr Apr 19 16:29:03 but that's a bit nasty Apr 19 16:33:27 Hello Apr 19 16:33:55 Could someone help me with hob? How can I add a fstype in advanced settings Apr 19 16:33:56 ? Apr 19 16:39:38 bluelightning: ^ Apr 19 16:40:28 otavio: it's controlled by IMAGE_FSTYPES I think Apr 19 16:40:34 er, I mean IMAGE_TYPES Apr 19 16:56:44 bluelightning: right Apr 19 16:56:56 bluelightning: it is not picking the sdcard image I added Apr 19 16:57:08 bluelightning: how it fetches this value? Apr 19 16:57:46 otavio: I'm not entirely sure, but the IMAGE_TYPES value is set in the image_types*.bbclass files and hob apparently reads that value Apr 19 16:58:33 for some reason I don't understand it does not show up in bitbake -e, and you can't extend it from local.conf Apr 19 16:58:41 (as an experiment) Apr 19 16:59:13 bluelightning: so it seems as a bug to me Apr 19 16:59:18 :) Apr 19 16:59:34 otavio: maybe... but does your image type class add to IMAGE_TYPES? Apr 19 16:59:57 hello Apr 19 17:00:01 bluelightning: I think so Apr 19 17:00:29 bluelightning: IMAGE_TYPES? not defined Apr 19 17:00:54 otavio: then add to it with += in your class Apr 19 17:02:44 is anybody using yocto/bitbake with jenkins ? Apr 19 17:03:26 feydrautha80: JaMa is Apr 19 17:03:45 bluelightning: doing it Apr 19 17:04:49 do you know if he is "alive" more often than less ? :) Apr 19 17:06:12 I'm right now, if the question is quick Apr 19 17:07:26 JaMa: do you have a place with the setup/scripts? Apr 19 17:07:51 JaMa: and how is your cycle to test things? use an internal GIT tree to push stuff for building? Apr 19 17:18:35 I use the same scripts I'm using for shr Apr 19 17:19:00 https://github.com/shr-distribution/shr-makefile/tree/jansa/test-all Apr 19 17:27:12 bluelightning: didn't work Apr 19 17:30:16 otavio: I would suggest filing a bug in that case Apr 19 17:40:43 the distutils seems quite painfull Apr 19 17:41:23 my packages seem to be missing some thing, need to figure it out Apr 19 17:41:50 hopefully I will end-up submitting some pull-request to fix this :) Apr 19 17:42:15 actually, any idea why python 3 is not in poky? Apr 19 19:42:48 hm... are there logs for this channel? Apr 19 19:45:45 errordeveloper: http://logs.nslu2-linux.org/livelogs/yocto/ Apr 19 19:45:52 awesome! Apr 19 19:47:34 ah, but it doesn't have stuff from today Apr 19 19:48:18 I just wonder if anyone responded to me while I was offline Apr 19 19:48:19 errordeveloper: scroll down on the main listing, it's at the bottom Apr 19 19:48:29 http://logs.nslu2-linux.org/livelogs/yocto.txt Apr 19 19:48:51 ah! Apr 19 19:49:09 pretty sweet :) Apr 19 19:49:58 ok, so nobody commented on distutils being sucky Apr 19 19:52:02 i need to figure out why I only get one directory Apr 19 19:52:03 cosm-demo-image-beaglebone/usr/lib/python2.7/site-packages/requests-1.2.0-py2.7.egg/ Apr 19 19:52:19 as in /usr/lib/python2.7/site-packages/requests-1.2.0-py2.7.egg/ Apr 19 19:52:33 and python doesn't seem to like it that way Apr 19 19:53:57 so here what it's supposed to look like Apr 19 19:53:57 https://www.archlinux.org/packages/community/any/python2-requests/files/ Apr 19 19:54:14 but I get just the egg dir ;9 Apr 19 19:54:47 ah ... may I just try to hack it Apr 19 20:45:07 ok so replacing `inherit distutils` with `inherit setuptools` seems to work Apr 19 20:45:35 setuptools is some tiny little class that passes different flags to destutils Apr 19 20:45:46 i'm all confused with this python stuff now Apr 19 20:46:04 anyhow, seems like I got the right dir structure now! wow! Apr 19 23:37:41 Hello - I'm getting an "Unable to resolve package " error when I build. Apr 19 23:38:03 At the moment, _0.1.bb only lists dependencies and doesn't build anything. Apr 19 23:38:28 Do I need to do something special on a dependency-only package? Apr 19 23:52:12 Circuitsoft: do you list them as DEPENDS or RDEPENDS Apr 19 23:52:25 RDEPENDS Apr 19 23:52:39 RDEPENDS_${PN} Apr 19 23:53:06 So are you trying to be like a packagegroup? Apr 19 23:54:21 For now. The app is written in python, and this is listing all the dependencies. At the moment it's easier to install it directly to the target than to go through Yocto. Apr 19 23:54:35 Circuitsoft: ie, just creating a recipe to group other packages together? Apr 19 23:54:40 I do intend to have this recipe be the app, but not just yet. Apr 19 23:55:16 you may want to mark it with ALLOW_EMPTY then Apr 19 23:55:42 Circuitsoft: ALLOW_EMPTY = "1" Apr 19 23:56:11 Awesome. Thanks. Apr 19 23:56:20 Circuitsoft: actually ALLOW_EMPTY_${PN} = "1" (I always for the ${PN} **** ENDING LOGGING AT Sat Apr 20 02:59:57 2013