**** BEGIN LOGGING AT Thu Jan 31 02:59:58 2013 Jan 31 08:18:50 good morning Jan 31 08:47:27 otavio, I need to add a 1.4_M3 branch to meta-fsl-arm to generate the milestone release candidate. Can I branch from master? Jan 31 09:25:25 bluelightning: hello Jan 31 09:25:33 hi ant_work, all Jan 31 09:25:56 hi bluelightning, better now? Jan 31 09:26:11 rburton: better, but still not 100% Jan 31 09:26:36 thanks for asking Jan 31 09:26:51 just don't give me anything :) Jan 31 09:27:30 no promises :) Jan 31 10:54:38 halstead: yes, please Jan 31 10:54:59 halstead: it has still build failures and we're working on those. Jan 31 10:55:52 otavio, Thank you. It's done now. Jan 31 10:56:22 Waiting on the build to finish now so I can post the RC to the mailing list. Jan 31 10:56:35 I see Jan 31 11:03:42 hi, anyone an idea what bsp would be best suited as starting point (or, even better, use as is) for Xeon E5620 ? Jan 31 11:27:48 eFfeM_work: MACHINE="atom-pc" ? Jan 31 11:28:30 mckoan: hm, atom and xeon seem somewhat apart Jan 31 11:28:46 actually for a test trying to see if I can get a yocto build for my current pc Jan 31 11:28:56 mckoan: btw are you going to fosdem ? Jan 31 11:30:51 ls Jan 31 11:42:40 eFfeM_work: not this year :-( Jan 31 12:01:57 eFfeM_work: pretty sure meta-intel has something exactly like what you need Jan 31 12:19:00 rburton: yeah, peeking at it, it is not always too clear what is for what Jan 31 12:19:24 eFfeM_work: sure, it's all buried behind codenames. grep xeon and you'll see the machines aiming at xeon and you can pick one close. Jan 31 12:19:41 eFfeM_work: at the end of the day, atom-pc isn't really specific to atom, so it will boot on xeon fine Jan 31 12:19:50 (ignoring drivers, you'll need to add more probably) Jan 31 12:20:30 rburton: I'm already building atom-pc, tought I'd give it a stab Jan 31 12:21:12 grepping xeon did not help too much, probably closest is sugarbay, but probably atom-pc will do what I want Jan 31 12:21:45 I din't have strong driver needs for now (and that is something I can fix) Jan 31 12:22:33 fwiw, atom-pc will be renamed generic-x86 at some point, with a few more drivers enabled by default Jan 31 12:23:20 hi Jan 31 12:26:19 rburton: ah didn't know about the rename Jan 31 12:26:21 Can someone help me ? I build core-image-x11 using poky-danny-8.0 but his image contain packages with debug symbol how can we remove them ? My aim is to reduce size of image Jan 31 12:27:41 Pravin: do you mean some libraries are unstripped or you have some -dbg pacakges installed? Jan 31 12:28:38 yes Jan 31 12:29:00 I want to use this image for release version Jan 31 12:29:12 someone with yocto wiki R/W access? please modify https://wiki.yoctoproject.org/wiki/index.php?title=PR_Service to say that "bitbake-prserv-tool migrate_localcount" needs to be executed for each MACHINE Jan 31 12:29:34 I guess Constantin is not here Jan 31 12:50:03 RP: I have bitbake branch for both sftp patchset versions and only changes in v2 were in 6/6 Jan 31 13:07:59 JaMa: tweaked wiki Jan 31 13:08:03 JaMa: ok, thanks Jan 31 13:09:45 RP: thanks Jan 31 14:14:54 <_Lucretia_> hi, i'm still having trouble with my layer, I have 2 test recipes in there, one build a static lib and other builds a test app which links against the lib, but on a clean build it fails as it hasn't build the lib first. I have a DEPENDS = "libhello" in my hello.bb file, is there something that needs to go into layer.conf that I'm missing? Jan 31 14:38:01 I can't log with python functions bb.note Jan 31 14:38:20 2.3.7.1. Logging With Python http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Jan 31 14:38:54 I have bb.note("~~~~~~~~~~~~~~~~~~~~~~~~~") Jan 31 14:39:08 and I get Failure expanding variable do_fetch: ShellSyntaxError: LexToken(TOKEN,'"~~~~~~~~~~~~~~~~~~~~~~~~~"',0,0) Jan 31 14:39:27 Greetings all, I'm trying to add python to my generated distro (by adding IMAGE_INSTALL_append += "python"), but I get a image creation-time failure in do_rootfs saying "Unable to resolve package python" Jan 31 14:39:32 any idea what I may have done wrong? Jan 31 14:40:24 adalton: looks like you don't have any python recipe in your layers Jan 31 14:40:43 mckoan: odd thing is, if I do a 'bitbake python' it works Jan 31 14:41:53 from .../meta/recipes-devtools/python/python_2.7.3.bb Jan 31 14:43:07 or, I guess I should say .../openembedded-core/meta/...; I took ./meta out and replace it with the one from git Jan 31 14:45:27 Do you automatically get a package whose name is the same as the recipe? Jan 31 14:46:14 For example, if in a recipe bar I have a PACKAGE += "foo", does that recipe provide packages foo and bar? Jan 31 14:46:44 like, I note that the python recipe doesn't have an explicit python PACKAGE or FILES_python Jan 31 14:51:54 I face similar problem in yocto poky then I was adding DISTRO_EXTRA_RDEPENDS += "mypackage" in local.conf then it works Jan 31 14:53:33 hum, I'll give that a shot and see Jan 31 14:55:13 adalton: I never used python in my rootfs, in oe-classic recipe is quite different with more FILES_, I guess it could be the problem Jan 31 14:55:43 adalton: I'd ask to oe channel too Jan 31 14:55:57 ah, there's an oe channel? :-) Jan 31 14:56:13 yes of course ;-) Jan 31 14:56:33 #OE? Jan 31 14:56:36 yep Jan 31 14:56:42 great -- thanks :-) Jan 31 14:56:45 yw Jan 31 14:56:52 Can someone help me ? I have build core-image-x11 using poky-danny-8.0 but this image contain packages with debug symbol how can we remove them ? My aim is to reduce size of image Jan 31 14:57:09 Pravin: don't install the -dbg packages? Jan 31 14:57:35 I just add layer in bblayer file Jan 31 14:57:48 I don't specifically installed dbg pkg Jan 31 14:57:51 but I want to remove Jan 31 14:57:54 them Jan 31 14:58:04 How can I do this ? Jan 31 14:58:14 Pravin: figure out whether they're installed first? Jan 31 14:58:30 hi, is there a clean way to add an "inherit xyz" in a bbappend only for one machine ? Jan 31 14:59:16 ericben: great question! Jan 31 15:00:43 usecase : one one machine I need to add initscripts for a package so I have INITSCRIPT_NAME_${PN}-smsd_machine (and other INITSCRIPTS_xxx) set and I need to add inherit update-rc.d but that will trigger an error if I build for an other machine as bitbake will complain that I inherit update-rc.d without having set INITSCRIPT_NAME Jan 31 15:03:09 you can do tests inside a ${@ block, which can be inline with inherit Jan 31 15:03:17 i.e. "inherit " is a valid no-op Jan 31 15:03:40 so you can test against the machine and inherit the class or "" Jan 31 15:04:05 rburton: ok thanks I was not aware I could have intherit "" Jan 31 15:04:46 ericben: it wasn't possible before Jan 31 15:04:56 ericben: but RP said that now it works Jan 31 15:05:30 JaMa: OK thanks do you know if that will work on danny ? Jan 31 15:05:58 no idea when that was changed.. I guess so Jan 31 15:06:06 JaMa: I'm actually trying so answer in a few minutes ;-) Jan 31 15:07:36 rburton: mckoan: atom-pc worked fine for me, now need to find how to get to 64 bit Jan 31 15:07:47 thanks for your help! Jan 31 15:09:32 eFfeM_work: compare qemux86 with qemux86-64 Jan 31 15:09:47 rburton: yeah, was doning that Jan 31 15:12:33 JaMa: rburton: ok inherit ${@base_conditional("MACHINE", "my-smsgw", "update-rc.d", "", d)} works fine thanks a lot Jan 31 15:17:53 eFfeM_work: good! Jan 31 15:25:15 so when I build my image, I get "multiple providers are available for java2-runtime" "consider defining a PREFERRED_PROVIDER entry to match java2-runtime." Jan 31 15:25:38 I've created new bb.event TargetsListForWorldGenerated any idea why bitbake always complains? ERROR: Unknown event: Jan 31 15:25:53 I tried adding PREFERRED_PROVIDER_java2-runtime = "..." and PREFERRED_PROVIDER_virtual/java2-runtime = "..." Jan 31 15:26:04 neither seemed to satisfy it Jan 31 15:27:04 what's the right way to do it? Jan 31 15:30:30 ah found it, it's knotty complaining Jan 31 15:37:09 ideas? Jan 31 15:45:44 on a related note, any have any experience with the meta-java layer? I'm looking at installing a jdk and running into some problems with a git server at berlios. I was hoping there might be some alternative Jan 31 15:53:17 rp: hi, regarding the sftp patches... didn't the summary for v2 make it to the list? i did send one Jan 31 15:54:22 zibri: sorry, it did and I just missed it Jan 31 15:54:44 zibri: you replied to it so my mail client put it at the end and I wasn't expecting it there, sorry Jan 31 15:56:15 RP: have you seen also ssh:// fetcher changes? maybe I would need them backported to 1.14 bitbake Jan 31 15:57:10 JaMa: I merged them earlier I think Jan 31 15:58:19 great now I see them Jan 31 15:58:44 I'll test in 1.14 and send backport (is [for 1.14] in subject enough?) Jan 31 16:02:01 s/1.14/1.16/g Jan 31 16:03:51 works as-is in 1.16 Jan 31 16:21:53 what's the status of debian in general as a host system? Jan 31 16:22:53 i have someone who's trying my oe-based build on debian sid and running into a weird failure where eglibc-initial is trying to install files to the host prefix: http://people.gnome.org/~fpeters/log.do_install.8948 Jan 31 16:23:05 the same build works on rhel6 as a host Jan 31 16:23:48 i'm suspecting some sort of conflict/confusion with the debian multiarch stuff on the host with respect to eglibc's cross compilation knowledge Jan 31 17:46:07 RP, You started a build with no comment. It looks like you're rebuilding M3. Did the last build fail? It looks like it succeeded except there was a problem with nightly-x86-64-lsb. Jan 31 17:47:03 halstead: right, we restarted because of a couple of missing patches and shared state issue Jan 31 17:47:27 * halstead nods. Jan 31 17:48:03 sgw1, Okay. I have the e-mail written and ready to go as soon as it finishes. Jan 31 18:07:21 halstead: I did send email to the builds list Jan 31 18:10:00 RP, I found it after I pinged you. Thanks. Jan 31 19:19:36 Hum, can a bbclass have its own SRC_URI? My class depends on a local file. Jan 31 19:21:24 that seems like it wouldn't work Jan 31 19:21:56 yeah, I was afraid it might not, I'm giving it a try now to see what happens Jan 31 19:25:11 yeah, no love it seems Jan 31 22:08:54 otavio: ping Jan 31 22:09:00 Hi Jan 31 22:09:39 otavio: how do I get gpu-viv-bin-mx6q to put the libGAL-fb.so onto the disk image? Jan 31 22:10:05 otavio: I've tried adding libgal-fb-mx6-dev to the RDEPENDS, but no luck. Jan 31 22:10:19 You ought to link to it Jan 31 22:10:25 shlibs will handle it for you Jan 31 22:10:34 and have the gpu in depends **** ENDING LOGGING AT Thu Jan 31 22:46:41 2013 **** BEGIN LOGGING AT Thu Jan 31 22:48:23 2013 Jan 31 22:55:34 * sgw1 sez M3 is built, starting testing, thanks to everyone! Feb 01 00:04:11 hi , I want to build yocto to use on the x86_64 jasperforest target, the hardware has only 1 serial console port and 1 ethernet port Feb 01 00:04:29 should I choose "core-image-basic" or "core-image-lsb" as my target build? Feb 01 00:07:27 Eddy: that depends on what you will be doing with it. Feb 01 00:07:31 application running on it will be storage disk I/O and configuration thu ethernet only Feb 01 00:08:39 how can I compare the difference btwn "image-core" and "image-lsb"? Feb 01 00:08:55 Read the .bb files? Feb 01 00:08:56 basic and lsb Feb 01 00:08:59 oh Feb 01 00:09:02 ok, thx Feb 01 00:10:13 they will show a nice summary of what groups are installed. Personally, I use neither. It is easy enough to make your own image. Feb 01 00:11:19 so , you create a target image like "core-image-myappiance"? Feb 01 00:12:43 anyone available to help me with a problem with devshell/menuconfig on Fedora? Feb 01 00:14:54 something like that. But it's generally image-devicetype for me. Feb 01 00:15:32 the documentation discusses how to go about doing it. Feb 01 02:33:36 RP: The mini-x-session patch I sent fixes core-image-x11 to work for my machine Feb 01 02:34:02 sgw1: ^ **** ENDING LOGGING AT Fri Feb 01 02:59:58 2013