**** BEGIN LOGGING AT Thu Mar 29 02:59:58 2012 Mar 29 04:07:52 khem: ping? Mar 29 05:34:39 how can i determine in which order the task of a package is executed? Mar 29 06:33:51 #angstrom Mar 29 06:34:21 Hello, is anyone active? Mar 29 06:43:16 anyone here? Mar 29 06:44:02 the nic-list is full - nobody is here :-P Mar 29 06:48:27 Well, i have a question for you guys...How do I get a the shared libraries for a package to be installed in an image? Mar 29 06:50:26 I have created a new image recipe based off of another recipe (omap3-console-image) and added the opencv package to the IMAGE_INSTALL variable. But, when I copy the image over to my SD card, I don't see the executables or the libraries. Mar 29 06:50:43 any ideas? Mar 29 06:51:53 starts the build for opencv? Mar 29 06:54:48 Yes, the build for opencv indeed starts Mar 29 06:56:02 ave you in your $WORKDIR-tempfolder a logfile for do_install? Mar 29 06:57:35 would it be in this directory: tmp/work/armv7a-angstrom-linux-gnueabi/opencv-2.2.0+svnr4462-r3/? Mar 29 06:58:22 yes - i think Mar 29 06:58:25 If so, I do not see a logfile in there Mar 29 06:58:59 I do see libraries and executables in the tmp/work/armv7a-angstrom-linux-gnueabi/opencv-2.2.0+svnr4462-r3/usr/lib and tmp/work/armv7a-angstrom-linux-gnueabi/opencv-2.2.0+svnr4462-r3/usr/bin directories, respectively Mar 29 07:01:33 Ok, I do see a log file for do_compile in the tmp/work/armv7a-angstrom-linux-gnueabi/opencv-2.2.0+svnr4462-r3/temp directory Mar 29 07:03:21 noone for do_install? you are sure the build was ok? Mar 29 07:03:59 Oh, wait there is one for do_install Mar 29 07:04:43 I have a log.do_install and a run.do_install Mar 29 07:04:51 Which one should I look at? Mar 29 07:05:13 ok - run.do_install is the script which is executed Mar 29 07:05:18 and log is the log :-) Mar 29 07:05:46 look into log.do_install can you see where is the lib installed? Mar 29 07:10:10 I have a lot of line like this "Installing: /opt/embedded-systems/armv7/gumstix/tmp/work/armv7a-angstrom-linux-gnueabi/opencv-2.2.0+svnr4462-r3/image/usr/lib/libopencv_calib3d.so.2.2.0" at the end of the log file, but nothing telling me where the install destination is Mar 29 07:11:17 I guess it's installing everything into the appropriate /opt/embedded-systems/armv7/gumstix/tmp/work/armv7a-angstrom-linux-gnueabi/opencv-2.2.0+svnr4462-r3/image/usr ? Mar 29 07:11:56 This "/opt/embedded-systems/armv7/gumstix/tmp/work/armv7a-angstrom-linux-gnueabi/opencv-2.2.0+svnr4462-r3/image/usr/lib/libopencv_calib3d.so.2.2.0" is the location, all in .../image/ goes to a ipk/dep/rpm package and should installed from your image-recipe into the image Mar 29 07:12:58 now look at the log-files in your image-recipe-workdir and ensure the opencv-2.2.0+svn4462-r3 is installed in your image Mar 29 07:17:38 Hmm, I looked at the log file in my image-recipe-workdir and there were only three lines: Mar 29 07:17:51 + do_install Mar 29 07:17:56 + base_do_install Mar 29 07:18:02 + : Mar 29 07:18:08 That was it Mar 29 07:18:37 you have only one log-file in this dir? Mar 29 07:18:52 look to other files and search :-) Mar 29 07:24:37 After some searching, there was some more opencv stuff in log.do_rootfs. I found these two lines: Mar 29 07:24:46 Installing opencv (2.2.0+svnr4462-r3.6) to root... Mar 29 07:24:52 Downloading file:/opt/embedded-systems/armv7/gumstix/tmp/deploy/glibc/ipk/armv7a/opencv_2.2.0+svnr4462-r3.6_armv7a.ipk. Mar 29 07:25:35 I didn't find anything saying where "Installing opencv (2.2.0+svnr4462-r3.6) to root..." was located though Mar 29 07:27:53 the opencv_2.2.0+svnr4462-r3.6_armv7a.ipk is a ar-archiv, extract it and look into the content what is in the ipk and this is installed to your root Mar 29 07:34:59 Hmm, there only appears to be a file named control in the archive Mar 29 07:35:25 it's located in DEBIAN/ in the archive Mar 29 07:36:41 mornin Mar 29 07:38:37 you have no data.tar.gz? Mar 29 07:39:10 No, that wasn't present in the .ipk archive. Mar 29 07:39:22 Just the "Control" file Mar 29 07:39:44 hmm ... have you some other opencv* files in the deploy/ipk directory? Mar 29 07:42:11 There are other opencv* files. Namely, opencv-apps....ipk, opencv-dbg....ipk and opencv-dev....ipk. I looked at the opencv-dbg and it has the libraries and the opencv-apps has the executables. But, these are found in the logs Mar 29 07:43:29 have you in your log.do_rrotfs a "Installing..." of that package which has your needed content Mar 29 07:43:32 ? Mar 29 07:48:01 No. I just performed a grep for the others and didn't find anything Mar 29 07:49:08 have you opencv or opencv-apps in your IMAGE_INSTALL? Mar 29 07:49:34 i have opencv in my IMAGE_INSTALL, not opencv-apps Mar 29 07:50:01 should I have opencv-apps instead? Mar 29 07:50:11 along with opencv-dbg? Mar 29 07:50:47 try it Mar 29 07:55:39 I added the opencv-apps and opencv-dbg to my IMAGE_INSTALL and it completed without fail. But, I didn't see any output to stdout indicating that the opencv-apps and opencv-dbg were being compiled/installed. Mar 29 07:57:41 If I do a bitbake opencv-apps or bitbake opencv-dbg, both commands fail Mar 29 07:59:53 opencv in which meta-layer is this? Mar 29 08:00:35 I'm not sure what you mean my meta-layer Mar 29 08:00:40 good morning Mar 29 08:00:40 *by Mar 29 08:01:25 which style of oe you use oe-classic or oe-meta? Mar 29 08:02:05 is opencv a package created from you? Mar 29 08:03:43 I'm using oe classic Mar 29 08:03:51 opencv is not created by me Mar 29 08:05:15 what is teh error message if you try "bitbake opencv-apps"? Mar 29 08:06:07 i'm in the overo-2011.03 branch Mar 29 08:23:01 Hi, I'd like to influence a oridnary package recipe depending on which image recipe I'm building. Any ideas? Mar 29 08:23:53 A solution based on setting a variable in the image recipe that could be read in the package recipe would be nice. But I can't see that this is possible at all. Mar 29 08:31:27 guest___: i would try to use the overrides-mechanism?! Mar 29 08:34:13 sounds interesting I'll Google that. Mar 29 08:39:17 silviof: Do you mean the usual override of stuff like global variable that can be change locally in a recipe? Mar 29 08:42:00 guest___: oh - Sorry - no I have read the part with "image recipe" over ... Sorry Mar 29 08:43:39 What I'd like to do is depending on the image built influence the build of specific packages. Like less stuff in the kernel when I'm building a specific smaller image. Mar 29 08:53:56 isn't that supposed to be defined by the distro, rather than image? Mar 29 09:18:51 how can i determine in which order the task of a package are executed? Mar 29 09:30:25 silviof: do you want to know, or change? Mar 29 09:35:07 to know Mar 29 09:36:36 Zagor: to know Mar 29 10:13:11 silviof: for a standard recipe it usually goes fetch, unpack, patch, configure, compile, install, package, package_write_*, package_write (noexec) Mar 29 10:13:49 silviof: you can always use bitbake -n to do a dry-run Mar 29 10:14:15 bluelightning, libpng sources are in oe mirror. :D Mar 29 10:14:45 ka6sox: ok Mar 29 10:14:50 ka6sox: thanks Mar 29 10:14:59 Alex___, got all the good info :D Mar 29 10:15:33 bluelightning: thx, but if i have no standard recipe, i have a bitbake -g. but the file for task-depends file is a big mess. After converting to eps I have no viewer to view - it's to big :-) Mar 29 10:16:06 silviof: I did find a decent viewer for big graphs recently, let me find it Mar 29 10:17:41 http://code.google.com/p/jrfonseca/wiki/XDot Mar 29 10:17:54 bluelightning: thx - i will try it Mar 29 10:17:58 works better than any of the other alternatives I tried Mar 29 10:40:29 bluelightning: thx dotx is very fast! a good viewer. but ... Mar 29 10:41:08 bluelightning: can i read from the .dot-file the order of the executed tasks? Mar 29 10:41:39 silviof: I don't think you really can, they may not be sorted in dependency order Mar 29 10:41:52 bitbake -n is probably the best way to visualise that Mar 29 11:53:42 <_tasslehoff_> I built a console-image and have now added xfwm4 using opkg install from the angstrom feeds. when I try to start it I get "cannot open display". Anyone got an idea what packages/setup is needed? Mar 29 15:37:56 khem: ping Mar 29 15:39:24 RP: what do you know about 64bithack.patch Mar 29 15:39:27 for gcc-4.6 Mar 29 15:41:52 it seems somewhat related my issue where our meta-toolchain is looking in the wrong lib folder for libraries Mar 29 16:16:29 does anyone know what tune file i have to include for the marvel 88AP510? Mar 29 16:16:54 i think i'm running in a circle ^^ Mar 29 16:17:58 i've build a root image with arch-armv7a included and it booted fine on the cubox ... Mar 29 16:18:54 but when i try to include the kernel in the image i get a compiler error because it is searching in x86 dir of the kernel instead of arm Mar 29 16:19:41 and when i include tune-armv7.inc it failes at gcc-cross-initial Mar 29 16:29:11 VtS: Do you have proper kernel config Mar 29 16:29:32 yes the provided a working defconfig Mar 29 16:29:52 VtS: icluding tune-armv7.inc is not the right thing Mar 29 16:30:07 so figure out why kernel is not accepting your defconfig Mar 29 16:30:50 it usually happens when defconfig is not there and then kernel will assume you are making it for native system Mar 29 16:31:12 so including the armv7a is right? Mar 29 16:31:36 because denisATeukrea told me not to do that ^^ Mar 29 16:32:59 is it correct to specify the defconfig with KERNEL_DEFCONFIG = "cubox_defconfig" ? Mar 29 16:33:09 https://git.teamcoders.org/lmc/meta-cubox/blobs/master/recipes-kernel/linux/linux-cubox_2.6.32.9.bb Mar 29 16:35:37 VtS: KERNEL_DEFCONFIG ? Mar 29 16:35:44 who handles that Mar 29 16:36:09 mhm Mar 29 16:39:31 os so u have do_configure_prepend Mar 29 16:40:41 is ${WORKDIR}/defconfig correct in your tree after this Mar 29 16:41:19 how can i check that? Mar 29 16:41:35 simply by going into the that dir Mar 29 16:42:32 in that dir i have a defconfig Mar 29 16:42:46 i'll check if its the right one Mar 29 16:42:46 ok is it same as cubox defconfig Mar 29 16:43:23 yeah its cubox_defconfig Mar 29 16:45:18 VtS: and you are just using oe-core right Mar 29 16:45:26 not meta-oe layer on top Mar 29 16:46:46 copy it directly into a .config so intead of ${WORKDIR}/defconfig use ${S}/.config Mar 29 16:47:23 will try that Mar 29 16:52:12 if changed the install line that to .config but the file doesnt exit in the build dir Mar 29 16:52:30 do i have to clean the package temp? Mar 29 16:54:10 or should i clean the meta-oe layer ? Mar 29 16:54:28 no clean ... i thought include the meta-oe layer? Mar 29 16:59:11 no you dont have to Mar 29 16:59:21 khem i'v cleaned up the dir and no i have .config Mar 29 16:59:23 bitbake -cclean virtual/kernel Mar 29 16:59:33 no = now ? Mar 29 16:59:38 yes Mar 29 16:59:42 ok Mar 29 16:59:57 Does it build better ? Mar 29 17:00:18 better but CC scripts/mod/empty.o Mar 29 17:00:18 HOSTCC scripts/mod/mk_elfconfig Mar 29 17:00:18 as: unrecognized option '-EL' Mar 29 17:00:18 make[2]: *** [scripts/mod/empty.o] Error 1 Mar 29 17:01:54 sounds like the assembler you are using is mismatched from something else Mar 29 17:02:45 yeah compiler spec is are messed Mar 29 17:05:42 VtS: the problem is that your recipe is more geared toward old OE style Mar 29 17:06:04 which work ok if you use meta-oe and include linux.inc and stuff Mar 29 17:06:14 with oe-core you have to look at some bsps Mar 29 17:06:37 may be mets-fsl or some such Mar 29 17:07:54 i'll look into that bsp Mar 29 17:08:24 oh hang on Mar 29 17:08:29 HOSTCC scripts/mod/mk_elfconfig Mar 29 17:08:29 so its a good idea to change it the way that i can run without meta-oe or is it pointless? Mar 29 17:08:37 as: unrecognized option '-EL' Mar 29 17:08:47 so its a host utility Mar 29 17:08:56 and somehow target flags are leaking into it ? Mar 29 17:09:32 yes running without meta-oe should be a fine goal Mar 29 17:09:42 and it should work easily Mar 29 17:13:43 khem i dont really understand what you mean ... do you mean TARGET_CFLAGS="-O2 -pipe -g -feliminate-unused-debug-types" ? Mar 29 17:48:07 hello Mar 29 17:48:13 can I use the devshell without specifying any target? Mar 29 17:48:23 I have some custom code which I want to cross compile Mar 29 17:48:55 so I want a shell where "gcc" is aliased to the cross compiler etc. Mar 29 17:50:54 right now I just type bitbake -c devshell , where is something that I already built Mar 29 17:58:17 anyone know how to tell gcc where to look for libraries? Mar 29 17:58:27 im having a problem with meta-toolchain tarball looking for libgcc in the wrong place Mar 29 18:00:08 03Alex J Lennon  07master * r5aaca5c679 10openembedded.git/recipes/libpng/libpng_1.2.48.bb: Mar 29 18:00:08 Modified fetch() checksums to be correct for libpng 1.4.28 released 15/3/12 (current) instead of previous 8/3/12 release Mar 29 18:00:08 Signed-off-by: Alex J Lennon Mar 29 18:13:51 dv_: it's possible you should use meta-toolchain for that Mar 29 18:14:18 meta-toolchain produces an extractable cross toolchain along with an environment setup script Mar 29 18:35:04 msm: -L surely ? Mar 29 18:35:14 well, that's link time... Mar 29 18:35:31 bluelightning: right Mar 29 18:35:40 bluelightning: the default libdir search path is not good Mar 29 18:35:50 i can't always specify the path to libgcc.a ;) Mar 29 18:36:15 heh Mar 29 18:36:25 I'm not sure, but khem may be able to help Mar 29 18:36:30 its looking in: /local/opt/fsl/1.1/sysroots/x86_64-fslsdk-linux/usr/bin/ppc64e5500-fsl-linux/../../lib/ppc64e5500-fsl-linux/gcc/powerpc64-fsl-linux/4.6.2 Mar 29 18:36:38 when it should be looking in: /local/opt/fsl/1.1/sysroots/x86_64-fslsdk-linux/usr/bin/ppc64e5500-fsl-linux/../../lib64/ppc64e5500-fsl-linux/gcc/powerpc64-fsl-linux/4.6.2 Mar 29 18:36:49 its quite close to correct, i assume it's some little thing im missing Mar 29 18:37:00 this is for meta-toolchain btw Mar 29 18:37:07 i've pinged khem ;) Mar 29 18:37:24 he generally knows these things and my problem goes away quickly Mar 29 18:37:26 heeh Mar 29 21:27:45 msm: I think the problem is multilibs for ppc are inverted in gcc logic Mar 29 21:31:45 msm: what is base_libdir in your case ? if its not lib64 then you have a problem Mar 29 21:31:55 since thats what gcc will honor Mar 29 21:35:24 base_libdir is what? Mar 29 21:35:35 is it defined as a configure arg or env var or a yocto var? Mar 29 21:36:02 bitbake -e gcc-cross-canadian | grep base_libdir Mar 29 21:47:23 khem: base_libdir is point at the x64 sysroot - /opt/fsl/1.1/sysroots/x86_64-fslsdk-linux/lib64 Mar 29 21:47:54 however libdir appears hardcoded: libdir=${exec_prefix}/lib/${TUNE_PKGARCH}${TARGET_VENDOR}-${TARGET_OS} Mar 29 21:48:40 meta/classes/cross-canadian.bbclass:libdir = "${exec_prefix}/lib/${TUNE_PKGARCH} Mar 29 21:50:10 khem: hmmm - what you think? Mar 29 22:06:19 in openembedded-classic meta-toolchain used two alias: opkg and opkg-target. but in oe-core i don't undestand how to use opkg-cl **** ENDING LOGGING AT Fri Mar 30 02:59:58 2012