Bug 3504 - meta-baryon:proftpd-1.3.4b can't passed in meta-baryon layer.
Summary: meta-baryon:proftpd-1.3.4b can't passed in meta-baryon layer.
Status: RESOLVED FIXED
Alias: None
Product: Other YP Layers
Classification: Build System, Metadata & Runtime
Component: layers (show other bugs)
Version: 1.3
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.3.1
Assignee: Kevin Strasser
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-11-28 07:53 UTC by scanli
Modified: 2012-12-05 17:55 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description scanli 2012-11-28 07:53:19 UTC 
My development environment：
   Ubuntu 12.04 LTS
   TCMODE = external-sourcery
   EXTERNAL_TOOLCHAIN = /home/ljc/arm-2012.03
   LICENSE_FLAGS_WHITELIST = commercial
   
   Build Configuration:
   BB_VERSION        = "1.16.0"
   TARGET_ARCH       = "arm"
   TARGET_OS         = "linux-gnueabi"
   MACHINE           = "qemuarm"
   DISTRO_VERSION    = "oe-core.0"
   TUNE_FEATURES     = "armv5 dsp thumb arm926ejs"
   TARGET_FPU        = "soft"
   meta              
   meta-hob          = "<unknown>:<unknown>"
   meta-atmel        = "master:08f5b887f93578a1973e351aaef62ef743b2b2d3"
   meta-baryon       = "master:ad1dfa139195f39a72b8e0fb47de5c3339397b8b"
   meta-oe           
   meta-sourcery     = "master:1571c2c566c51799eceea2aabe13d1c3116f36b3"

   NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
   NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
   NOTE: multiple providers are available for ffmpeg (ffmpeg, libav)
   NOTE: consider defining a PREFERRED_PROVIDER entry to match ffmpeg
   NOTE: Resolving any missing task queue dependencies
   NOTE: Preparing runqueue
   NOTE: Executing SetScene Tasks
   NOTE: Executing RunQueue Tasks
   ......
recipe consider proftpd-1.3.4b-r1: task do_install: Failed

log.do_install.31925:
.....
make[1]: Leaving directory `/home/ljc/baryon/build/tmp-eglibc/work/armv5te-oe-linux-gnueabi/proftpd-1.3.4b-r1/proftpd-1.3.4b/include'
rmdir: failed to remove `/home/ljc/baryon/build/tmp-eglibc/work/armv5te-oe-linux-gnueabi/proftpd-1.3.4b-r1/image/usr/lib/proftpd': No such file or directory
ERROR: Function failed: do_install (see /home/ljc/baryon/build/tmp-eglibc/work/armv5te-oe-linux-gnueabi/proftpd-1.3.4b-r1/temp/log.do_install.31925 for further information)
Comment 1 Kevin Strasser 2012-11-30 20:38:00 UTC 
Thanks for the report. This bug appears to have been introduced after danny and is not specific to any architecture. At first glance, it seems to be an issue with libexecdir being changed from "${exec_prefix}/libexec" to "${libdir}/${BPN}". Will report back after bisecting.
Comment 2 Kevin Strasser 2012-12-03 23:32:11 UTC 
My assumption was correct, this error was introduced as of poky commit id 1d18224b24a515a07170ce36dbd725cb203d3300. In changing the value of libexecdir, the proftpd install task was attempting to remove a directory twice.
I have submitted a patch to the mailing list.
Comment 3 Kevin Strasser 2012-12-05 17:55:50 UTC 
Fix merged in meta-baryon commit 9a80f62b1874bbb0819068cf394e9fd920bb84b7