**** BEGIN LOGGING AT Fri Nov 29 02:59:58 2013 Nov 29 05:31:43 hi i have been trying to compile digitalpersona source for arm-poky-linux,while compiling i got below error http://pastebin.com/Eyvn6nE0 can you help me to solve this error Nov 29 05:37:19 i'm thinking that -L . should be a -L./ instead Nov 29 05:37:55 especially if that's where libdpfj.so is Nov 29 05:41:57 nerdboy, in make file it looking like LDFLAGS = -lm -lc $(CFLAGS) -L $(LIB_OUT_DIR) -ldpfpdd -ldpfj so i want to change it as LDFLAGS = -lm -lc $(CFLAGS) -L./ $(LIB_OUT_DIR) -ldpfpdd -ldpfj right? Nov 29 05:54:27 nerdboy, actually i am fresher to yocto so i am confused,can you help me ? Nov 29 06:06:52 looks like $(LIB_OUT_DIR) resolves to . Nov 29 06:07:54 then it might be better to set LIB_OUT_DIR=${S} (or whatever dir . is) and pass it via EXTRA_OEMAKE Nov 29 06:25:06 linu: whatever dir under the build/src dir has the libraries in it, append it to ${S} Nov 29 06:25:50 it might be ${S}/libs or something Nov 29 08:24:17 'morning.... just to get my thinking set straight - is the following correct? Nov 29 08:24:33 1) local.conf and bblayers get *always* parsed Nov 29 08:25:11 2) any conf file included from local.conf (also recursively) gets always parsed Nov 29 08:25:38 3) a bb file gets only parsed when it has to fulfill a specific action, like do_compile, do_package, etc. Nov 29 08:25:41 ? Nov 29 08:44:44 LetoThe2nd: I think you are correct if you be parse means it will actually be used for something. All recipes are parsed when you run bitbake, even though it's not used (try creating a dummy recipe with an error, and you'll see bitbake won't continue). Nov 29 08:45:19 erbo: thanks - yes, i actually mean "used" instead of "parsed" Nov 29 08:57:07 LetoThe2nd: in fact bitbake will parse conf/bitbake.conf (you will find it in oe-core/meta) Nov 29 08:57:27 bitbake.conf is the one that includes all other conf files, in a specific order. Nov 29 08:57:33 grep for include/require in that file. Nov 29 08:57:40 ndec: aaaah yes. Nov 29 08:57:49 all recipes are pasrsed once at the beginning, one by one. Nov 29 08:58:19 for each recipe, bitbake.conf is parsed, then the .bb file (which can have additional include/require/inherit), then .bbappend files Nov 29 08:58:38 ndec: delayed enlightenment coming from late night tinkering :) Nov 29 08:59:04 as discussed last night, any variable change in a .bb file will only be visible in that bb file, it cannot impact another bb file Nov 29 08:59:17 yeah i think i got my head around that by now Nov 29 08:59:37 well, from my own experience... it is a relief once you actually understand that ;-) Nov 29 08:59:54 everything is much clear after that! Nov 29 09:00:08 hell yeah. Nov 29 09:03:47 so the magic is mostly in ln.~650.ff of bitbake.conf, right? Nov 29 09:04:22 and i assume order ir important, so local.conf is pretty much near the top Nov 29 09:05:50 yes, the order is important, since you are setting variables in these files, so you get to see which file is able to override the others! Nov 29 09:06:31 in fact looking at bitbake.conf gives you lots of information in general... that's where most variables are initialized, so you will find lots of info there. Nov 29 09:07:10 ndec: so the magic in getting the correct machine config pulled in is basically that local.conf sets MACHINE, and bitbake.conf uses that a few lines later for include conf/machine/${MACHINE}.conf Nov 29 09:07:17 (as an example) **** BEGIN LOGGING AT Fri Nov 29 09:18:38 2013 Nov 29 09:20:37 Hi! I'm using yocto on a gumstix (overo). After an advice yesterday I tried to upgrade from dylan to dora, but are having some problems when building. I'm using hob and starting from a gumstix-console-image recepie. I've added bluez5 and some other packages from the GUI. Nov 29 09:21:35 The build completes, but when I boot there are not much there. lsmod is empty, and none of the packages I've choosen is there. When I look at the recepies screen in hob and search for "kernel" nothing is included. Nov 29 09:22:22 Does anyone know what I can be doing wrong? Isn't hob working on dora? It worked fine for me @ dylan branch. Nov 29 10:11:19 morning Nov 29 10:14:05 morning all Nov 29 10:14:07 my syslog disappear on every reboot, (/etc/fstab : tmpfs /media/ram tmpfs defaults 0 0) is there on option on yocto to disable this? Nov 29 10:14:55 (sry this is tmpfs /var/volatile tmpfs defaults 0 0) Nov 29 10:16:30 /var/log -> volatile/log Nov 29 10:18:50 should be in th default volatile config, which is easy to change Nov 29 10:19:11 you can make a bbappend for that Nov 29 11:04:05 As a non-advanced user I got to say that it's abit annoying that hob excludes the whole package-group if you exclude one package within it. E-g- I just excluded bluez4 and package-group-base was removed... Nov 29 12:02:45 does anyone recall the problem with ICU on ppc? Nov 29 12:43:31 rburton: there is something in the bugzilla however basically icu only works on the endian it was built upon Nov 29 12:47:47 ah yes. so its more "interesting" than "ppc" Nov 29 12:48:24 maybe we should make our ppc recipe check host and target endian, and break Nov 29 12:48:37 icu recipe, even Nov 29 12:54:59 ICU is certainly one of those things we need to ptest Nov 29 13:06:30 rburton: yes to all the above Nov 29 13:06:42 rburton: we probably should cause it to fail cross endian Nov 29 13:06:57 any idea what a reliable BE target is? Nov 29 13:13:08 rburton: ppc? Nov 29 13:29:34 I'm trying to run yocto on a gumstix with bluez5, but there are some incompability issues with some packages that requires bluez4 - like ofono and neard. Can I blacklist those modules somehow, and what is the best way of doing that? Nov 29 13:41:35 erija952_: if you have no need you can easily disable those in your DISTRO_FEATURES so they'll never be pulled in Nov 29 13:43:16 Ok, can you point me to some reference of how to do that? Nov 29 13:44:01 DISTRO_FEATURES_remove = "bluetooth nfc" Nov 29 13:44:12 (for those examples in particular) Nov 29 13:48:01 rburton: In local.conf? Can I add that for modules like ofono, or does it need to be whole "features"? Nov 29 13:49:47 features, otherwise the dependency chain can still come in other ways Nov 29 13:53:14 bluelightning: ping Nov 29 13:53:35 lpapp: pong Nov 29 13:53:53 bluelightning: if someone uses an external toolchain, then the wrong C++ library is getting installed? Nov 29 13:54:05 bluelightning: or is it guaranteed somehow that the corresponding? Nov 29 13:54:39 lpapp: not sure, sorry; I don't have a lot of experience with external toolchains Nov 29 13:55:03 I guess I need to ask kergoth Nov 29 13:55:18 because Yocto builds its own Nov 29 13:55:52 and that is probably the one shipped to the image by default, not the external toolchain's library. Nov 29 13:56:04 so basically C/C++ applications will not work on Yocto this way. Nov 29 13:56:40 lpapp: it depends how the external toolchain is configured Nov 29 13:57:19 lpapp: sometimes it packages up the external c++ lib Nov 29 14:03:40 RP: sometimes means? :) Nov 29 14:04:21 lpapp: meaning it depends on what the external toolchain recipe does. Some do this, some might rebuild it Nov 29 14:04:43 lpapp: presumably you have the recipe so you can look and see... Nov 29 14:54:05 Not sure if this is a bug or not, but I think so: If I have a recipe that installs a file with a given group owner that exists in tmp/sysroots/x86_64-linux/etc/group all is fine. If the group is not present I get an error, which is expected. However, if the group file does not exist in the sysroot, any group that exist in /etc/group will be accepted... (The same holds true for users.) Nov 29 14:57:11 Saur: That does sound suboptimal. Its the fallback mode of pseudo Nov 29 14:58:48 RP: Question is what would happen if one installed empty files when the sysroot is first created, until base-passwd is installed. Nov 29 14:59:28 Saur: I suspect pseudo would have a fit :/ Nov 29 14:59:49 Probably true... :/ Nov 29 15:00:04 Saur: I think we're likely going to have to install base copies with the standard users in Nov 29 15:03:40 RP: Should I add a ticket about this to bugzilla? Nov 29 15:09:36 Saur: yes please Nov 29 15:14:08 RP: Ok, will do. Nov 29 15:19:02 Saur: you could send patches? :) Nov 29 15:22:45 RP: Well, I do not know what the right thing to do is... Nov 29 15:35:35 Saur: The only solution is probably to check a static list into OE-Core which puts our use of base-passwd into quesiton Nov 29 15:41:56 RP: I think I'll add a ticket, and then someone will get the honors of analyzing the problem, and come up with a good solution. ;) Nov 29 15:43:25 Saur: we're running out of "someone"s Nov 29 15:45:00 RP: Well, as long as it is in the system, it will at least not be forgotten (I hope)... It is probably not a major problem as OE has been used for quite a while... Nov 29 15:47:04 Saur: agreed, its better in there than not Nov 29 15:59:01 hello Nov 29 15:59:29 kernel modules-.tgz contain all modules Nov 29 16:00:20 but core-image-minimal contains only /lib/modules//modules.* Nov 29 16:01:51 where did things go wron?.. Nov 29 16:02:52 sledges: that's intentional, core-image-minimal is intended to be small Nov 29 16:03:05 oh Nov 29 16:03:19 sledges: if you want all built kernel modules to be part of the image, you can add the "kernel-modules" package to IMAGE_INSTALL Nov 29 16:03:47 or if you prefer, you can add individual kernel-module- packages as needed Nov 29 16:04:00 very nice Nov 29 16:13:50 bluelightning: I've added IMAGE_INSTALL += " kernel-modules" to build/conf/local.conf, but nothing seem to have changed Nov 29 16:15:00 sledges: if you use core-image-minimal, it will reset IMAGE_INSTALL variable Nov 29 16:15:08 so your change is likely going to be lost. Nov 29 16:16:21 sledges: I'd suggest having a look at this section of the manual: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage Nov 29 16:16:24 you can use core-image-base which includes package-core-boot and package-base-extended (which in turns includes all the modules) Nov 29 16:16:53 or you can read what bluelightning just said ;-) Nov 29 16:19:20 thank you fellows, building core-image-base ndec ^_^ certainly a good read bluelightning Nov 29 16:21:26 humm, core-image-base might not fit through tftp into board's memory Nov 29 16:21:49 yes, core-image-base is quite large Nov 29 16:22:15 * sledges needs to rtfm ^_^ Nov 29 16:55:30 RP: Submitted: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5612 Nov 29 16:55:31 Bug 5612: normal, Undecided, ---, saul.wold, NEW , If no passwd/group files exist in sysroot, users/groups are picked up from /etc Nov 29 17:25:01 moin Nov 29 23:42:25 If I have a cpio.gz rootfs, how can I unpack, edit a file, and repack it? Are there any instructions online? Nov 30 00:05:44 maybe not yocto-specific, but yeah there are tools for that Nov 30 00:12:27 I found this: http://www.wiki.xilinx.com/Build+and+Modify+a+Rootfs Nov 30 00:12:31 Seems to be working fine. **** ENDING LOGGING AT Sat Nov 30 02:59:59 2013