**** BEGIN LOGGING AT Fri Aug 26 02:59:59 2016 Aug 26 03:30:06 What does it mean when bitbake prints a layer name with a git hash, e.g. 'meta-custom = "master:239294294293482394"` Aug 26 03:30:27 The hash doesn't mash any particular commit from the git repo that I can find Aug 26 03:30:30 *match Aug 26 03:35:07 https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles suggests it's a layer hash rather than a git hash Aug 26 04:37:09 @hweaving if you haven't already discovered it, you can set 'SRCREV = "${AUTOREV}"' to track the latest version of your target repository Aug 26 04:39:28 pwebster: Thanks, I think someone did mention that -- useful for development Aug 26 04:40:29 @hweaving Alternatively, there's devtool and workspaces where you can temporarily point the recipe at an externally checked out copy of your source that you can modify, build and deploy through bitbake. Rinse and repeat until you're happy and then commit and bump the SRCREV in the recipe Aug 26 04:43:56 Interesting Aug 26 04:51:45 I have a nginx recipe that is definitely running do_install (I tried echoing into a file in /tmp), but which fails to create an init.d directory Aug 26 04:51:59 Is there something in Yocto which might delete /etc/init.d after the nginx recipe runs? Aug 26 04:57:29 I would first check the staging area for the recipe. I believe you should see everything that is installed by a specific recipe in the build/tmp/work////image directory Aug 26 04:58:06 if your do_install does: Aug 26 04:58:26 install -d ${D}${sysconfdir}/init.d Aug 26 04:58:47 pwebster: It does precisely that Aug 26 04:58:52 install -m 0755 ${WORKDIR}/init_script ${D}${sysconfdir}/init.d/nginx Aug 26 04:59:58 then you should have a 'FILES_${PN} += "${sysconfdir}/init.d/nginx"' line as well Aug 26 05:00:48 That's not in the FILES_${PN} setup Aug 26 05:03:00 pwebster: I had added "systemd" to the inherit list for nginx, and removing that populated init.d properly Aug 26 05:03:26 pwebster: However, I originally added it because nginx wasn't autostarting. I'll see what happens. Aug 26 05:05:18 Those were the things I had to do for the recipe I was writing (not for nginx tho) Aug 26 05:05:34 Yeah, I'm back to my original issue. I can do "systemctl start nginx", but I want that to happen automatically Aug 26 05:06:02 Someone suggested systemd had some autostart variables, but that requires inheriting systemd which breaks the rest of the nginx recipe. Maybe there's another way to add autostart service code in Yocto? Aug 26 05:07:58 Sorry, I'm stuck with sysvinit on my system at the moment, so I can't help much there Aug 26 05:09:37 heh, I'm learning the ways of systemd Aug 26 05:11:34 With sysvinit (ie /etc/init.d and /etc/rc*.d), the recipe uses "INITSCRIPT_xxxx" variables Aug 26 05:12:21 I think I've seen that systemd has "SYSTEMD_xxxx" equivalents, one of them had an "autostart" or something Aug 26 05:13:11 pwebster: I think so, but only if you inherit sytemd. And since this recipe already inherits update-rc.d, the systemd inheritance understandably caused the install conflict, I think. Aug 26 05:13:37 I suspect I can just add my own autostart install line Aug 26 05:13:43 ../poky/meta/classes/systemd.bbclass:4:SYSTEMD_PACKAGES ?= "${PN}" Aug 26 05:13:44 ../poky/meta/classes/systemd.bbclass:5:SYSTEMD_PACKAGES_class-native ?= "" Aug 26 05:13:44 ../poky/meta/classes/systemd.bbclass:6:SYSTEMD_PACKAGES_class-nativesdk ?= "" Aug 26 05:13:44 ../poky/meta/classes/systemd.bbclass:9:SYSTEMD_AUTO_ENABLE ??= "enable" Aug 26 05:54:23 Google is turning up other recipes that inherit both update-rc.d and systemd, so maybe there's some way to make them compatible Aug 26 06:01:31 Well, I found it Aug 26 06:01:55 If you inherit both update-rc.d and systemd, systemd.bbclass will remove your /etc/init.d directory using rm_sysvinit_initddir () Aug 26 06:02:41 I'm not sure of the proper way to work around it, though Aug 26 06:05:03 Huh, there's a chat log talking about this precise thing! https://www.yoctoproject.org/irc/%23yocto.2015-03-12.log.html Aug 26 06:05:44 Apparently the verdict was "Saur: lazy developers putting things where they don't belong really isn't behavior we should be encouraging, imo" Aug 26 06:05:52 from kergoth Aug 26 06:52:53 My solution was modifying nginx.service and nginx.inc to support pure-systemd systems. Aug 26 07:26:23 moon is not doing allah is doing Aug 26 07:26:34 stars are not doing allah is doing Aug 26 07:26:59 planets are not doing allah is doing Aug 26 07:27:10 galaxies are not doing allah is doing Aug 26 07:27:24 oceans are not doing allah is doing Aug 26 07:27:40 mountains are not doing allah is doing Aug 26 07:27:47 trees are not doing allah is doing Aug 26 07:27:55 mom is not doing allah is doing Aug 26 07:28:01 dad is not doing allah is doing Aug 26 07:28:07 boss is not doing allah is doing Aug 26 07:28:18 job is not doing allah is doing Aug 26 08:07:00 fuck you Aug 26 08:17:38 Snert: don't feed trolls, especially not those long gone already. Aug 26 08:19:22 yea, 'spose I shouldn't. Aug 26 09:55:11 hello, at what stage is my device tree dtb file generated in Yocto? how should I go about modifying it for a new board? Aug 26 10:02:11 look at http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#var-KERNEL_DEVICETREE Aug 26 10:03:27 the linux-dtb.inc file it mentions appends to the compile, install, and deploy tasks Aug 26 10:06:29 Ulfalize, thank you Aug 26 11:15:22 Hello I have a question about a bitbake recipes : I have a big repo with a lot of cmakes Aug 26 11:15:38 I can write a recipes for every cmake project i want to crosscompile Aug 26 11:15:48 but then bitbake will download the source code x times Aug 26 11:16:02 is it possible to download the source code one time and build it in different recipes? Aug 26 11:20:04 gcc does something similar with work-shared Aug 26 11:20:30 But there's also a download cache, so if it's the same repo, it shouldn't be downloaded multiple times in any case Aug 26 11:25:53 Hunk: check the bitbake variable called PACKAGES Aug 26 11:26:06 it might be documented in the bitbake documentation, not the yocto documentation Aug 26 11:26:52 that will allow you to build multiple packages in one recipe, not multiple recipes. that might not be exactly what you want Aug 26 11:27:34 * Ulfalize made PACKAGES more informative in the most recent manual version: http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-PACKAGES Aug 26 11:27:35 thank you I will check :) Aug 26 11:27:49 if it's different projects that just happen to live in the same repo, it'd be weird to build many of them in the same recipe though Aug 26 11:45:54 the problem is that multiple, independant projects in the same repo is not a common case. I don't know if yocto has an elegant way to deal with that Aug 26 11:46:19 either have one recipe for all of them or just do one recipe for each, but you won't share the work dir... Aug 26 11:57:40 yocto group on linkedin is for contributors only or users can join also? Aug 26 13:01:21 khem. just seeing your message from yesterday now. I'll look at the fragment and drop it in where it make sense. Aug 26 14:05:50 how i can set a static ip addresse with systemd Aug 26 14:07:37 i get a fixed ip addresse from somewhere but I don't understand why I get this Aug 26 14:31:57 Hunk: do you have a dhcp server on your network ? Aug 26 14:32:21 IIUC default yocto has connman installed, and connman is the one that deals with network configuration (not systemd per-se) Aug 26 14:38:10 kergoth: If you're around today, I have a file organization question Aug 26 15:41:57 khem: Also if YOU'RE around, I finally resolved the service startup problem I was having yesterday. It turns out packages inheriting both update-rc.d and systemd cause conflicts on pure systemd systems. Aug 26 15:58:47 When a Yocto recipe is described as having a version like "2.0.4+gitX", what does the gitX represent? The newest available rev on github? Aug 26 16:03:03 That's usually generated by gitpkgv.bbclass from meta-oe. see https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/classes/gitpkgv.bbclass Aug 26 16:10:55 neverpanic: Hmm, I don't see how the 'x' works in there Aug 26 16:11:00 Unless it's a wildcard for "any revision" Aug 26 16:14:15 hweaving: is it a literal X, or is it a variable? Aug 26 16:14:25 which recipe are you talking about? Aug 26 16:15:27 neverpanic: Literal X, like https://layers.openembedded.org/layerindex/branch/master/recipes/?q=uwsgi Aug 26 16:19:06 hweaving: that just seems to be an artifact of the layerindex Aug 26 16:19:14 see http://git.yoctoproject.org/cgit/cgit.cgi/meta-cloud-services/tree/meta-openstack/recipes-extended/uwsgi/uwsgi_git.bb?h=master, where it reads +${SRCPV} Aug 26 16:19:51 and http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-SRCPV Aug 26 16:21:35 neverpanic: Thanks. So it looks like SRCPV would end up being 2.0.4+2342394829384933948394 or whatever the hash is Aug 26 16:26:19 Ulfalize: Now if only you could absorb ulf` everything would be perfect :D Aug 26 16:44:46 hweaving: hmmm did you delve into the conflict if you did please file a bug report we need to solve it Aug 26 16:45:39 hweaving: hweaving X is abbreviated ( 10 chars ) SRCREV hash Aug 26 16:46:12 khem: What's the link to file a package bug report? Aug 26 16:47:31 bugzilla.yoctoproject.org Aug 26 17:20:54 JOIN Aug 26 17:21:55 First time on IRC chat so. Aug 26 17:23:36 Having trouble with zeromq on krogoth. Aug 26 17:23:48 ibc_nonshared.a(elf-init.oS): In function `__libc_csu_init': | /usr/src/debug/glibc/2.23-r0/git/csu/elf-init.c:87: undefined reference to `__init_array_start' Aug 26 17:24:30 I added: Aug 26 17:24:37 # bobt CFLAGS =+" -shared " CPPFLAGS =+ " -shared " CXXFLAGS =+ " -shared " LDFLAGS =+ " -shared " Aug 26 17:24:56 to the bb file. Aug 26 17:25:22 Does anybody have an idea of what to do? Aug 26 17:30:34 bobt: it seems you are compiling with security flags on Aug 26 17:30:50 bobt: but you are not passing these switches to linker Aug 26 17:31:15 its always best to let gcc driver do the linking with default options Aug 26 17:32:08 You mean don't pass -shared ? Aug 26 17:32:52 are you passing them from recipe ? Aug 26 17:32:54 then dont Aug 26 17:34:06 I tried Aug 26 17:34:13 CFLAGS_prepend_pn-zeromq += " -shared " Aug 26 17:34:30 CXXFLAGS_prepend_pn-zeromq += " -shared " Aug 26 17:35:00 In local.conf Aug 26 17:35:03 dont do that Aug 26 17:35:24 this means you want to build everything in zeromq as shared library Aug 26 17:35:47 Yes isn't that the error I'm getting? Aug 26 17:36:06 which may not be right, I expect zeromq build system do that Aug 26 17:36:39 the error is not that Aug 26 17:37:03 ok Aug 26 17:37:52 most probably whats going on, is that zeromq is adding -nostdlib to linker cmdline Aug 26 17:37:59 and adding the libraries on its own Aug 26 17:38:05 which is not a good thing to do Aug 26 17:38:13 so you should check zeromq Aug 26 17:38:16 makefiles Aug 26 17:38:20 and correct it there Aug 26 17:38:37 OK Aug 26 17:39:01 thank you very very much Aug 26 17:39:23 np Aug 26 18:46:07 hello Aug 26 18:47:19 is it possible to have a project in yocto where the makefile builds c code into an exe which is run on the host to build additional source code as part of the larger build and deployment to the target? Aug 26 18:48:43 yes, just compile the build tool with BUILD_CC instead of CC, BUILD_CFLAGS instead of CFLAGS, etc Aug 26 18:48:54 lots of examples of this in existing recipes Aug 26 18:49:25 cool many thanks. kergoth you are a wealth of knowledge. Aug 26 18:50:14 see also meta/conf/bitbake.conf, it's where all those vars are defined Aug 26 18:50:16 np **** ENDING LOGGING AT Sat Aug 27 02:59:58 2016