**** BEGIN LOGGING AT Tue Dec 12 03:00:01 2017
Dec 12 09:29:59 <kosta> Guys, I build "safplus" and do_package fails, because some files are built for host (not target). Log: https://pastebin.com/ZNzCqNKA. How to remove files before packaging?
Dec 12 09:30:43 <kosta> The error is: "ERROR: QA Issue: safplus: Files/directories were installed but not shipped in any package"
Dec 12 09:31:30 <nayfe> Hi kosta, can you share your recipe with us ?
Dec 12 09:32:05 <LetoThe2nd> kosta: the error message  actually means something completely different than you told us. thats why the exact error message is important
Dec 12 09:32:28 <LetoThe2nd> kosta: the files seem to be built correctly for the target, its just that they are not added to the package step
Dec 12 09:33:18 <kosta> safplus recipe: https://pastebin.com/ZmFSNKMX
Dec 12 09:33:35 <LetoThe2nd> kosta: here you go: http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-FILES
Dec 12 09:34:15 <LetoThe2nd> probably you just need to expand FILES_${ON} a little more
Dec 12 09:34:38 <kosta> LetoThe2nd: Thanks. I think that the "built-for-host" should not be added to the package.
Dec 12 09:35:01 <kosta> LetoThe2nd: Is there a way to tell package what to take in and what not?
Dec 12 09:35:17 <LetoThe2nd> kosta: thats exactly what FILES does.
Dec 12 09:35:18 <nayfe> <LetoThe2nd> there are a lot of issues in recipe, so it's not just a problem of shipping
Dec 12 09:35:38 <LetoThe2nd> nayfe: no surprise, but thats what he/she asked :)
Dec 12 09:36:02 <kosta> Guys, I cloned an ancient safplus recipe from https://github.com/joaohf/meta-openclovis/blob/master/recipes-extended/safplus/safplus_6.1.bb
Dec 12 09:36:26 <kosta> ... and I'm trying to fix it to use for Yocto 2.4 (rocko branch).
Dec 12 09:37:29 <kosta> LetoThe2nd: Did you mean "FILES_${PN}" or "FILES_${ON}"?
Dec 12 09:38:11 <LetoThe2nd> kosta: PN of course. if you look at your keyboard, the letter 'P' is directly next to the letter 'O', which hints that my finger just slipped.
Dec 12 09:38:42 <kosta> LetoThe2nd: Got it. I'll try to dance with "FILES_${PN}". Thanks guys!
Dec 12 09:40:10 <yocti> New news from stackoverflow: Yocto change psplash image without rebuild the system <https://stackoverflow.com/questions/47769154/yocto-change-psplash-image-without-rebuild-the-system>
Dec 12 09:52:32 <nayfe> kosta: normally, result files of do_compile() are put in "build" folder of recipe, then when do_install()  is called, it put files into "deploy" folder, then you need to create your package by selecting files you want in, but your recipe put files into strange folders, it does not use STAGING_DIR_*, to me, you better make a new one
Dec 12 09:54:38 <kosta> nayfe: Can you please recommend a recipe to be used as a basis for this?
Dec 12 09:55:01 <kosta> nayfe: Or some good reference that uses STAGING_DIR_*?
Dec 12 09:55:56 <nayfe> kosta: i suggest you to look at https://www.youtube.com/watch?v=CiD7rB35CRE then read http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html
Dec 12 09:57:11 <kosta> nayfe: Thanks. Watching youtube... ))
Dec 12 09:58:45 <kosta> nayfe: BTW, the build system of this "safplus" is really strange and complicated. So, I'm not going to change it in any case...
Dec 12 09:59:59 <nayfe> kosta: indeed, but sometimes if buildsystem is not compatible with yocto, you don't have choice
Dec 12 10:02:16 <kosta> nayfe: By "don't have choice" you mean "to convert safplus build system to yocto style" or "to work-around safplus build system incompatibility inside the recipe"?
Dec 12 10:04:44 <nayfe> kosta: you maybe need to patch sources
Dec 12 10:35:44 <lukma> I do have a problem with having installed libgcc.a on my system -> it is huge (25 MiB)
Dec 12 10:35:53 <lukma> It is installed at: /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a
Dec 12 10:36:08 <lukma> I do not have gcc installed on my target system
Dec 12 10:36:35 <lukma> is seems like it is installed by libgcc-initial
Dec 12 10:36:39 <lukma> or libgcc
Dec 12 10:36:54 <lukma> $PREFERRED_VERSION_libgcc-initial
Dec 12 10:37:08 <lukma> set? poky/meta/conf/distro/include/tcmode-default.inc:43
Dec 12 10:37:29 <lukma> Is there a way to ask OE to not install it? (And any extra libraries)
Dec 12 10:37:47 <LetoThe2nd> lukma: well try to find out what actually pulls it in. something seems to hava dependency on it.
Dec 12 10:38:45 <lukma> LetoThe2nd: bitbake -g libgcc -u depexp
Dec 12 10:38:53 <lukma> shows that I cannot connect to the server
Dec 12 10:41:24 <nayfe> bitbake -u taskexp -g <bitbake_target> ?
Dec 12 10:45:16 <lukma> nayfe: This works
Dec 12 10:51:41 <nayfe> I'm trying to use BB_NO_NETWORK, and swupdate fails with "bb.data_smart.ExpansionError: Failure expanding variable do_configure", i suspect problem comes from  https://github.com/sbabic/meta-swupdate/blob/master/recipes-support/swupdate/swupdate.inc#L41 (defconfig = bb.fetch2.localpath('file://defconfig', d)), any idea ?
Dec 12 10:53:50 <abelloni> RP: I can't fill a bug in bugzilla right now but http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#migration-1.4-proxies-and-fetching-source is referring to meta-yocto that doesn't exist anymore
Dec 12 11:07:57 <lukma> nayfe: Regarding SWUpdate
Dec 12 11:08:06 <lukma> shouldn't this be fetched: https://github.com/sbabic/meta-swupdate/blob/master/recipes-support/swupdate/swupdate/defconfig
Dec 12 11:10:28 <yocti> New news from stackoverflow: Cross compiling scipy for open-embedded <https://stackoverflow.com/questions/47770891/cross-compiling-scipy-for-open-embedded>
Dec 12 11:30:03 <rfried> Hello. I was wondering if anyone knows of a working setup of Icecream distributed build with Yocto.
Dec 12 11:30:03 <rfried> I tried to follow the wiki here: https://www.openembedded.org/wiki/Using_IceCC
Dec 12 11:30:03 <rfried> with no much luck.
Dec 12 11:40:09 <LetoThe2nd> rfried: well history of that article show the last modification in 2014
Dec 12 11:40:13 <LetoThe2nd> erm, 2013
Dec 12 11:40:42 <rfried> LetoThe2nd: Yes. that's along time ago. that's why I'm asking :)
Dec 12 11:41:18 <LetoThe2nd> it is very much possible somethign has broken or changed in the meantime. plus, about everybody i know just uses a bigger build system instead of going through the hassles of a distributed setup
Dec 12 11:43:14 <rfried> It's not that of a hassle according to the wiki. just the minor detail that it doesn't work...
Dec 12 11:44:25 <LetoThe2nd> all depends on the POV
Dec 12 11:45:50 <rfried> that's always true
Dec 12 11:56:18 <RP> abelloni: thanks, I filed https://bugzilla.yoctoproject.org/show_bug.cgi?id=12418
Dec 12 11:56:19 <yocti> Bug 12418: normal, Undecided, ---, srifenbark, NEW , Stale reference to meta-yocto
Dec 12 12:51:27 <xtron> hi all, building selinux got error "swig command not found" from audit recipe, so I put <DEPENDS += "swig-native"> then got same error from libsemanage and fix it in <selinux_common.inc>, so how can I find the origin of dependency
Dec 12 12:51:31 <otavio> RP: it seems there are more meta-yocto entries which need review on the manual
Dec 12 12:53:19 <otavio> rfried: I'd better invest time in getting a shared PRServer and a shared sstate and use multiple machines building than using distributed build
Dec 12 12:53:55 <otavio> rfried: we've been using AWS for some builds at OSS and it proves to be very appealing
Dec 12 12:54:28 <RP> otavio: entirely possible :(
Dec 12 13:00:54 <xtron> ping question ^
Dec 12 13:35:33 <Tamis> If you need to install in an image a pre-build file of a different arch of the machine. The only possible way to do this, is it to inherit the allrach bbclass and INSANE_SKIP the arc at the recipe?
Dec 12 13:36:13 <Tamis> Is there an other method?
Dec 12 13:59:18 <nayfe> tamis: put file in archive ?
Dec 12 14:46:22 <Tamis> nayfe: It will work but the file needs to be as it is. Right now I have done it like I described above.
Dec 12 14:50:26 <kanavin> Tamis: how about 'MACHINE=<other_machine> bitbake <different_arch_recipe>', then explicitly install the resulting package to the image?
Dec 12 14:58:57 <nayfe> lukma>  problem for swupdate_git.bb is no SRCREV is set, and it seems to not work with BB_NO_NETWORK
Dec 12 15:04:48 <Tamis> kanavin: But you need to have the conf for that <other_machine> right? Which for the time being I haven't setup it.
Dec 12 15:06:18 <kanavin> Tamis: yeah
Dec 12 15:10:41 <Tamis> kanavin: I will do that and build also those prebuild files, but at a second step. Right now I take them as it is because they are not the same arch with the board. Only a certain HW peripheral requires them.
Dec 12 15:11:48 <Tamis> kanavin: Using also the PACHAGE_ARCH = <other_arch> wouldn't have the same effect if I setup the other machine conf?
Dec 12 15:12:19 <kanavin> Tamis: I don't know :)
Dec 12 15:13:07 <Tamis> kanavin: Thanks for the help. You gave me some pointers
Dec 12 15:13:58 <kanavin> Tamis: fwiw, linux-firmware recipe does the same thing as you do, so maybe that can be considered 'official' :)
Dec 12 18:41:54 <yocti> New news from stackoverflow: Query on directory creation during build in yocto <https://stackoverflow.com/questions/47779322/query-on-directory-creation-during-build-in-yocto>
Dec 12 18:49:10 <batman_> Hello, Does yocto build rely on libraries in native sysroots or does it use them from the host ?
Dec 12 18:50:19 <Crofton|work> Sign up if you will be at FOSDEM, https://www.openembedded.org/wiki/FOSDEM_2018
Dec 12 18:51:25 <fray> batman_ both
Dec 12 18:51:46 <fray> libraries for native items (things that will run on the host), if may come from either.. some things that are built, some from the host
Dec 12 18:55:36 <batman_> fray: Is there a way to know from where yocto is trying to get a library? I am looking at a build failure involving libpcre and I am not sure where the problem is
Dec 12 18:57:17 <fray> if it says the librayr isn't present.. then it's not in either location.. if it says it's present and ther eis a missing symbol -- it should show you what it tried to load
Dec 12 19:50:01 <peacememories> hmm, when building samba i get a QA Issue warning that "sysv" is an invalid PACKAGECONFIG
Dec 12 20:17:04 <khem> peacememories: are you using trunk ?
Dec 12 20:18:40 <peacememories> trunk?
Dec 12 20:18:57 <rburton> khem showing his svn roots
Dec 12 20:18:59 <rburton> master :)
Dec 12 20:20:29 <khem> heh. master is just a misnomer in git world,
Dec 12 20:21:58 <khem> now to the question above, I do not see sysv as a packageconfig in samba recipe neither defined nor used
Dec 12 20:22:32 <rburton> which suggests that its something peacememories has done themselves
Dec 12 20:24:30 <khem> hmmm it seems this commit is missing http://git.openembedded.org/meta-openembedded/commit/?id=505b35c89b988a6504d80b28eb68786d14a4549b
Dec 12 20:24:40 <peacememories> it is... or was defined. i'm sadly using a slightly older commit in morty
Dec 12 20:25:04 <peacememories> which has the following line when defining packageconfig `${@bb.utils.contains('DISTRO_FEATURES', 'sysvinit', '${SYSVINITTYPE}', '', d)`
Dec 12 20:25:08 <khem> ok then its understood
Dec 12 20:25:14 <peacememories> (sysvinittype is set to sysv)
Dec 12 20:25:15 <khem> you might want relvant backports
Dec 12 20:25:47 <peacememories> probably, but every time i try to move to a newer commit something breaks^^
Dec 12 20:29:12 <khem> hmmm
Dec 12 20:29:49 <khem> if you are on morty then its better to stay with morty unless you intend to move to newer release, if you do then move all layers together
Dec 12 20:30:02 <khem> otherwise you can do selective backports
Dec 12 20:49:20 <peacememories> trying selective backports, but now "tdb" is not found^^
Dec 12 20:49:33 <peacememories> (by sambas `do_configure`)
Dec 12 20:56:22 <peacememories> backports tend to be kind of fractal^^
Dec 12 21:04:11 <majuk> Hey all. Trying to roll qt5base in Krogoth. It looks like OE_QMAKE_PATH_QT_ARCHDATA has an extra '/' in the middle of it and it's causing do_install to throw fits. Error: https://pastebin.com/9DCs66K6 [line 6, image//usr/lib] Relevant section of qtbase_git.bb: https://pastebin.com/8Tdz1Hxc
Dec 12 21:04:42 <majuk> I commented out line 3 to avoid the first instance of this problem, but it happens again at line 22 [which is the source of the current error]
Dec 12 21:07:18 <majuk> Can anyone recommend a fix or work around for this issue?
Dec 12 21:16:53 <majuk> Alright then, replace the variable with the path it is.
Dec 12 21:29:57 <peacememories> hmm, it seems samba-python installs /usr/lib/python2.7/site-packages/ldb.so
Dec 12 21:30:02 <peacememories> how can i stop it from doing that?^^
Dec 12 21:56:45 <peacememories> i've removed ldb.so from sambas FILES_${PN}-python, oe-pkgdata-util does not list it as provider of the file anymore, but i am still getting the same error
Dec 12 21:56:47 <peacememories> whyyyy
Dec 12 22:37:42 <lukma> If I may ask:
Dec 12 22:37:56 <lukma> Has something changed since: https://lists.yoctoproject.org/pipermail/yocto/2015-January/022897.html
Dec 12 22:38:17 <lukma> is it possible with wic to seamlessly exclude /home from rootfs
Dec 13 00:14:16 <majuk> So I wiped and re-cloned all the sources for my Krogoth build and the qtbase issue magically disappeared.
Dec 13 00:14:39 <majuk> That is... well, something. I'm kinda ok with it. Also kinda scared.
**** ENDING LOGGING AT Wed Dec 13 03:00:01 2017