**** BEGIN LOGGING AT Thu Sep 26 02:59:59 2013 Sep 26 07:29:19 morning all Sep 26 08:55:45 good morning Sep 26 08:58:45 morning mckoan Sep 26 12:02:42 i'm currently creating a bitbake recipe which compiles only one c file - its working. do_compile() { Sep 26 12:02:42 ${CC} -o ${WORKDIR}/myprog ${WORKDIR}/myprog.c ${LDFLAGS} Sep 26 12:02:42 } - now i have to use libevent (which is available as bb file), but how can i add this to my recipe? I think i need to add "-levent" to compiler arg but it doens't find ev.h (eventlib header) - how to tell the include path (and where is it?) Sep 26 12:06:27 devzero_: does your recipe have a DEPENDS on libevent? Sep 26 12:09:53 yes, i added DEPENDS = "libevent" - but it seems not being used, when i run bitbake on my recipe it doens't perform compiling of libevent Sep 26 12:11:05 devzero_: libevent 2.0.21-r1 (master) doesn't appear to include an ev.h #include file. maybe you're assuming a different version of libevent? Sep 26 12:11:28 if bitbake isn't building libevent, it might be because it is already built and doesn't need rebuilding Sep 26 12:13:10 in $TMPDIR/work//libevent/2.0.21-r1/packages-split "find . -name ev.h -print" doesn't return anything Sep 26 12:16:13 Crofton|work: ping Sep 26 12:17:18 hey Sep 26 12:17:24 I am confused Sep 26 12:17:42 the board is me, likewise darknighte_znc and debris` Sep 26 12:17:45 arg Sep 26 12:17:46 denix, Sep 26 12:18:01 the usage email never went to the members list Sep 26 12:18:10 I figured most of them would see it on the dev list Sep 26 12:18:50 i'll check, thx Sep 26 12:20:02 gcc builds remain racy on our builders, but unable to reproduce locally again :-/ Sep 26 12:20:28 Crofton|work: uh, sorry I tought the board was the board of members Sep 26 12:21:14 suihkulokki: for racy do you typically get "aarch64-oe-linux-ld.bfd: cannot find libgcc.a: No such file or directory"? Sep 26 12:21:28 no worries Sep 26 12:21:49 it isn't contreversial otherwise I would have emailed the members list Sep 26 12:22:08 Crofton|work: fair enough Sep 26 12:23:59 frobware: That's one of the way it may manifest Sep 26 12:24:07 ah my fault.. i need libev, not libevent Sep 26 12:26:04 suihkulokki: I wonder if it would help, on our builders, if we were to explicitly build gcc, then then linaro-images... It's not a solution, but it may be a temporary fix... Sep 26 12:48:14 are there bitbake recipes for "libev"? Sep 26 12:51:48 devzero_: doesn't look like any can be found in http://layers.openembedded.org, but I suspect it would be fairly easy to write one Sep 26 12:52:44 jeah i'll try now - didn't also find one Sep 26 13:00:20 hello guys, i wanna build Gstreamer1.0 for the beagleboneblack, i got the oe-embedded core libraries. when i run bitbake gstreamer1.0 it build for qe,ux86, how can i change that to beaglebone? Sep 26 13:04:01 anyone ? Sep 26 13:11:18 kevin_rz: set the MACHINE. the documentation has a good quick start for people haven't used oe before. Sep 26 13:13:49 no luck on beaglebone, or beagleboard it just has that qeux86 machines Sep 26 13:13:52 kevin_rz: the manuals here are the best reference: https://www.yoctoproject.org/documentation/current Sep 26 13:15:18 for the Angstrom building when i use MACHINE=beaglebone ./oebb.sh config beaglebone, it works well, now i need the GStreamer1.0 which is not in the default ANgstrom setup scripts, so i got the open embedded core, its there in theopen embedded core but i need to know how to set machine to beaglebone or equivalent :/ Sep 26 13:19:50 kevin_rz: assuming you want to build on top of OE-Core basically you need to add a layer to your supporting beaglebone e.g. meta-beagleboard Sep 26 13:20:12 kevin_rz: another choice would be using the latest development version of angstrom instead of the stable version Sep 26 13:23:48 bluelightning: libev was easy as u said.. SRC_URI and inherit autotools - works alone then ; Sep 26 13:23:50 ) Sep 26 13:24:10 devzero_: cool... it would be awesome if you could send a patch to add that to meta-oe ;) Sep 26 13:56:56 otavio: I was wondering whether fsl-community-bsp-platform has to be considered obsolete in favor of meta-fsl-arm Sep 26 14:00:46 how do i add the meta-beagleboard layer to the openembedded source? i mean like where do i place it? Sep 26 14:02:51 kevin_rz: http://www.openembedded.org/wiki/Layers_FAQ#How_do_I_make_use_of_a_layer.3F Sep 26 14:31:09 ant_work: ping Sep 26 14:31:35 pong Sep 26 14:31:48 ant_work: pulled in meeting Sep 26 14:31:50 sorry Sep 26 14:32:29 np, surviving to phone calls here Sep 26 15:18:18 Problem >.< "There is a confusing multiline, partially commented expression on line 22 of file /home/rz2/Desktop/openembedded-core/meta-openembedded/meta-oe/recipes-multimedia/libav/libav.inc (B = "${S}/build.${HOST_SYS}.${TARGET_SYS}")" Sep 26 15:20:01 kevin_rz: the line starts with # and ends with \ probably Sep 26 15:24:22 # start and a \ is supposed to mean the line is commented right? well it looks like a command B = "${S}/build.${HOST_SYS}.${TARGET_SYS}", well i tried commenting it now it says the same error for the next line which is blank. Sep 26 15:26:31 kevin_rz: no, it'll be the line before it Sep 26 15:27:26 kevin_rz: you're not mixing branches are you? i.e. master of one layer and "dylan" of another? Sep 26 15:32:07 ant_work: back Sep 26 15:32:21 hi Sep 26 15:32:52 ant_work: hi. Can I have sometime from you in order to understand meta-initram layer problem that we discussed couple of days back Sep 26 15:33:44 ant_work: I assumed that the yocto bug entry that you have me has the fix for the loop problem Sep 26 15:34:26 but when I looked int the patch I could not find that how modules dependency on kernel is resolved in that patch Sep 26 15:34:49 and then you said that due to that patch your layer is broken so you have reverted that patch Sep 26 15:34:57 so kind of confused here Sep 26 15:35:39 Noor: the old way of embedding an INITRAMFS_IMAGE just declaring it in a kernel recipe has been broken Sep 26 15:35:56 ahan Sep 26 15:36:02 my patch fixes it, using the compatibility-mode left Sep 26 15:36:10 INITRAMFS_TASK Sep 26 15:36:20 but I really don't like the full patch Sep 26 15:36:41 and I'm in touch with Bruce to understand what theyreally need Sep 26 15:37:11 see, I've embedded yesterday a full core-base-image complete of modules in my kernel Sep 26 15:37:12 ant_work: I think my problem is bit different Sep 26 15:37:18 not sure BY they way Sep 26 15:37:20 :) Sep 26 15:37:36 wait, there is even a kernel in /boot Sep 26 15:37:37 ;) Sep 26 15:38:06 I'm trying now toexplain that in order to obtain that you need a separate kernel recipe Sep 26 15:38:27 this recipe can be custom or just include a linux-yocto recipe Sep 26 15:38:39 well i just added meta-beaglebone to the main folder and edited the bblayers.conf: in meta/config folder. Sep 26 15:39:06 what's important is, the 'container' kernel is renamed and doesn't PROVIDE virtual/kernel Sep 26 15:39:30 but in fact is the same kernel as inside the initramfs/ as the modules if you want Sep 26 15:40:02 so it should be able to load the modules in the cpio Sep 26 15:42:23 ant_work: do you know the commit what is causing this issue Sep 26 15:42:51 Noor: http://imagebin.org/271984 Sep 26 15:42:58 ant_work: in our setup we are not doing it using NITRAMFS_IMAGE method Sep 26 15:44:01 in recipe we have Sep 26 15:44:02 if [ -e "${DEPLOY_DIR_IMAGE}/minimal-nae-image-${MACHINE}.cpio" ]; then Sep 26 15:44:02 cp -f "${DEPLOY_DIR_IMAGE}/minimal-nae-image-${MACHINE}.cpio" initramfs.cpio Sep 26 15:44:35 ok, you can do it with do_configure[depends] += "my_image:do_rootfs" and do the cpy in the recipe Sep 26 15:45:01 do_compile[depends] += "${@base_contains("IMAGE_FEATURES", "initramfs", "minimal-nae-image:do_rootfs", "", d)}" Sep 26 15:46:13 ant_work: so we have these two lines in our kernel recipe Sep 26 15:46:53 well, is a duplication ;) Sep 26 15:47:01 the code WAS in kernel.bbclass Sep 26 15:47:23 and I'd do do_configure[depends] += Sep 26 15:47:53 but hey, isn't it easier a one-liner INITRAMFS_IMAGE = "blah" Sep 26 15:48:08 ant_work: what I am saying is I have arround the same code that you have applied Sep 26 15:48:25 but why I am getting the dependency on kernel Sep 26 15:48:34 yes, that code was oiginally in linux.inc then was moved to kernel.bbclass Sep 26 15:48:37 iirc Sep 26 15:48:40 Yeah you are right Sep 26 15:49:16 I have ancient recipe :) Sep 26 15:49:59 but my question is it's the same as your patch but why I am getting the circular dependency Sep 26 15:50:45 because you are probably injecting the virtual/kernel Sep 26 15:51:09 yes this recipe provides virutal kernel Sep 26 15:51:10 as well Sep 26 15:51:39 that's the issue Sep 26 15:52:33 ant_work: OK ... can you explain how this is creating the issue Sep 26 15:52:58 * Noor just need to understand what is causing this circular dependency Sep 26 15:54:19 the cissue is explained in the text of the offending patch Sep 26 15:54:29 s/cissue/issue Sep 26 15:54:30 http://cgit.openembedded.org/openembedded-core/commit/?id=609d5a9ab9e58bb1c2bcc2145399fbc8b701b85a Sep 26 15:56:51 ant_work: thanks Sep 26 15:57:02 * Noor is going through the patch Sep 26 16:23:40 bbl Sep 26 19:37:43 Crofton|work, we need to do some upgrades to Opal tomorrow night Sep 26 19:44:53 ka6sox, ok Sep 26 19:45:03 I assume you have timed this for minimal annoyance? Sep 26 20:11:25 after 5pm left coast time...(once I see git traffic drop off) Sep 26 20:18:32 Hi, I am trying to build libsdl2. I need to build test programs prresent in libsdl2. The test programs are present in test folder. can anyone tell me how to make OE to cpmpile the sources present inside test folder Sep 26 20:22:16 test folder contains its own configure script Sep 26 21:55:37 mckoan|away: no; in fact the fsl-community-bsp-platform uses the meta-fsl-arm. **** ENDING LOGGING AT Fri Sep 27 02:59:58 2013