| Summary: | Build of current master fails with "cannot change ownership" errors. | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Wolfgang Denk <wd> |
| Component: | meta-yocto | Assignee: | Paul Eggleton <bluelightning> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | bluelightning, mark.hatle, poky.bs.watcher, poky.watcher, richard.purdie, sgw |
| Version: | unspecified | ||
| Target Milestone: | 1.0 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Wolfgang Denk
2011-01-14 01:13:38 UTC
Which version of Poky are you using? The 0.9 release or master? This happens when pseudo isn't loaded for some reason or isn't working properly (pseudo is a replacement of fakeroot). Was pseudo-native built? I wrote: current "master" branch of the git repo (to be specific: commit ID 34bf835). From what I see in the log file, pseudo-native was built fine: -> 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 (In reply to comment #2) > I wrote: current "master" branch of the git repo (to be specific: > commit ID 34bf835). Sorry, somehow I didn't manage to spot that in the subject line! I agree it looks like pseudo was built ok. What does "which bitbake" show? I'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. 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 '.' 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 '.' 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 "wrong" tool so it cannot be found by accident? 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. I'm going to disagree slightly with Saul :). I think if for whatever reason pseudo isn'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. Decision is to set an environment variable from within the bitbake wrapper. The wrapper will set the variable and indicate if it's in stage1 or stage2 of the build. insane.bbclass will look for the existence of the variable, if it doesn'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's an error if it doesn't function. Q: If we'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't work. Issues were addressed in commit http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=3046a96bf0bdb1ca32db96a11a372a0e09f91856 |