**** BEGIN LOGGING AT Fri Dec 30 03:00:01 2016 Dec 30 09:18:18 Is there a way to show how much space each of the packages are taking up on an image? Dec 30 09:19:30 I have been poking around in the build/tmp/work/cortexa7hf-neon-poky-linux-gnueabi/XYZ/image folder for XYZ being each of the packages in that dir and it appears to contain the complete install dir from each package Dec 30 09:20:12 However a lot of these files are not contained in the final image Dec 30 09:22:06 deva: on the target, you probably can ask your package manager Dec 30 09:22:31 I use opkg. Any idea how to do that with that package manager? Dec 30 09:22:40 on the host, i'm not sure... the size of tthe packages in tmp/deploy might be a good aproximation Dec 30 09:23:01 deva: no, but opkg --help is very usefull Dec 30 09:23:26 boucman_work, Of course :-) Sorry for being lazy there :p Dec 30 09:26:09 np, I also think there is a script on the host called oe_pkgdata or something like that but my yocto build env isn't readily available right now for me to check Dec 30 09:44:27 I have found the package libx11-locale which takes up quite a bit of space. Can I somehow use bitbake to tell me which recipe depends on it? Dec 30 09:46:27 opkg tells me it is part of "root set" which I suppose means that it is somehow part of my IMAGE_INSTALL? Dec 30 09:52:33 deva: you should probably check LINGUAS in the mega-manual and in your distro configuration, to remove languages you don't plan to support Dec 30 12:22:19 Hi all, I have created a recipe which generates a static library, the library recipe uses autotools and I can see that it is actually installed under ./tmp/sysroots/qemux86/usr/lib/ooc/libooc.a - nevertheless another recipe which depends on that can't find the library and it fails to link Dec 30 12:38:11 pedr0_: if you are using the poky distro be warned it forces a "--disable-static" policy (with exclusions on certain recipes) - see meta/conf/distro/include/no-static-libs.inc Dec 30 12:39:09 I can't file that in my tree Dec 30 12:39:45 I have files such as default-providers.inc distro_alias.inc ... Dec 30 12:40:50 Would you know a quick hack to check that is actually the problem ? I wonder if I am simply doing sth stupid in my recipe as I am a newbye Dec 30 12:41:57 pedr0_: you can check "bitbake -e" and see if EXTRA_OECONF has "--disable-static" in it Dec 30 12:43:16 EXTRA_OECONF="" cnf = d.getVar('EXTRA_OECONF', True) or "" Dec 30 12:43:25 build@pocky:~/poky/build$ bitbake -e ttysnoop | grep EXTRA_OECONF # $EXTRA_OECONF [2 operations] EXTRA_OECONF="" cnf = d.getVar('EXTRA_OECONF', True) or "" Dec 30 12:43:25 pedr0_: without the link errors, and knowning what you are trying to statically link. I wouldn't know whats going wrong tbh Dec 30 12:44:11 | /home/build/poky/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.9.2/ld: cannot find -looc Dec 30 12:44:18 pedr0_: is it "" for both recipes (the linked and the one linking? Dec 30 12:44:37 wait, I did check the one generating the static lib Dec 30 12:45:09 yes that is empty as well Dec 30 12:45:14 pedr0_: have your got the full command that is doing the linking? e.g. "gcc.....-looc" Dec 30 12:45:33 i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/build/poky/build/tmp/sysroots/qemux86 -O2 -pipe -g -feliminate-unused-debug-types -c -o ttysnoop.o ttysnoop.c Dec 30 12:46:01 sorry Dec 30 12:46:02 no Dec 30 12:46:21 i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/build/poky/build/tmp/sysroots/qemux86 -o ttysnoop ttysnoop.o main.c -g -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -looc Dec 30 12:46:32 pedr0_: ah, your "libooc.a" is in a "ooc/" subdir, you will need to point the linker to that path "-L /usr/lib/ooc/" Dec 30 12:46:53 I have already tried Dec 30 12:48:13 wait Dec 30 12:48:21 I might have done a tremendous mistale Dec 30 12:48:25 *mistake* Dec 30 12:49:15 where would you put the -L /usr/lib/ooc/, in the recipe itself as OE_EXTRAMAKE.. ? Dec 30 12:50:18 i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/build/poky/build/tmp/sysroots/qemux86 -o ttysnoop ttysnoop.c main.c -g /usr/lib/ooc/libooc.a | i586-poky-linux-gcc: error: /usr/lib/ooc/libooc.a: No such file or directory Dec 30 12:50:24 pedr0_: depends, normally its populated for you by pkg-config or such Dec 30 12:50:39 I am utterly lost Dec 30 12:50:54 build@pocky:~/poky/build$ find ./ -name libooc.a ./tmp/sysroots/qemux86/usr/lib/ooc/libooc.a Dec 30 12:51:01 build@pocky:~/poky/build$ find ./ -name libooc.a Dec 30 12:51:07 ./tmp/sysroots/qemux86/usr/lib/ooc/libooc.a Dec 30 12:51:23 it's there ! Dec 30 12:51:26 :-( Dec 30 12:54:05 pedr0_: ...-gcc .... -L /usr/lib/ooc -looc Dec 30 12:54:15 pedr0_: its there but it is not in the search path Dec 30 12:54:31 pedr0_: you need to tell gcc/ld that it needs to search the ooc subdir Dec 30 12:54:38 it's the same Dec 30 12:54:51 you can tell the .a file directly, I tried that as well Dec 30 12:54:58 EXTRA_OEMAKE = " LDFLAGS=-L/usr/lib/ooc/" Dec 30 12:55:06 Makefile: $(CC) -o $@ $^ -g $(LDFLAGS) -looc Dec 30 12:55:19 | i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/build/poky/build/tmp/sysroots/qemux86 -o ttysnoop ttysnoop.c main.c -g -L/usr/lib/ooc/ -looc | /home/build/poky/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.9.2/ld: warning: library search path "/usr/lib/ooc/" is unsafe for cross-compilation | /home/build/poky/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.9.2/l Dec 30 12:55:21 if you tell it directly, you cant point at the hosts /usr/lib/ooc Dec 30 12:55:44 pedr0_: you need to point at the cross-compilation sysroot Dec 30 12:56:16 --sysroot=dir Use dir as the logical root directory for headers and libraries. For example, if the compiler normally searches for headers in /usr/include and libraries in /usr/lib, it instead searches dir/usr/include and dir/usr/lib. Dec 30 12:57:03 I don't think so, after the -sysroot option the gcc will point to /home/build/poky/build/tmp/sysroots/qemux86/usr/lib/ooc/ Dec 30 12:57:20 I reckon, judging from the man page Dec 30 13:06:59 pedr0_: sorry, was afk, No the -L/-I args dont work like that. You would need to use "-L=usr/lib/ooc" Dec 30 13:07:01 bah, I do not know Dec 30 13:07:24 -L/usr/lib/ooc ==> is treated as exactly that, /usr/lib/ooc Dec 30 13:07:39 you can check by running gcc with "--verbose" Dec 30 13:07:42 would that search on my local machine or under the yocto tree ? Dec 30 13:08:47 pedr0_: "gcc ... -L=usr/lib/ooc -looc" is probably what you are after Dec 30 13:09:20 *-L=/usr/lib/ooc* ? Dec 30 13:09:26 heres the excerpt from the gcc directory-options docs "If dir begins with =, then the = is replaced by the sysroot prefix; see --sysroot and -isysroot. " Dec 30 13:09:48 sorry i forget the "/" is front of the usr/lib Dec 30 13:09:52 ah, good catch Dec 30 13:09:55 forgot* Dec 30 13:10:19 oks Dec 30 13:10:35 ok, let us get at the bottom of this Dec 30 13:10:39 EXTRA_OEMAKE = " LDFLAGS=-L/usr/lib/ooc/" Dec 30 13:10:42 results into: Dec 30 13:10:49 i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/build/poky/build/tmp/sysroots/qemux86 -o ttysnoop ttysnoop.c main.c -g -L/usr/lib/ooc/ -looc | /home/build/poky/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.9.2/ld: warning: library search path "/usr/lib/ooc/" is unsafe for cross-compilation Dec 30 13:11:10 yep, because "-L/usr/lib... is refering to the host rootfs '/ Dec 30 13:11:14 I need to add the yocto rootfs at the -L I guess Dec 30 13:11:31 or change it to "-L=/usr/lib/ooc" Dec 30 13:12:01 Ti devo una cena Dec 30 13:15:20 thanks a lot Dec 30 13:15:27 it works now Dec 30 13:15:55 pedr0_: :) Dec 30 15:17:43 Has anyone ever tried using squashfs as an initrd? Dec 30 17:45:03 hey, I have a class with xyz_do_patch() and it contains: bbwarn "cp ${FILE} ${FILE}.orig"; cp ${FILE} ${FILE}.orig I can see the warning with the right command but it seams like cp is not executed since the orig file is missing. what am I missing here? Thanks Dec 30 17:52:20 oh lord.. nevermind forget that I asked Dec 30 21:25:55 Hey all **** ENDING LOGGING AT Sat Dec 31 03:00:01 2016