**** BEGIN LOGGING AT Sun Nov 25 03:00:00 2018 Nov 25 06:11:35 New news from stackoverflow: Add same files to multiple PACKAGES Nov 25 10:12:17 New news from stackoverflow: Trying to create sample linux mage with yocto prject but cause building error Nov 25 14:36:17 Is anybody around? I have two recipes conflicting with each other, and I've no idea why Nov 25 14:47:48 what is the error? Nov 25 14:50:55 Crofton I have a recipe that adds a user (based on the example in the skeleton). It creates /home/USER/ etc. This has been working fine until now. I now have a new recipe that sticks some files into a subdirectory of /home/USER. When I try to build, I get the following: https://paste.ubuntu.com/p/6bfH4vf8qw I tried adding DEPENDS = "adduser" to the latter recipe, but it had no effect Nov 25 14:52:18 Crofton The adduser: http://paste.ubuntu.com/p/kCMRQgJNBb/ the new recipe: http://paste.ubuntu.com/p/NkHJSCSHNx/ Nov 25 14:53:08 what is the rror message? Nov 25 14:53:34 oh wait Nov 25 14:55:29 Crofton https://paste.ubuntu.com/p/6bfH4vf8qw It's about 1000 lines, though Nov 25 14:59:11 I'm not sure, but hopefully some other people look at it Nov 25 15:01:07 Crofton Ok, thanks anyway :) I really thought that the DEPEND would fix it, but apparently not Nov 25 15:11:47 look slike proble is dir creted in two places, but not sure what should happen Nov 25 15:13:21 Crofton That's what I thought, but adduser should create /home/user/ and then the second recipe adds /home/user/code/...files... I don't see the conflict Nov 25 15:15:17 yeah I am confused Nov 25 15:15:29 lists the dir as the conflict Nov 25 15:17:29 Crofton Well, I'm glad i'm not the only one, lol Nov 25 15:56:03 building qemux86-64 but it doesn't have /usr/lib64, I'm trying to replace x86-64 behavior from another target who has /usr/lib64 Nov 25 15:56:39 shouldn't 64-bit build have lib64 header and libraries? Nov 25 16:43:29 New news from stackoverflow: Yocto build fails due to conflict between recipes Nov 25 17:28:50 Crofton If you're still around, it turns out adding DIRFILES = "1" to the second recipe fixed it Nov 25 17:31:01 Although, the chown -R foo ${D}/home/foo/code/ didn't work. It's all owned by root... Nov 25 17:31:29 the chown is going to have issues since it is users ownership from build machine I think Nov 25 17:32:37 Crofton Hmm, it seems to have worked in adduser... /home/foo is indeed owned by foo Nov 25 20:11:16 Anybody around? I have a chown line that doesn't work... In this recipe: http://paste.ubuntu.com/p/NkHJSCSHNx/ The chown doesn't seem to actually do anything Nov 25 21:06:50 la_croix: the issue probably is the "kriminel" user doesn't exist in the environment in which the recipe is being built Nov 25 21:07:02 la_croix: I'd recommend the useradd class for something like this Nov 25 21:52:00 bluelightning Even though the adduser is a requirement of this recipe? I would have thought that that would mean that the user would exist by the time the recipe is created Nov 25 21:52:11 *by the time the recipe builds Nov 25 21:52:41 la_croix: no, it's a lot more complicated than depending on adduser Nov 25 21:53:51 bluelightning Hmm, ok. So I need to populate *all* the files that should live in the home directory within the adduser recipe? Nov 25 21:54:24 la_croix: oh hang on, so the adduser recipe is one you creaed yourself? Nov 25 21:54:54 bluelightning Yes, it's based on the example in meta-skeleton: http://paste.ubuntu.com/p/kCMRQgJNBb/ Nov 25 21:55:55 hmm, actually that should work... Nov 25 22:14:19 bluelightning I'm not doing anything totally stupid, then? Nov 25 22:25:35 la_croix: I can't see anything amiss Nov 25 22:26:33 bluelightning Hmm, ok, I'll keep playing with it **** ENDING LOGGING AT Mon Nov 26 02:59:59 2018