Branch: Denzil commit 846b7c388738f382e83576e77b705aa547c1dd9b Date: Thu Oct 11 11:43:52 2012 -0700 Using PAM and building core-image-sato-sdk including "sudo" by following the wiki guide: https://wiki.yoctoproject.org/wiki/PAM_Integration will result in a do_install error: " install: cannot stat `/home/cornel/SDD/Yocto/poky/build/tmp/work/i586-poky-linux/sudo-1.8.4p4-r1/sudo.pam': No such file or directory "
(In reply to comment #0) > Branch: Denzil > commit 846b7c388738f382e83576e77b705aa547c1dd9b > Date: Thu Oct 11 11:43:52 2012 -0700 > > Using PAM and building core-image-sato-sdk including "sudo" by following the > wiki guide: https://wiki.yoctoproject.org/wiki/PAM_Integration will result > in a do_install error: " install: cannot stat > `/home/cornel/SDD/Yocto/poky/build/tmp/work/i586-poky-linux/sudo-1.8.4p4-r1/ > sudo.pam': No such file or directory " My build for sudo with pam-enabled is fine. And our QA team had built denzil with pam-enabled this week was succeeded too. Which platform did you build on? And would you like give more information, such as how to reproduce it? Thanks.
I have an Ubuntu 12.04 x86_64. I got repeated fails with the build by including DISTRO_FEATURES_append += " pam" or DISTRO_FEATURES_append = " pam" in local.conf. In all builds I kept the downloads and sstate directory and erased the rest. I will start a fresh build now (clean sstate) and get back to you.
(In reply to comment #2) > I have an Ubuntu 12.04 x86_64. > > I got repeated fails with the build by including DISTRO_FEATURES_append += " > pam" or DISTRO_FEATURES_append = " pam" in local.conf. > > In all builds I kept the downloads and sstate directory and erased the rest. > > I will start a fresh build now (clean sstate) and get back to you. Hi Stoicescu, does it fail in fresh build?
Just did a clean build (only kept the downloads directory because of libowl do_fetch bug) and it finished successfully. Also when using old sstate directory I am getting a dependency error now. It seems to be a sstate contamination issue. Please tell me if you need more info on this, or close, as you seem fit.
(In reply to comment #4) > Just did a clean build (only kept the downloads directory because of libowl > do_fetch bug) and it finished successfully. Also when using old sstate > directory I am getting a dependency error now. It seems to be a sstate > contamination issue. Please tell me if you need more info on this, or close, > as you seem fit. I rebuild sudo with new-created sstate, and build fine. The SSTATE you build on may build without pam. Close it.
Verified.