**** BEGIN LOGGING AT Sun Jun 24 02:59:58 2012 Jun 24 14:16:01 gm Jun 24 14:16:31 hm why dbus still overlaps with /var/voiletale Jun 24 14:30:18 hm ah found it Jun 24 14:30:29 dbus own install stuff installs one dir Jun 24 14:30:46 I really wonder why nobody stumbled over it before Jun 24 15:08:11 I'm having a problem with SRC_URI Jun 24 15:09:09 the SRC_URI below seems to be down: Jun 24 15:09:09 svn://svn.java.net/svn/phoneme~svn/builds/phoneme_advanced-mr2-dev-${BUILDREV};module=cdc;proto=https;localdir=cdc \ Jun 24 15:09:39 apelete uhm we dont really support phoneme anymore Jun 24 15:09:44 do you really need it? Jun 24 15:10:03 and yes it changed because of oracle Jun 24 15:10:39 yeah, I'm trying to build an image on oe-classic, so I'm trying to replace it with an alternative link I found: Jun 24 15:10:39 http://build.shr-project.org/sources/svn/svn.java.net/svn/phoneme~svn/builds/phoneme_advanced-mr2-dev-${BUILDREV}/cdc/ Jun 24 15:11:49 what is the syntax the replace the svn:// link with and http:// one ? (given that the http content seems to be a mirror of the original svn repo) Jun 24 15:12:03 s/the replace/to replace/ Jun 24 15:12:16 s/and/an/ Jun 24 15:12:30 are you trying to build an oe-classic world image? Jun 24 15:12:57 no muffinman-image (for the jlime distribution), why ? Jun 24 15:13:29 my goal is to make muffinman build on oe-classic, then try to port it over oe-core Jun 24 15:13:48 just exclude phoneme Jun 24 15:13:55 we dont have it on oe-core Jun 24 15:14:00 and nobody need it Jun 24 15:14:04 we have android now Jun 24 15:15:14 I can't exclude it right now because I need it to complete the build process on oe-classic, or can I ? Jun 24 15:15:38 o.O Jun 24 15:15:51 just exclude it from the image recipe Jun 24 15:15:57 where is the problem? Jun 24 15:16:04 or task Jun 24 15:16:21 okay have to go now Jun 24 15:16:24 till later maybee Jun 24 15:16:27 okay Jun 24 15:16:40 will look into this solution Jun 24 15:16:43 thanks Jun 24 16:23:13 re Jun 24 19:16:43 woglinde: who should win today ? :) Jun 24 19:16:53 woglinde: ITA seems to be in better control so far Jun 24 19:48:19 dont know Jun 24 20:07:51 woglinde: uclibc does have %m support Jun 24 20:08:04 woglinde: so may be that %m patch for systemd wont be needed Jun 24 20:08:32 woglinde: I have enabled this option to turn it on in uclibc but it has no testing for so many years Jun 24 20:09:47 khem uhm lol Jun 24 20:10:19 I wondered why you changed Item->argument Jun 24 20:10:21 too Jun 24 20:10:24 and fixed it here Jun 24 20:10:51 which one Jun 24 20:10:52 btw. udev needs now an explicit -lrt too Jun 24 20:10:59 yes Jun 24 20:11:00 khem in tmpfiles.c Jun 24 20:11:03 I have that patch Jun 24 20:11:26 oh thats because those buffers are on stack now Jun 24 20:11:42 so whatever unquote function returns should be copied into them Jun 24 20:11:55 remember they are not pointers in this patch Jun 24 20:12:04 so simple assignment is not enough Jun 24 20:12:27 but that also reminds me that because of this patch there will be so much memory leaks Jun 24 20:12:38 all those strdups wont be freed Jun 24 20:14:20 woglinde: I have some patches for uclibc and some for apps that I will unleash if it starts to work Jun 24 20:14:42 woglinde: right now I can build a systemd-image with uclibc-git/master locally Jun 24 20:14:51 but booting is not perfect Jun 24 20:14:58 systemd ends up with errors Jun 24 20:15:46 hms Jun 24 20:16:10 khem but with gcc-4.7 the code compiles anymore Jun 24 20:16:27 because of mismatch of char[50] and char* Jun 24 20:16:34 +dont Jun 24 20:16:41 woglinde: http://pastebin.com/mPtvNtRD Jun 24 20:17:08 woglinde: I have updated the patch to do strcpy there Jun 24 20:17:49 journal my fail because of missing run/log Jun 24 20:18:35 khem can you post the patch? Jun 24 20:19:11 systemd update patch you mean ? Jun 24 20:19:28 yes Jun 24 20:19:40 hmmm the failure is same if I enable %m in uclibc and remove the patch Jun 24 20:19:45 so %m is working ok :) Jun 24 20:20:36 woglinde: here is the patch http://paste.ubuntu.com/1058103/ Jun 24 20:24:01 stupid ubuntu wants the login for downloading it as text Jun 24 20:25:21 ok let me paste it elsewhere Jun 24 20:29:00 yes? Jun 24 20:29:44 http://paste.kde.org/507044 Jun 24 20:31:26 woglinde: which version of udev are you using Jun 24 20:32:08 hm let me see Jun 24 20:32:34 udev-182-r0 Jun 24 20:32:59 are you able to boot with systemd ? Jun 24 20:33:23 sorry Jun 24 20:33:29 I am not there yet Jun 24 20:33:45 I only have my beagle here with broken serial console Jun 24 20:35:44 k Jun 24 20:36:36 and I trashed one sdcard while getting u-boot usb serila support working again Jun 24 20:44:46 woglinde: I guess something got added to udev thats not in line with uclibc Jun 24 20:55:27 hm looks like with kernel 3.x u-boot usbserial dont works anymore Jun 24 20:59:58 woglinde: you mean the dongles Jun 24 21:00:04 no Jun 24 21:00:08 I have a usb2serail dongle works ok here Jun 24 21:00:24 u-boot has serial console support via usb Jun 24 21:00:33 oh that bit yeah I dont use that Jun 24 21:00:59 as I said serial console here got broken Jun 24 21:31:15 italy won Jun 24 21:31:28 another penalty kicking lost for england Jun 24 21:59:44 does anyone know where i can get some info on which udev version to use with my 2.6.26 kernel? Jun 24 22:01:04 sorvats should be in the kernel documentation Jun 24 22:01:06 try grep Jun 24 22:01:20 or otherway round in the udev source Jun 24 22:01:37 sorvats but why you need to stick to such an old kernel Jun 24 22:01:44 which gains no security patches anymore Jun 24 22:03:00 beh, it seems upgrading to a newer kernel will take some considerable amount work, as we are using a custom camera driver Jun 24 22:03:52 hm oh okay Jun 24 22:03:55 with udev and buggy jffs2 i'm about to start cutting myself just a bit, so that pain is a little more copable with Jun 24 22:04:00 have to go now Jun 24 22:04:03 good nite Jun 24 22:04:07 nite ty :) Jun 25 01:32:04 howdy folks Jun 25 01:32:28 i recently set up a recipe for Python 3.2 in stable/2009 Jun 25 01:33:11 it built successfully, still need to verify that it actually installs and runs correctly Jun 25 01:35:01 is it still possible to push such recipes up to stable/2009 in case anyone else wants it? Jun 25 01:36:07 waynr: it may not make sense to put it in release branch but new recipes are good for master Jun 25 01:36:23 waynr: you can submit this against meta-oe or oe-core Jun 25 01:36:26 would that be oe-core? Jun 25 01:36:27 there will be interest Jun 25 01:36:29 okay Jun 25 01:37:01 cool, i don't know when i will get to work on it though i still need to port our bsps from 2009/stable to the meta-oe layering architecture Jun 25 01:38:21 i really like openembedded : D Jun 25 01:45:37 is the documentation on the OE website outdated? http://docs.openembedded.org/usermanual/html/chapter_metadata.html Jun 25 01:46:05 "The OpenEmbedded directory, $OEBASE/openembedded/, has seven directories, three of which hold BitBake metadata" Jun 25 01:46:22 is that referring to the older/classic OE layout? Jun 25 01:46:48 i think it is...if you go up one directory: http://docs.openembedded.org/usermanual/html/ the latest copyright is 2009 Jun 25 01:47:13 where might I find the latest documentation? Jun 25 01:48:17 honestly everywhere I look I get confused because I run into a mix of versions Jun 25 01:48:35 i'm not sure...i have been reading poky documentation: http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Jun 25 01:48:57 disclaimer: i have only been on this IRC for about ten minutes so don't take anything i say as authoritative Jun 25 01:51:48 I keep running into yocto/poky in my searching Jun 25 01:52:44 i understand "The OpenEmbedded-Core Project (OE-Core for short) resulted from the merge of the Yocto Project with OpenEmbedded" according to wikipedia Jun 25 01:52:59 poky is a...distribution; yocto is a project that aims to document and provide templates and structure to the bitbake recipes provided by openembedded Jun 25 01:53:33 poky is the primary project supported by yocto which is why if you follow yocto documentation you will end up with a poky build Jun 25 01:53:58 but it's really just an example of how to structure your own bitbake/openembedded project Jun 25 01:54:04 I've been building an Angstrom distro with the classic OE Jun 25 01:54:35 and I'm trying to upgrade my project to the latest OE Jun 25 01:55:37 so it's theoretically possible to just substitute poky with angstrom while following yocto build instructions Jun 25 01:55:38 ? Jun 25 01:55:45 maybe Jun 25 01:55:50 check this link out: http://www.openembedded.org/wiki/LayerIndex Jun 25 01:56:00 that is a list of layers, among which you will find angstrom Jun 25 01:57:31 when you are editing your bblayers.conf, you would specify the path to the meta-angstrom layer in the BBLAYERS variable Jun 25 01:59:25 so for a simple embedded system having no fancy graphics, Jun 25 01:59:36 i have been building the console-image Jun 25 02:00:31 with this new layering stuff I should be able to just pull in the oe-core, the single hardware layer, and angstrom layer Jun 25 02:00:59 sound good in theory or am I already missing something? Jun 25 02:01:16 sounds good in theory to me, but i am still learning it Jun 25 02:02:53 learning OE or just this new layering stuff? Jun 25 02:03:16 new layering stuff, although i am still fairly new to the whole OE thing Jun 25 02:08:46 well thx for the help Jun 25 02:24:17 by the way, Jack_Handy, there is an #angstrom channel on freenode Jun 25 02:25:48 yep Jun 25 02:25:55 i'm avoiding it atm Jun 25 02:26:27 i want to keep clear separation of oe-core from angstrom in my head Jun 25 02:26:55 i'm currently building two versions of the new OE on some amazon spot instances Jun 25 02:27:27 one is the pure oe-core, following these directions: https://wiki.yoctoproject.org/wiki/OpenEmbedded-Core Jun 25 02:28:30 the other is taken from a pre-configured AMI, following these directions: http://www.openembedded.org/wiki/EC2CloudBuild Jun 25 02:35:00 interesting Jun 25 02:38:32 only costing me 1.8 cents per hour per instance right now Jun 25 02:39:56 and that's for a dual core system per instance Jun 25 02:54:41 never thought of trying something like that, i might have to give it a go **** ENDING LOGGING AT Mon Jun 25 02:59:58 2012