Bug 1491 - Some issues while using oe-core on Debian machine
Summary: Some issues while using oe-core on Debian machine
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: unspecified
Hardware: x86 x86_64
: Medium minor
Target Milestone: 1.2
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard: (1.2)
Depends on:
Blocks:
 
Reported: 2011-09-16 15:21 UTC by Mikhail Boiko
Modified: 2012-04-04 23:29 UTC (History)
7 users (show)

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

Attachments
libgcc log (5.12 KB, text/x-log)
2011-09-20 09:33 UTC, Mikhail Boiko 		no flags Details
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 Mikhail Boiko 2011-09-16 15:21:39 UTC 
Hi

Have some issues with oe-core for qemuarm target. When running "bitbake core-image-minimal" I receive lot of "Operation not permitted" errors for libgcc's do_install. Please see full log attached. It also happens for "base-passwd", "db" and "gcc-configure-runtime" packages. Adding fakeroot before "chown ...." in recipe solves the problem, but it is not the way it supposed to be.

I'm using Debian GNU/Linux 6.0.2 (squeeze) for x86_64
oe-core repo: git://git.openembedded.org/openembedded-core
oe-core rev: 20529035a4c0befb3c6bdbcb289a2de930fb143d
Please inform me if any addition information is needed.

Same steps reproduced on Ubuntu causes no troubles at all.

Thanks
Comment 1 Saul Wold 2011-09-19 08:16:14 UTC 
Please add the attachement, there is no log.

Thanks
Comment 2 Mikhail Boiko 2011-09-20 09:33:28 UTC 
Created attachment 244 [details]
libgcc log

install log for libgcc in oe-core
Comment 3 Mikhail Boiko 2011-09-20 09:36:39 UTC 
Sorry that forgot to add it at once.

Thanks
Comment 4 Saul Wold 2011-09-21 22:09:43 UTC 
By any chance do you have selinux or apparmour enabled on this system?

This looks like it might be related to that. All the install task run using pseudo already so they are "fakerooted' already.
Comment 5 Mark Hatle 2011-09-22 08:00:20 UTC 
Also verify that you are running bitbake via the scripts/bitbake shell wrapper and not directly from the bitbake directory.

If you are not running the wrapper, then you will not have pseudo preloaded into memory.  pseudo is what does the "root" emulation for many of these items.
Comment 6 Mikhail Boiko 2011-09-22 11:13:25 UTC 
(In reply to comment #4)
> By any chance do you have selinux or apparmour enabled on this system?
> 
I'm not 100% sure, but it seems that there is no selinux or apparmout enabled. 
 
> This looks like it might be related to that. All the install task run using
> pseudo already so they are "fakerooted' already.
Will try to investigate this a little more careful, thank you for pointing.

Thanks you
Comment 7 Mikhail Boiko 2011-09-22 11:17:17 UTC 
(In reply to comment #5)
> Also verify that you are running bitbake via the scripts/bitbake shell wrapper
> and not directly from the bitbake directory.
> 
> If you are not running the wrapper, then you will not have pseudo preloaded
> into memory.  pseudo is what does the "root" emulation for many of these items.

I use wrappers (oe-init-build-env) and can see with "ps -e | grep pseuso" that 2 pseudo processes starts. 


Thanks
Comment 8 Saul Wold 2012-04-04 23:29:33 UTC 
I just attempted a build with Debian 6.0.2 (no updates or patches) on a vmware image. 

I was able to build libgcc correctly without any issues, I also built and booted core-image-minimal.

If this is still an issue for you, we meed to dig deeper about your system and what you have installed.