<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>653</bug_id>
          
          <creation_ts>2011-01-14 01:13:38 +0000</creation_ts>
          <short_desc>Build of current master fails with &quot;cannot change ownership&quot; errors.</short_desc>
          <delta_ts>2011-03-21 07:24:41 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Meta-yocto</product>
          <component>meta-yocto</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>1.0 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Wolfgang Denk">wd</reporter>
          <assigned_to name="Paul Eggleton">bluelightning</assigned_to>
          <cc>bluelightning</cc>
    
    <cc>mark.hatle</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>11467</commentid>
    <comment_count>0</comment_count>
    <who name="Wolfgang Denk">wd</who>
    <bug_when>2011-01-14 01:13:38 +0000</bug_when>
    <thetext>Attempts to build the current &quot;master&quot; branch of the git repo (to be specific: commit ID 34bf835) fail with &quot;cannot change ownership&quot; errors.

I&apos;m running

MACHINE=qemuppc bitbake poky-image-sdk

which results in this error:

NOTE: package portmap-6.0-r7: task do_install: Started
ERROR: Function &apos;do_install&apos; failed (see /opt/poky/build-master-34bf835-qemuppc/tmp/work/ppc603e-poky-linux/portmap-6.0-r7/temp/log.do_install.27432 for further information)
ERROR: Logfile of failure stored in: /opt/poky/build-master-34bf835-qemuppc/tmp/work/ppc603e-poky-linux/portmap-6.0-r7/temp/log.do_install.27432
Log data follows:
| ERROR: Function &apos;do_install&apos; failed (see /opt/poky/build-master-34bf835-qemuppc/tmp/work/ppc603e-poky-linux/portmap-6.0-r7/temp/log.do_install.27432 for further information)
| NOTE: make -e MAKEFLAGS= install DESTDIR=/opt/poky/build-master-34bf835-qemuppc/tmp/work/ppc603e-poky-linux/portmap-6.0-r7/image
| install -o root -g root -m 0755 portmap /opt/poky/build-master-34bf835-qemuppc/tmp/work/ppc603e-poky-linux/portmap-6.0-r7/image/sbin
| install: cannot change ownership of `/opt/poky/build-master-34bf835-qemuppc/tmp/work/ppc603e-poky-linux/portmap-6.0-r7/image/sbin/portmap&apos;: Operation not permitted
| make: *** [install] Error 1
| FATAL: oe_runmake failed
| Function &apos;do_install&apos; failed (see /opt/poky/build-master-34bf835-qemuppc/tmp/work/ppc603e-poky-linux/portmap-6.0-r7/temp/log.do_install.27432 for further information)
NOTE: package portmap-6.0-r7: task do_install: Failed
ERROR: Task 939 (/home/wd/git/poky/work/meta/recipes-connectivity/portmap/portmap_6.0.bb, do_install) failed with exit code &apos;1&apos;

This error has been reported before on the ML, see
http://article.gmane.org/gmane.linux.embedded.poky/1007
so it seems this is a general problem and not specific to my build environment.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11471</commentid>
    <comment_count>1</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2011-01-14 02:36:53 +0000</bug_when>
    <thetext>Which version of Poky are you using? The 0.9 release or master? This happens when pseudo isn&apos;t loaded for some reason or isn&apos;t working properly (pseudo is a replacement of fakeroot). Was pseudo-native built?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11472</commentid>
    <comment_count>2</comment_count>
    <who name="Wolfgang Denk">wd</who>
    <bug_when>2011-01-14 02:55:33 +0000</bug_when>
    <thetext>I wrote: current &quot;master&quot; branch of the git repo (to be specific:
commit ID 34bf835).

From what I see in the log file, pseudo-native was built fine:

-&gt; grep pseudo-native BITBAKE-poky-image-sdk.LOG 
NOTE: selecting pseudo-native to satisfy virtual/fakeroot-native due to PREFERRED_PROVIDERS
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_setscene: Started
NOTE: Removing shared state for package pseudo-native
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_setscene: Succeeded
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_fetch: Started
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_fetch: Succeeded
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_unpack: Started
NOTE: Unpacking /home/wd/git/poky/downloads/git_github.com.wrpseudo.pseudo.git_c9792c7acdb1cac90549ff08db12a8bf0c53cdcf.tar.gz to /opt/poky/build-master-34bf835-qemuppc/tmp/work/x86_64-linux/pseudo-nativ-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16/
NOTE: Unpacking /home/wd/git/poky/work/meta/recipes-devtools/pseudo/pseudo/static_sqlite.patch to /opt/poky/build-master-34bf835-qemuppc/tmp/work/x86_64-linux/pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16/
NOTE: Unpacking /home/wd/git/poky/work/meta/recipes-devtools/pseudo/pseudo/895fa7e359e8026a608fba052c2994e42901e45f.patch to /opt/poky/build-master-34bf835-qemuppc/tmp/work/x86_64-linux/pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16/
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_unpack: Succeeded
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_patch: Started
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_patch: Succeeded
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_configure: Started
NOTE: pseudo-native: md5 checksum matched for file://COPYING;md5=243b725d71bb5df4a1e5920b344b86ad
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_configure: Succeeded
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_compile: Started
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_compile: Succeeded
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_install: Started
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_install: Succeeded
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_populate_sysroot: Started
NOTE: package pseudo-native-0.0+git0+c9792c7acdb1cac90549ff08db12a8bf0c53cdcf-r16: task do_populate_sysroot: Succeeded</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11473</commentid>
    <comment_count>3</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2011-01-14 04:26:24 +0000</bug_when>
    <thetext>(In reply to comment #2)
&gt; I wrote: current &quot;master&quot; branch of the git repo (to be specific:
&gt; commit ID 34bf835).

Sorry, somehow I didn&apos;t manage to spot that in the subject line!

I agree it looks like pseudo was built ok.

What does &quot;which bitbake&quot; show? I&apos;m wondering if your PATH somehow got messed up - it should be pointing at the scripts/bitbake script, not bitbake/bin. That script is responsible for loading the pseudo wrapper.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11487</commentid>
    <comment_count>4</comment_count>
    <who name="Wolfgang Denk">wd</who>
    <bug_when>2011-01-15 06:51:03 +0000</bug_when>
    <thetext>Good point.

I had manually set

PATH=/home/wd/git/poky/work/bitbake/bin:/home/wd/git/poky/work/scripts:...

as I did in previous versions of Poky, to make sure it does not contain &apos;.&apos; which usually is included in my PATH.  After swapping the order of .../bitbake/bin and .../scripts the build completes fine.

Hm...t his is the second time I run into such issues because of incorrect PATH settings. I can understand that having &apos;.&apos; in the PATH my cause trouble, but here a setting that used to work fine before suddenly breaks the build in a pretty obscure (well, to me) way.

Is it really necessary to provide the same files in different versions in several directories, so search order becomes critical? Would it not be more robust to rename the &quot;wrong&quot; tool so it cannot be found by accident?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11488</commentid>
    <comment_count>5</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2011-01-16 08:50:42 +0000</bug_when>
    <thetext>This issue is resolved as not a bug.

The normal operations of poky is to use the poky-init-build-env, which is documented and correctly sets up the path. Your concern about having 2 versions of the bitbake command is noted and I will have to leave it others to comment on the history of that particular item.  As Richard noted the scripts/bitbake is a wrapper over bitbake/bin/bitbake in order to do the pseudo setup.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>11489</commentid>
    <comment_count>6</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2011-01-16 11:06:56 +0000</bug_when>
    <thetext>I&apos;m going to disagree slightly with Saul :). I think if for whatever reason pseudo isn&apos;t loaded during a do_install task, we should error with more informative error for the user and also, if bitbake is being run outside the scripts/bitbake script, sanity.bbclass should inform the user about it.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12366</commentid>
    <comment_count>7</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2011-03-08 13:31:20 +0000</bug_when>
    <thetext>Decision is to set an environment variable from within the bitbake wrapper.  The wrapper will set the variable and indicate if it&apos;s in stage1 or stage2 of the build.

insane.bbclass will look for the existence of the variable, if it doesn&apos;t exist a _warning_ will be generated that the person is not using the bitbake wrapper.

Further the insane.bbclass will check the value, and if in stage2 it will check that pseudo is available and working properly.  It&apos;s an error if it doesn&apos;t function.

Q: If we&apos;re NOT using the wrapper -- what do we do?  Suggestion is no wrapper, we check if pseudo is working and WARN then that target package compilation won&apos;t work.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>12868</commentid>
    <comment_count>8</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2011-03-21 07:24:41 +0000</bug_when>
    <thetext>Issues were addressed in commit http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=3046a96bf0bdb1ca32db96a11a372a0e09f91856</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>