**** BEGIN LOGGING AT Tue Nov 12 02:59:58 2013 Nov 12 06:47:29 rburton, ping Nov 12 06:49:30 what's the correct way to override DEFAULT_PREFERENCE=-1 ? Nov 12 06:50:01 do I need a .bbappend for each recipe? Nov 12 06:55:06 no, a PREFERRED_VERSION should work Nov 12 06:55:07 hmmm Nov 12 08:03:34 Stygia, thanks for yesterday help Nov 12 08:03:38 Stygia, thanks for yesterday help. Nov 12 08:04:03 I've got another question and this is a big one...about workflow. Nov 12 08:05:00 We are working with yocto and freescale extra layers, because we have our custom board based on Freescales imx board. Nov 12 08:05:56 The problem is that we have many different projects with different board revisions (configurations) and we will probably have different boards in future. Nov 12 08:06:42 Every project is considered as a separate linux distribution (because of different needed packages, different recipe configurations...etc) Nov 12 08:07:52 We would like to have this all maintanabli in some way that if I needed an image for some projet I could just compile it without any configurations Nov 12 08:08:22 The thing is that we probably could have different machines/machineconfigurations for the same project/distribution/recipecombination Nov 12 08:08:41 It would be easy if we simply had 2 machines Nov 12 08:09:49 But we have different revisions of the same board, which are "cut down" - manu hardware parts/periherals removed, where we would need a different kernel branch/repo Nov 12 08:12:11 Separate layer for each project seems fine, but then there is kernel layer, which means kernel+boardrevision layer - and that seems to much. Nov 12 08:12:35 Separate machine for each revision seems cumbersome too. Nov 12 08:12:55 What would be anyone's workflow in this situation? Nov 12 08:13:49 if you can't have more 'runtime' detection, then i would opt for 1 layer with several machine configs. machine config can 'include' files, so you can minimize the duplication. Nov 12 08:15:39 Hmm but each project should have a different recipe configs. In example kernel defconfig for each project should be stripped down to minimal - In one case I need iptables and bluetooth, in other project I need other different stuff. Nov 12 08:17:11 each machine can have its defconfig. are you saying you don't want that? Nov 12 08:18:45 no not really. I want to use the same machine/board for different project too. Nov 12 08:19:29 chocis: you can have one core BSP which you then just tweak in a given layer... Nov 12 08:19:52 e.g. tweak the kernel defconfig in that layer Nov 12 08:20:03 there is also config fragment (.cfg file) that can be used to tweak defconfig Nov 12 08:20:20 Yes, tweaking in the config fragment format works well Nov 12 08:20:34 the cfg could be specific to distro or machine (or both) Nov 12 08:23:20 Thank you for your answers. Thans of solutions we thought of. Then I could enbale one projectSpecific layer at a time. Nov 12 13:11:17 Are there any llvm+clang bitbake recipes? I found some in meta-openembedded for llvm but none for clang. Nov 12 14:47:33 chocis: use DTB if possible Nov 12 15:23:36 hi, Nov 12 15:24:37 dose bitbake edit the BBFILE_PRIORITY of a layer even if i set it manually ? Nov 12 15:30:35 "edit"? "set it manually"? Nov 12 15:30:48 bitbake doesn't pull priorities out of thin air, it reads them from layer.conf Nov 12 15:34:45 in the dev-manual section 5.1.6. Prioritizing your Layer, it is stated: "You can either specify the priority manualy, or allow the build system to calculate it based on the layer's dependencies." Nov 12 15:36:36 and when i have some extra layers configured in to the build (bblayers.conf) some layers will have a different priority set to them when executing "bitbake-layers show-layers" Nov 12 15:36:49 so why is that ? Nov 12 15:37:19 FYI all my layers have a manually set priority Nov 12 16:01:15 YPTM: jzhang on the call Nov 12 16:01:25 YPTM: Matthew on the call Nov 12 16:01:37 YPTM : ross finding the phone Nov 12 16:01:37 YPTM: Nitin joined the call Nov 12 16:01:46 YPTM: belen on the call Nov 12 16:02:06 The Yocto Project Tech Meeting Con-Call will be starting at the top of the hour Nov 12 16:02:06 Dial-in number: 1.972.995.7777 / Participant passcode: 42001078 Nov 12 16:02:06 This call is open to all and the channel remains open to discuss any topic Nov 12 16:02:23 YPTM: Björn is on the call Nov 12 16:02:47 YPTM: Scott Rifenbark is on the call Nov 12 16:02:50 YPTM: Bruce is on the call Nov 12 16:02:54 YPTM: Saul is on Nov 12 16:03:29 YPTM: Darren has joined Nov 12 16:03:32 YPTM: Michael here. Nov 12 16:03:51 YPTM: Polk is here Nov 12 16:03:51 YTPM: Richard is here Nov 12 16:03:52 YPTM: Tom Z on Nov 12 16:04:02 * rburton on Nov 12 16:04:11 YPTM: pidge is also on the call Nov 12 16:04:16 YPTM: Björn is on the call Nov 12 16:04:39 YPTM: Open - ptest Nov 12 16:05:28 YPTM: any open? Nov 12 16:05:58 I can talk briefly about performance either as team sharing or as an open... Nov 12 16:06:18 YPTM: Corneliu joined Nov 12 16:06:39 YPTM: Mark is here Nov 12 16:07:30 oe-selftest feature: https://bugzilla.yoctoproject.org/show_bug.cgi?id=4740 Nov 12 16:07:31 Bug 4740: enhancement, High, 1.6, corneliux.stoicescu, ACCEPTED , Consider providing an oe-selftest script to run automated tests against bitbake tools Nov 12 16:08:13 https://wiki.yoctoproject.org/wiki/Yocto_1.6_Features Nov 12 16:10:04 * RP has just pushed Nov 12 16:11:20 new git fetching code is EPIC Nov 12 16:11:23 for the record Nov 12 16:11:49 :) Nov 12 16:15:31 sgw_: Stumbled upon something the other day. In July you added inclusion of "conf/distro/include/security_flags.conf" to "meta-yocto/conf/distro/poky-lsb.conf b/meta-yocto/conf/distro/poky-lsb.conf". You may want to change that to "conf/distro/include/security_flags.inc" as that is what the file is called. Nov 12 16:17:51 and this is why we should use "require"... Nov 12 16:18:15 :) Nov 12 16:24:09 dvhart: thanks for clarifying that Nov 12 16:26:38 RP -- would it make sense to -not- generate the debug info on natives? Nov 12 16:26:48 (or generate minimal)? Nov 12 16:30:39 ok Nov 12 16:32:36 YPTM: Bruce has to drop. Nov 12 16:33:51 zeddii: I can't wait for the kernel files filtering ;-) Nov 12 16:35:58 halstead: "burning" could be taken as a challenge by some people on the team :) Nov 12 16:37:48 halstead: sounds good, thanks for keeping it all working! :) Nov 12 16:38:16 Thank you RP. :) Nov 12 16:39:51 YPTM: thank you all for joining the meeting. Have a niceday/evening Nov 12 16:42:29 Song_Liu: Thanks! Nov 12 18:04:43 hi, when I am flashing the rootfs generated by Yocto, I am experiencing this issue: Nov 12 18:04:47 zcat /proc/config.gz | grep 6650 Nov 12 18:04:49 # CONFIG_SENSORS_MAX6650 is not set Nov 12 18:05:13 even though our defconfig has it: CONFIG_SENSORS_MAX6650=y Nov 12 18:05:20 what is happening? Nov 12 18:07:54 we basically do not use the linux kernel package from core. Nov 12 18:08:05 because we need to stick to a different version due to customization. Nov 12 18:08:18 but anyway, I thought defconfig changes should appear in the final rootfs imagE? Nov 12 18:13:58 lpapp: if you take that defconfig and put it into a kernel tree, then run "make oldconfig", does it change the config options? Nov 12 18:14:12 lpapp: its possible the defconfig was adjusted as it wasn't 100% valid Nov 12 18:18:31 RP: no Nov 12 18:19:00 I edited it manually. Nov 12 18:19:05 perhaps I need to enable some deps as well Nov 12 18:19:17 is there a simple way to do make menuconfig within the Yocto environment? Nov 12 18:20:06 lpapp: bitbake virtual/kernel -c menuconfig Nov 12 18:22:49 RP: ERROR: No valid terminal found, unable to open devshell Nov 12 18:22:49 ERROR: Function failed: do_menuconfig Nov 12 18:24:49 hmm, I may need ncurses. Nov 12 18:25:28 hmm, that is already installed in the debian chroot, strange. Nov 12 18:25:32 What else could it be? Nov 12 18:25:57 lpapp: its trying to start a terminal of some kind, i.e. use screen, or some other terminal app (e.g. over X) Nov 12 18:26:10 ncurses-term maybe? Nov 12 18:26:29 lpapp: no, it needs to open a new window to handle the input/ouput Nov 12 18:26:36 just installed that package. Nov 12 18:26:36 same error. Nov 12 18:26:55 why is it not working with sudo systemd-nspawn environment by default? Nov 12 18:27:44 lpapp: can you install screen? Nov 12 18:29:17 RP: yes Nov 12 18:29:59 RP: http://pastebin.kde.org/p03379cen Nov 12 18:30:22 lpapp: try "screen -r devshell_20537" Nov 12 18:33:53 RP: the screen is hanging, so I cannot try. Nov 12 18:34:13 and systemd-nspawn only allows one connection. Nov 12 18:35:05 I will rerun this after running screen inside systemd-nspawn Nov 12 18:35:15 RP: hmm, screen Nov 12 18:35:15 Cannot open your terminal '/dev/console' - please check. Nov 12 18:35:25 perhaps something is not bound to the stuff from the real host? Nov 12 18:35:37 lpapp: yes, probably Nov 12 18:35:54 lpapp: it can use X based terminals too if some of those were available with a suitable DISPLAY setting Nov 12 18:36:29 lpapp: it just needs some way of multiplexing the terminal (since in theory you could have multiple targets specified) Nov 12 18:36:30 I thought the whole deal with nspawn it sets up everything for you. :D Nov 12 18:41:05 RP: it is kind of strange. Nov 12 18:41:42 lpapp: sounds like your kernel should be the preferred one Nov 12 18:42:08 mr_science: yes Nov 12 18:42:13 but if I cannot even configure it. :p Nov 12 18:42:20 you did say the build defaults to a different kernel than the one you actually use, right? Nov 12 18:43:09 hmm? Nov 12 18:44:00 i'd try getting it set as your default and the dev-shell into it Nov 12 18:44:09 s/the/then/ Nov 12 18:44:22 the problem is that I cannot use screen Nov 12 18:44:40 what about vnc and xterm? Nov 12 18:45:03 I do not have vnc. Nov 12 18:45:08 I only systemd-nspawn for now. Nov 12 18:45:20 so you have no way to dev-shell? Nov 12 18:46:18 set this in the appropriate machine include file: PREFERRED_PROVIDER_virtual/kernel = "your_kernel" Nov 12 18:46:43 the manually bitbake -b kernel_recipe -c patch Nov 12 18:47:07 cd /path/to/work/dir and run make oldconfig and whatnot Nov 12 18:58:05 mr_science: I am not sure you are getting it, but I do not have screen access. Nov 12 18:58:14 so I cannot run make menuconfig Nov 12 18:58:24 and I would not like to patch the txt file manually since I apparently failed at that, already. Nov 12 18:58:30 I would like to use the UI. Nov 12 18:58:57 I guess I will need to figure out how to use screen or xterm with systemd-nspawn. Nov 12 18:59:04 currently, I have no clue. :D Nov 12 18:59:09 I thought it should just work (tm). :) Nov 12 19:08:17 Can someone give me pointers on how to use the gitsm fetcher for fetching submodules from a Git repository. I need an example of it's use? Nov 12 19:15:28 Anyone ever use the gitsm fetcher? Nov 12 20:32:59 Glenn__: I've used it.. Nov 12 20:33:36 Glenn__: I just changed the git:// to gitsm:// Nov 12 20:55:53 kergoth: is checking tmp/work/all-poky-linux/resolvconf/1.74-r0/image/ a good way to list all files installed by resolvconf? Nov 12 20:57:20 cause if so, it's putting nothing in /etc/network/if-up.d/, and also isn't installing anything with a bash shebang Nov 12 20:58:22 (although /etc/dhcp/dhclient-enter-hooks.d/resolvconf has no #!, and a comment saying it's a script fragment that uses bashisms) Nov 12 20:59:58 ther shouldn't be a schebang. schebangs are only of any use whatsoever for something executed directly Nov 12 21:00:10 those sorts of hooks are sourced, usually Nov 12 21:00:29 but if its not installing anything there, that sounds like a bug/oversight in the recipe/package, to me Nov 12 21:01:35 kergoth: yeah, comment says it is to be sourced by dhclient. i don't get how dhclient is supposed to know it's a bash script, though - does dhclient always use bash, or is it assuming that /bin/sh is bash? Nov 12 21:02:56 dhclient knows what it is because of where it is Nov 12 21:03:04 its hooks are shell scripots by definition Nov 12 21:03:11 it doesn't support any arbitrary executable Nov 12 21:03:19 kergoth: i meant, bash as opposed to POSIX sh Nov 12 21:03:36 I don't understand the question Nov 12 21:03:43 kergoth: but that was because i didn't realise that pulling it bash automatically makes the /bin/sh symlink point to it, so nm Nov 12 21:03:47 if it's being sourced, then by definnition what's doing the sourcing is a shell script Nov 12 21:03:59 and what that shell script is using depends on *its* schebang Nov 12 21:04:39 kergoth: i meant, "how does dhclient know to use bash, rather than BB sh", but that was because i hadn't realised that depending on bash changed /bin/sh to point to bash, rather than just making bash available as an alternative interpreter Nov 12 21:06:38 if it did require bash, then it would have an appropriate shebang indicating that. bash can run posix sh scripts, just not vice versa. so bash replacing /bin/sh shouldn't harm a thing Nov 12 21:07:03 yeah, i only asked the question because i didn't realise the symlink was changed Nov 12 21:10:13 gotcha Nov 12 21:10:39 kergoth: did you say the hook should be installed in /etc/network/if-up.d/? Nov 12 21:12:14 yep, at least thats where it goes on debian systems, shoudl be the same there Nov 12 21:13:11 thanks. debian's tarball (SRC_URI for the recipe) has a "resolvconf.000resolvconf.if-up", so it should just be one more install line. i'll see if i can fix it Nov 12 21:19:24 indeed. good luck with it **** ENDING LOGGING AT Wed Nov 13 02:59:58 2013