**** BEGIN LOGGING AT Fri Apr 14 03:00:01 2017 Apr 14 08:40:55 hello guys, I would like yocto build the latest revision of the package each time when I am trying to build an image. I have SRCREV = "${AUTOREV}" PV = "+git${SRCPV}" and SRCREV_FORMAT = "${PN}" in the recipe. But it doesn't work unfortunately. What am I doing wrong? Apr 14 09:24:59 zloy: SRC_URI has a git:// url in it? Apr 14 09:27:17 RP: yup Apr 14 09:28:21 RP: something like that: git://git@bitbucket.org/foo/bar.git;protocol=ssh;branch=${BRANCH} Apr 14 09:42:54 zloy: why are you setting SRCREV_FORMAT? you shouldn't need that Apr 14 09:43:00 zloy: try not setting it Apr 14 09:44:40 RP: ok. But for some packages I have several repositories Apr 14 09:46:48 here is the error: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: The SRCREV_FORMAT variable must be set when multiple SCMs are used. Apr 14 09:47:09 zloy: ok, you didn't mention you have multiple repos and that is quite an important detail Apr 14 09:47:22 zloy: that setting of SRCREV_FORMAT is incorrect Apr 14 09:47:49 RP: what is correct one? Apr 14 09:49:02 zloy: in SRC_URI, give each repo a name with the name parameter, e.g. ;name=first and ;name=second in the urls Apr 14 09:49:12 zloy: then et SRCREV_FORMAT = "first_second" Apr 14 09:49:17 set Apr 14 09:49:26 the names need to match Apr 14 09:49:59 zloy: see linux-yocto as an example in OE-Core which does this (machine and meta are the names it uses) Apr 14 09:50:02 RP: thank you. I will try Apr 14 09:52:41 hm, I see the following: SRC_URI = "git://git.yoctoproject.org/linux-yocto-3.19.git;bareclone=1;branch=${KBRANCH},${KMETA};name=machine,meta" Apr 14 09:53:42 zloy: that must be an older repo as I don't see anything like that Apr 14 09:53:54 linux-yocto_4.10.bb:SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.10.git;name=machine;branch=${KBRANCH}; \ Apr 14 09:53:55 linux-yocto_4.10.bb: git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.10;destsuffix=${KMETA}" Apr 14 10:03:03 RP: thank you again :) Apr 14 12:56:23 I'm trying to compile a qt application with the sdk i genarated but it keeps complaining about: armv7ahf-neon-linux-gnueabi/usr/include/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory Apr 14 12:57:09 but my CFLAG contains: -mfloat-abi=hard Apr 14 12:58:06 also my tune features on building the sdk: TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa8" Apr 14 14:29:15 Hi all, for some big srouces, I get Fetchure Failure with connection timed out. " fatal: early EOF ". Do you know how to avoid it ? Apr 14 14:30:03 Have tried to git clone myself the file, and it works. So it's not a problem that came from the server. Apr 14 15:52:21 hello there Apr 14 15:52:23 any good way to do something like this? Apr 14 15:52:25 SYSTEMD_SERVICE_${PN} = "${PN}.service" Apr 14 15:52:35 but of course I need the value for PN :) Apr 14 15:52:51 and I don't want to use Python if possible Apr 14 15:53:25 not sure why you'd need the value for PN Apr 14 15:53:33 variable references are automatically expanded for you Apr 14 15:58:17 so, if the service is called as the recipe, the above should work? Apr 14 15:59:47 don't see any reason why not Apr 14 16:04:45 not sure, I have a new project with meta-raspberrypi instead of meta-freescale, different hw, and this bbclass I used to include is not working anymore Apr 14 16:49:08 Hi, I’m on daisy and meta-oe didn’t have libss2 so I added the recipe for it. I can see the libssh2.so files in the tmp folder and even in the image but I cannot see it in the sysroot directory. My qt app is looking for it there. How can i install it to the sysroots folder? Apr 14 16:50:15 will it be do_install_append() { install -m ${D}${libdir}/libssh2.so sysroots?/arch?/usr/lib Apr 14 16:50:42 is that the right way to do it and if yes how do i get to the sysroots dir Apr 14 16:50:44 thanks Apr 14 16:51:50 no Apr 14 16:52:07 do_populate_sysroot will automatically grab files from ${D} as long as they're in the correct paths Apr 14 16:52:13 do_install should never, ever touch a sysroot directly Apr 14 16:52:43 doe syour app depend on libssh2? if it doesn't, it won't be in the sysroot, at least with current versions Apr 14 16:53:19 it does, we haven’t moved to a new yocto yet so we didn’t have it by default in meta-oe so had to add it in Apr 14 16:53:59 well it’s really qt creator that’s being a pain i guess. Becaues the image has it. Apr 14 16:54:26 let me try do_populate_sysroot. Should that be defined empty? Apr 14 16:54:47 no, you should not touch or define that at all Apr 14 16:54:57 I can’t even find the function http://www.yoctoproject.org/docs/1.6.1/dev-manual/dev-manual.html here Apr 14 16:55:05 it already does what it needs to do. if you're installing a file that doesnt' end up in the sysroot, then you're installing it to a non-standard location Apr 14 16:55:45 i just got the bb file from a newer version on meta-oe. That’s all i did so I assumed it should have just worked Apr 14 16:56:09 combining files between different versions is in no way guaranteed to work. it might, it might not Apr 14 16:56:26 but again, any libs instaled to ${D}${libdir} will automatically end up in the sysroot in the correct location Apr 14 16:57:02 i can see it in ${D}${libdir} but not in sysroot Apr 14 16:57:54 if you really want to know what do_populate_sysroot does, read staging.bbclass Apr 14 16:59:01 ok, will do that Apr 14 17:26:15 ugh ok I asked the completely wrong question. It’s in the sysroot directory but not in the toolchain directory. Not sure where my head was. Apr 14 17:26:37 what handles adding something new to the toolchain directory Apr 14 17:27:40 * armpit no swat rotation change ?? Apr 14 17:41:47 HavoK_: TOOLCHAIN_TARGET_TASK is a space-separated list of packages to install in the target sysroot when building an sdk. see the yocto docs for details Apr 14 17:43:07 thanks, let me look into it **** ENDING LOGGING AT Sat Apr 15 03:00:00 2017