**** BEGIN LOGGING AT Tue Dec 09 02:59:58 2014 Dec 09 05:39:15 anyone has encountered "no package provides" error? Dec 09 05:47:46 chankit: getting several results in google search for it Dec 09 06:30:20 TypoNAM: I did too but I think my problem is more complicated than that...it's about llvm+clang thing Dec 09 07:10:16 Hi. Anyone who knows a good way to add a DEPENDS within a recipe on a specific task? DEPENDS itself will just ensure that you await do_configure (but for example do_unpack can be done in parallell), but I want to ensure that if recipe A depends on B, A-->do_unpack MUST wait until B is done.. Dec 09 07:20:49 zerus: May I know what's the occasion when do_unpack must be done sequentially? Dec 09 07:36:44 zerus, In recipe A: do_unpack[depends] = "A:do_install", or whatever task you want to depend on. Dec 09 07:37:12 Of course, it should be "B:do_install" and not A:do_install... Dec 09 08:20:29 good morning Dec 09 08:32:28 AndersD: Thx I will give it a try. I started elaborate with lockfiles but this seems like a far less complex solution. Dec 09 08:35:54 Has anybody used yocto to build minimal base images for docker? Dec 09 08:49:51 <_qwerty_> Hi all, I need to add libxml2 to my custom image or install rpm... how I can do? Dec 09 08:57:11 chankit: It is in a recipe with sub .bb files that are copying a external git repo in recipe specific task (that is run before do_fetch), this is a real strange solution I know, but it's due too legacy reasons.. In this situation a HEAD.lock file might occur when pkg B are doing do_fetch and in theory pkg A are doing do_unpack, then during pkg A do_unpack the HEAD.lock is removed due too that pkgB has finished do_fetch.. Then bitbake wil Dec 09 08:57:41 chankit: ..HEAD.lock. This is a very rare case but it happens from time-to-time. Dec 09 08:59:22 chankit: But AndersD might work since then I can add a depends on do_unpack[depends] = B:do_ Dec 09 08:59:39 chankit: * AndersD suggestion it should be ... =) Dec 09 09:29:45 zerus: thanks for the heads up...learned a new thing today Dec 09 09:39:16 morning all Dec 09 09:51:14 AndersD: I have verified your suggestion and it solves my problem. Thanks! Dec 09 10:01:17 zerus, Good to hear! Dec 09 10:47:37 <_qwerty_> How I can set to load modules in my custom image? Dec 09 10:51:20 _qwerty_: http://www.yoctoproject.org/docs/1.7/ref-manual/ref-manual.html#var-KERNEL_MODULE_AUTOLOAD Dec 09 10:59:27 <_qwerty_> ndec: ok but I have to specified all modules? Dec 09 10:59:52 <_qwerty_> ndec: because actually not modules are loaded Dec 09 11:01:23 yes, you need to specify each module Dec 09 11:07:25 I would imagine you would do KERNEL_MODULE_AUTOLOAD += "" to avoid wiping out any existing value Dec 09 11:08:08 it may be worth noting that driver modules for hot-pluggable modules are generally loaded through udev these days, so you may alternatively consider creating a udev rule depending on the situation Dec 09 11:08:17 hot-pluggable devices, that is Dec 09 11:12:32 Hi! So I'm trying to modify the following recipe http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/meta-ivi/recipes-extended/node-state-manager/node-state-manager_2.0.0.bb so that a plugin library is provided in a seperate package. The reason is that I want to replace that library with another library from a diferent package. I created this: @@ -28,11 +28,11 @@ S = "${WORKDIR}/git" Dec 09 11:12:32 Dec 09 11:12:32 inherit pkgconfig autotools-brokensep systemd Dec 09 11:12:32 Dec 09 11:12:35 +PACKAGES =+ "${PN}-statemachine-example" Dec 09 11:12:37 SYSTEMD_PACKAGES = "${PN}" Dec 09 11:12:39 SYSTEMD_SERVICE_${PN} = "nodestatemanager-daemon.service" Dec 09 11:12:41 SYSTEMD_AUTO_ENABLE = "disable" Dec 09 11:12:43 Dec 09 11:12:45 - Dec 09 11:12:47 do_configure_prepend() { Dec 09 11:12:49 mkdir -p m4 Dec 09 11:12:51 mkdir -p NodeStateAccess/doc Dec 09 11:12:53 @@ -48,3 +48,4 @@ FILES_${PN} += "\ Dec 09 11:12:55 ${systemd_unitdir}/system/nodestatemanager-daemon.service \ Dec 09 11:12:57 " Dec 09 11:12:59 FILES_${PN}-dev += "${datadir}/dbus-1/interfaces/" Dec 09 11:13:01 +FILES_${PN}-statemachine-example = "${libdir}/libNodeStateMachine.so" Dec 09 11:13:14 I can see that the file is provided in the statemachine package Dec 09 11:13:34 but when I try to replace that from another package I get a conflict when building the package Dec 09 11:13:54 he recipe node-statemachine-vcc is trying to install files into a shared area when those files already exist. Dec 09 11:14:09 hi, anyone who know how to refer the layer directory of the currently running recipe, using bitbake environment variable? Dec 09 11:14:18 ..WARNING: node-state-manager-statemachine-example-2.0.0 was registered as shlib provider for libNodeStateMachine.so, changing it to node-statemachine-vcc-0.1 because it was built later Dec 09 11:15:21 So basicallly what do I need to do in the other recipe to replace the package node-state-manager-statemachine-example? Dec 09 11:15:26 i found LAYERDIR, but that one is not available outside local.conf Dec 09 11:19:09 johnnykar: do you expect both recipes' packages to coexist on the target? if so, they shouldn't really be providing the same library file - are they currently? Dec 09 11:19:28 stiandre: can you explain what you're trying to do? Dec 09 11:21:25 bluelightning well no I don't want them both to exist, I want to override the meta-ivi lib Dec 09 11:21:43 bluelightning: hi, yes, I am trying to refer to my license file which is located at the top level of the current layer Dec 09 11:23:34 I am not sure that the COMMON_LICENSE_DIR is the correct place for our license (proprietary) Dec 09 11:32:19 johnnykar: then your recipe should have the same name Dec 09 11:33:00 stiandre: is this for LIC_FILES_CHKSUM? Dec 09 11:33:14 bluelightning: yes Dec 09 11:33:38 stiandre: ok, probably the easiest way is to set your own custom variable in your layer's layer.conf from LAYERDIR and then use that in the recipe Dec 09 11:34:03 bluelightning: ok, how to I do that? Dec 09 11:34:19 stiandre: the other alternative would be to ship the license file with the other files the recipe fetches, that is supposed to be how LIC_FILES_CHKSUM works Dec 09 11:34:39 (or rather, that's the manner in which it is intended to be used in most cases) Dec 09 11:35:04 bluelightning: ok, thanks Dec 09 11:40:27 bluelightning: well I don't wan't to replace the recipe, just the file provided by it ( libNodeStateMachine.so ) Dec 09 11:41:41 bluelightning: I just want to replace one of the packages provided by node-state-manager (ie node-state-manager-machine-example) Dec 09 11:42:18 johnnykar: in fact if this is just a slight patch to the packaging of the recipe then I think you'd want to use a bbappend Dec 09 11:44:54 bluelightning: the node-state-manager recipe ships a "dummy" plugin by default. In order to actually use the component for something useful this needs to be replaced, so it probably makes sense to adapt the original recipe to make that as easy as possible Dec 09 11:44:58 bluelightning: sure I could do that, but there should be a way to do this without doing a bbappend since the libNodeStateMachine.so is just a stubbed version that is supposed to be replaced to get real functionality. Dec 09 11:59:27 is there a good way to find out which package I have to activate to install a specific file? Dec 09 12:00:21 e.g. I want to add lsblk which is not available in core-image-base Dec 09 12:04:22 johnnykar: as far as I can tell from what you've told me, given the current state of that layer, a bbappend is the easiest way to solve the issue Dec 09 12:04:32 erbo: johnnykar: I would suggest talking to the maintainer of the layer to make things easier there Dec 09 12:04:40 (of meta-ivi, I mean) Dec 09 12:05:48 Hi, Im working with 3.14 kernel and trying to bring up tun/tap however with no success. Anyone can support with that? Dec 09 12:07:09 jaeckel: lsblk is in util-linux Dec 09 12:07:35 bluelightning: yeah I know that now, by googling Dec 09 12:07:55 jaeckel: there is a small utility called oe-pkgdata-util that can help to find that sort of info, e.g. in my case I ran: oe-pkgdata-util find-path tmp/sysroots/qemux86-64/pkgdata/ *lsblk Dec 09 12:08:21 you do have to have built the recipe which provides the package containing the file though Dec 09 12:11:48 okay thanks! I realized already that providing something like apt-file is impossible for the yocto architecture, but it would be nice to have an easy way to search e.g. online Dec 09 12:14:23 e.g. by providing a tool the meta layer maintainers can use to index the build output and send it to some central point Dec 09 12:17:55 Can anyone guide me on how to change desktop theme in Yocto Dec 09 12:18:09 I wanr to change matchbox theme Dec 09 12:24:06 jaeckel: it has certainly been considered, and the Toaster web UI can help with querying that sort of thing (although I don't think there are plans for a live instance of Toaster) Dec 09 12:24:31 jaeckel: one problem might be that the contents of packages can be dependent on the build parameters e.g. the selected target machine Dec 09 12:25:11 ok Dec 09 12:25:49 I have read that matchbox support only one window Dec 09 14:59:13 well howdy folks Dec 09 15:08:56 anyone using BBB with poky master lately? Dec 09 15:11:22 <_qwerty_> How I can add an entry to modules.alias Dec 09 15:23:41 Just a quick question. I would really love if I could get some guidance on getting started here..is this the best place to ask ? Dec 09 15:25:18 torbit: its a good place to ask, as the yocto quick start guide is a good thing to read and try :) Dec 09 15:27:23 LetoThe2nd: is this what is located here https://www.yoctoproject.org/documentation/build-appliance-manual Dec 09 15:27:28 :-) Dec 09 15:28:52 torbit: more like http://www.yoctoproject.org/docs/1.7/yocto-project-qs/yocto-project-qs.html Dec 09 15:29:03 thank you :-) Dec 09 15:29:37 let me try brush through that really fast Dec 09 15:31:00 torbit: why not actually *read* and try to understand it, without brushing and fasting? ;) Dec 09 15:33:22 yeah…thats what I meant..sorry :-) thanks though Dec 09 15:35:35 erbo: it would be the best to not build the "dummy" plugin, for example via a ./configure switch. But such a switch sadly does not exist. If it would, the recipe could be changed to have a packageconfig with which you could include or not include the statemachine Dec 09 15:36:41 what is the correct mailing lists for meta-yocto-bsp patches? Dec 09 15:49:57 seems like really cool stuff Dec 09 16:21:59 where do I set host gcc binary name to bitbake with BUILD_CC? As env variable when calling bitbake, in local.conf, or in a recipe? Dec 09 16:46:46 mcfrisk: i don't really see how it'd make sense to set BUILD_CC for just one recipe, do you? :) what about all the others? Dec 09 16:46:51 set it in local.conf Dec 09 21:21:44 otavio: new x server breaks fsl-arm x driver https://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/123/steps/BuildImages_1/logs/stdio **** ENDING LOGGING AT Wed Dec 10 02:59:59 2014