**** BEGIN LOGGING AT Tue Feb 21 02:59:58 2012 Feb 21 04:29:08 What machine name should be used for the imx.53 platform? Feb 21 04:43:27 Ah, i see its not supported yet Feb 21 07:51:11 morning all Feb 21 08:27:09 snow snow snow again Feb 21 08:28:11 ski ski ski again Feb 21 08:29:22 no mountains here Feb 21 08:29:59 * JaMa has to go 150km, but it's worth it :) Feb 21 08:30:24 "riesengebirge" ? Feb 21 08:30:28 well 150 to nearest and quite small skicentre Feb 21 08:30:51 yes or Ore Mountains Feb 21 08:32:01 hi all Feb 21 08:32:04 then you should buy kite to power your skies :) Feb 21 08:32:16 hi noor Feb 21 08:32:26 is there a way of ignoring LIC_FILES_CHKSUM in oe-core Feb 21 08:32:35 afaik no Feb 21 08:32:36 hi woglinde Feb 21 08:32:53 think why you cannt ignore it Feb 21 08:33:12 and it is not hard to add it Feb 21 08:33:36 I have a recipe which only have prebuild binaries ... it doenot have any licensing file .... how can I make it work in oe-core Feb 21 08:33:51 doesnot Feb 21 08:34:26 add LICENSE file to SRC_URI Feb 21 08:34:41 even if it's just local file in metadata Feb 21 08:34:42 are you talking about oracle arm java jvm? Feb 21 08:34:52 *just a wild guess* Feb 21 08:35:05 and use ${WORKDIR}/LICENSE in LIC_FILES_CHKSUM Feb 21 08:35:16 woglinde: u asking from me ..... no I got that recipe from somewhere else Feb 21 08:35:32 JaMa: I need to create my own then Feb 21 08:35:39 JaMa hm isnt there one for binary in core? Feb 21 08:35:43 and add it in SRC_URI Feb 21 08:36:07 or it can be an empty one? Feb 21 08:36:13 * Noor checks Feb 21 08:36:14 but yes its maybee better to make your own Feb 21 08:36:30 I would not ship an empty license file Feb 21 08:36:30 woglinde: there are all common licenses, but I would rather copy whatever license agreement you had to agree on web or something where you found what to put in LICENSE field Feb 21 08:36:40 jama yes Feb 21 08:37:31 thanks guys got the idea that what I need to do Feb 21 08:38:31 there is also CLOSED license if it does apply Feb 21 08:39:13 Noor: Not sure if it helps but the recipe for the external binary toolchain is using file://${COREBASE}/LICENSE and file://${COREBASE}/meta/COPYING.MIT Feb 21 08:39:20 http://git.openembedded.org/openembedded-core/tree/meta/recipes-core/meta/external-csl-toolchain.bb Feb 21 08:39:43 then it doesn't check LIC_FILES_CHKSUM, but having only binaries in SRC_URI does not always imply CLOSED license Feb 21 08:39:48 kenws no licese doesnt mean ots MIT Feb 21 08:39:50 its Feb 21 08:40:12 heh I wish it would :) Feb 21 08:41:27 well, this one explicitly specifies LICENSE = "MIT" Feb 21 08:41:56 yes because it's just for metadata Feb 21 08:41:59 it just came to my mind as it also package binary files Feb 21 08:42:07 like task* recipes Feb 21 08:42:31 kenws o.O Feb 21 08:42:44 that doesnt mean it has the same license Feb 21 08:43:01 JaMa: hm, "just for metadata" - could you elaborate? I'm afraid I don't get it. Feb 21 08:43:21 meta info in the resulting package Feb 21 08:43:28 like rpm or deb or ipk Feb 21 08:43:30 ah Feb 21 08:43:34 got it, thx Feb 21 08:44:02 kenws btw. the recipes inside oe are all MIT Feb 21 08:44:02 kenws: I mean that this license does apply to external-csl-toolchain.bb recipe etc. not to the binaries which are used thanks to this recipe Feb 21 08:44:59 JaMa: yes, it's for the recipe (not the code sourcery toolchain itself) Feb 21 08:45:05 woglinde: ok Feb 21 10:09:39 I wan't the shared glib-2.0 libraries to be added to my image. How can I do that? Feb 21 10:09:53 good morning Feb 21 10:10:47 hi mckoan Feb 21 10:11:01 woglinde_: hi Feb 21 10:11:04 hi all Feb 21 10:11:09 hi bluelightning Feb 21 10:11:10 morning mckoan Feb 21 10:23:26 hi mickeyl Feb 21 10:45:46 how do I get x11 on my image? I tried adding DEPENDS += "x11-common" RDEPENDS += "x11-common", but I don't see any startx or anything in the resulting image Feb 21 10:50:11 look at x11-common recipe what it provides first Feb 21 10:53:54 I have noticed that QA test function has been changed Feb 21 10:54:30 previously INSAVE-SKIP_$[PN] = "true" ignores all the tests Feb 21 10:54:37 but this is not the came now Feb 21 10:55:03 you need to give explicit test which you want to ignore .... how can I ignore all the tests? Feb 21 10:55:21 just list them all? there aren't very many, after all. Feb 21 10:55:22 damn I dont understand the oe git setup Feb 21 10:55:25 why do you want to ignore them all though? Feb 21 10:55:34 how do I push a new personal branch now? Feb 21 10:55:47 same as always, isn't it? Feb 21 10:56:06 push origin foo/bar? Feb 21 10:56:18 right Feb 21 10:56:24 pb_ just comparing how can i do what I was doing previously Feb 21 10:56:58 dont works here hm Feb 21 10:57:00 So setting it to true will not help Feb 21 10:57:58 How is auto-loading of kernel modules supposed to be implemented in Core? I can't find any recipes/classes that put anything in /etc/modules-load.d, so it seems that autoload modules should go in /etc/modutils and modutils-initscripts / modutils.sh is still required in the systemd world. Feb 21 10:58:54 pb -> http://pastebin.com/Z2XnytBd Feb 21 11:00:06 is my setup broken? Feb 21 11:02:23 well, that sounds rather like the branch you're trying to push just doesn't exist in your local repo. Feb 21 11:02:45 what does "git branch -a" say? Feb 21 11:04:17 okay but I thought it create it when pushing Feb 21 11:04:44 it creates it on the remote, but obviously there needs to be something to push first. Feb 21 11:04:53 are you trying to just create an empty branch? Feb 21 11:05:12 no Feb 21 11:05:28 I have a local branch k3 Feb 21 11:05:33 and want to push it Feb 21 11:05:41 to woglinde/foo Feb 21 11:05:50 where woglinde/foo do not yet exist Feb 21 11:06:17 ah. so you need to tell it to push k3 then. Feb 21 11:06:38 git push -n origin k3:woglinde/kaeilos-2011 Feb 21 11:06:44 args Feb 21 11:06:48 the : again Feb 21 11:06:55 okay thanks Feb 21 11:06:55 at the moment you're just asking it to push "woglinde/kaeilos-2011", which is clearly no good if you don't have a branch by that name Feb 21 11:07:04 yeah understood Feb 21 11:10:30 pb is deleting of the user branches now allowed? Feb 21 11:10:47 don't think so Feb 21 11:18:47 the "module_autoload_name" directive puts modules in "/etc/modutils" but I don't see systemd doing anything with this. is module_autoload just not working properly yet with systemd? it looks like modutils-initscripts/modutils.sh should not be used with systemd, but kernel modules don't load without it. Feb 21 11:19:03 wow another git feature mastered Feb 21 11:19:09 rebase --onto Feb 21 11:19:26 eleet Feb 21 11:20:54 for cherry-picking more patches at once Feb 21 11:25:12 a great day to master git commands today :-D Feb 21 11:25:56 mertsas: you probably want something like task-core-x11.bb Feb 21 11:26:42 icanicant what modules you need to load which udev not can? Feb 21 11:29:46 woglinde: in this case it's iscsi_tcp Feb 21 11:33:42 woglinde: please let's use mckoan/kaeilos-2012 Feb 21 11:35:09 * mckoan -> lunch (bb in 1,5 h) Feb 21 11:36:02 icanicant okay Feb 21 11:36:22 icanicant than you have to look into the systemd documentation Feb 21 11:37:06 ideally we would have some way of having these autoloaded without caring which init system was in use... Feb 21 11:41:55 it's not really a question about how to do it, it's a question about how to do it the "correct" way in OE Core. Feb 21 11:42:22 i can make it work but what is the recommended way of doing it? Feb 21 11:42:59 there is already the "autoload_module_name" directive which looks useful but it turns out that this doesn't work as expected, probably since systemd Feb 21 11:50:26 bluelightning: yes i think the module_autoload_ code just needs updating it for the systemd world. i'll see if i can knock up a patch. Feb 21 11:51:43 icanicant: when you're working on it, please look if there is possibility to force loading in specified order Feb 21 11:52:31 icanicant: or at least load more modules from one module_autoload_ directive (ie usb controller + g_ether) in one module_autoload_ Feb 21 11:59:43 JaMa: sounds useful Feb 21 12:00:50 yup I have usecase for it already :) Feb 21 12:01:01 SHR root@gjama ~ $ cat /etc/modules-load.d/g_ether.conf Feb 21 12:01:01 s3c2410_udc Feb 21 12:01:01 g_ether Feb 21 12:36:07 hi, Im trying to build using oe-core, I've ran the oe-init-build-env script, and then I run bitbake, and do not get past parsing Feb 21 12:36:26 I only get "ERROR: Command execution failed:" Feb 21 12:36:34 -v or -DDD do not give more info Feb 21 12:36:42 the cooker.log only includes the above line Feb 21 12:36:50 any ideas? Feb 21 12:39:42 om which ML we are sending patches for meta-oe? Feb 21 12:40:18 openembedded-devel Feb 21 12:41:27 ooo yeah ...... why I missed that Feb 21 12:41:52 there is only one patch should I sent pull request or just one patch will also work Feb 21 12:42:25 looks like only patch will do the work Feb 21 12:42:42 cant see recent pull requests Feb 21 12:53:29 then look better Feb 21 12:53:50 there are at least 2 from today Feb 21 12:54:00 but single patch with right prefix will work too Feb 21 13:07:50 re Feb 21 14:00:17 Is there anyway to get more info on why bitbake fails? first run after init oe-core it fails with only ERROR: Command execution failed: Exited with 1, -v and/or -DDD gives nothing more and cooker.log only gives same line Feb 21 14:02:27 does python work? Feb 21 14:04:48 yes Feb 21 14:26:33 ao2: ping Feb 21 14:44:44 ericben: ping Feb 21 14:56:32 pb_: do you know the list of users with write access on the git.openembedded.org repo? Feb 21 15:11:22 mckoan, pong Feb 21 16:13:48 would it be possible to upgrade a glibc based system into a eglibc one by just using opkg ? Feb 21 16:14:24 rob_w: yes Feb 21 16:14:36 we did that when we moved from OE classic to OE core Feb 21 16:15:06 we had to do some tuning of the packages though Feb 21 16:15:15 so is eglibc some much better ? Feb 21 16:15:23 which, shame on me, I still have not found time to go through and submit patches for those changes Feb 21 16:15:52 ah never mind .. i iwll read myself into it Feb 21 16:15:53 no idea :) but angstrom on OE coreused eglibc by default so it seemed like the way to go Feb 21 17:38:34 Crofton|work: hi, will you have a chance to test my qt patches this week? Feb 21 17:38:50 trying to Feb 21 17:39:10 ok, that would be great, thanks Feb 21 17:39:19 I have to get some guys setup to do local builds to support stuff in the field Feb 21 18:15:01 anyone using fedora 16 with oe-clssic? Feb 21 18:15:09 or oe-core? Feb 21 18:16:01 I am not Feb 21 18:16:13 I try to stay away from rpm Feb 21 18:28:27 ant_work: not offhand, but I can look it up Feb 21 18:28:41 going home now, but remind me later and I will investigate Feb 21 18:29:12 also, which particular repo are we talking about? Feb 21 18:33:09 ah kergoth linked me Feb 21 20:21:52 Which setting do I change to set the prefix of the toolchain? Feb 21 20:22:48 I would like to unify it a little bit... Feb 21 20:46:56 gaaaaah openmoko svn is down again Feb 21 21:19:31 florian: TARGET_PREFIX? Feb 21 21:33:34 hello , on Windows every window has ID named HWND , on Linux , how can i access other apps windows? they have something like HWND ? My real problem is , i've java app , i want to show some video on C++ side combining with java but java slows up , I want to bypass Java side and directly render some video on HWND on Windows but i could not found any solution on Linux , how can i fix problem Feb 21 21:44:09 re Feb 21 21:44:37 reaperofsouls: is this for the whole thing? Feb 21 21:50:02 florian: Where ever CC is used for and alike its ${TARGET_PREFIX}gcc, same for the various others. Normally it derived from ${TARGET_SYS}- Feb 21 21:51:38 hmm true... I wonder what it will break if I change it :) Feb 21 21:51:54 Sorry thats not exactly correct by default it is HOST_PREFIX=${TARGET_PREFIX} which for target apps resolves right. Feb 21 21:52:20 * florian wants toolchains for multiple targets all looking the same Feb 21 21:52:38 florian: We provide external toolchains, and it is what we set, though the stuff we are currently providing is more in line with classic atm, but it looks like it should carry in to core. Feb 21 21:52:38 sich as arm-linux-gcc and mipsel-linux-gcc Feb 21 21:53:11 true... it has to work for external ones Feb 21 21:57:09 Not sure if that would have the desired effect on the internally generated toolchains. Feb 21 21:59:07 A quick look at gcc-configure-common, I think the answer is probably though some one like khem would know. Feb 21 22:15:53 reaperofsouls: no effect. It should work fine if you override it provided its a valid gcc triplet Feb 21 22:16:07 since thats what we configure internal toolchain with Feb 21 22:16:18 for --program-prefix **** ENDING LOGGING AT Wed Feb 22 02:59:58 2012