[cros-dev] ACCESS DENIED? Problems building chromium from local source

[Sean Parent]

emerging chromeos-chrome in the chroot environment I'm getting:

________ running '/usr/bin/python2.6 src/build/gyp_chromium' in '/home/seanparent/chrome_root'

Updating projects from gyp files...

ACCESS DENIED  open_wr:      /home/seanparent/chrome_root/src/third_party/WebKit/WebCore/WebCore.gyp/idls_list_temp_file.tmp.gyp.6_A_Mu.tmp

ISE:write_logfile unable to append logfile

ISE open_wr(src/third_party/WebKit/WebCore/WebCore.gyp/idls_list_temp_file.tmp.gyp.6_A_Mu.tmp): No such file or directory

        abs_path: /home/seanparent/chrome_root/src/third_party/WebKit/WebCore/WebCore.gyp/idls_list_temp_file.tmp.gyp.6_A_Mu.tmp

        res_path: /home/seanparent/chrome_root/src/third_party/WebKit/WebCore/WebCore.gyp/idls_list_temp_file.tmp.gyp.6_A_Mu.tmp

I tried nuking the WebKit directory and resyncing  but same issue. Anyone have a clue about what is broken?

Thanks,

Sean

--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[ko...@codeaurora.org]

> emerging chromeos-chrome in the chroot environment I'm getting:
>
> ________ running '/usr/bin/python2.6 src/build/gyp_chromium' in
> '/home/seanparent/chrome_root'
> Updating projects from gyp files...
> ACCESS DENIED open_wr:
>

I/we actually have the same issue from day 1 when trying to mount
chrome_root. Unfortunately we are seeing it on most of our machines.
I haven't spent time on going to the bottom of it.

Currently, I have no other choice but to workaround it on my machine.
Modifying enter_chroot.sh to mount CHROME_ROOT in a different place than
/home/$USER/chrome_root (e.g., mount it in /tmp/chrome_root).
Same deal for chromeos-chrome ebuild.

HTH,
Kobi

[Sean Parent]

Interesting - how do you tell emerge where the new root is? (I'm trying a build now with a symlink in /home/$USER to the mount in /tmp)

Sean

[ko...@codeaurora.org]

> Interesting - how do you tell emerge where the new root is? (I'm trying a
> build now with a symlink in /home/$USER to the mount in /tmp)

Currently, until we find the root cause, I'm modifying my chromeos-chrome
ebuild.
AFAIR symlink didn't work for me. I needed to put the src in chroot/tmp
and change enter_chroot script + chromeos-chrome ebuild.

and e.g. for mounting.
./enter_chroot --chrome_root=../../chroot/tmp/chromium

We really need to get to the bottom of that.

Thx,
Kobi

[Trevor Bourget]

you can edit the CHROME_ROOT environment variable after you enter the
chroot, for example i always set CHROME_ORIGIN=LOCAL_SOURCE and
CHROME_ROOT=/tmp/chrome_root in the .bash_login of the chroot's home dir.
also, you don't need to use the --chrome_root flag. you can do the mount
explicitly before enter the chroot, and the cleanup will still
automatically catch it on exit.
-- trevor

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

[Bill Richardson]

Our /home/$USER directories are mounted on NFS. Building on an NFS mountpoint is very inefficient. Plus, if the server has the root_squash attribute enabled (ours does), your local root account won't be able to access it. We strongly recommend building on a local disk instead.

[ko...@codeaurora.org]

> Our /home/$USER directories are mounted on NFS. Building on an NFS
> mountpoint is very inefficient. Plus, if the server has the root_squash
> attribute enabled (ours does), your local root account won't be able to
> access it. We strongly recommend building on a local disk instead.
>

Even on a local disk, I'm getting that access denied unless I tweak it.

[Trevor Bourget]

the problem is not the location of the build, it is the location of the
mount point within the chroot.
it is strange that the behavior should be different but it is.
chromiumos.git/chroot/home/$USER/chrome_root has the permissions problem
but not chroot/tmp/chrome_root.
also, it doesn't happen with all machines.

-- trevor

[Sean Parent]

And, apparently, it can just suddenly appear. In my case I was building fine, did a sync, and suddenly I'm getting permission errors. I tried an rm/sync on the offending directory, rebooting, and deleting chroot/home/$USER/chrome_root but no luck. Moving the mount point to chroot/tmp/chrome_root worked but also cost a full rebuild - makes me wonder if it is the move that fixes things and the location is a red-herring. I'm going to try moving it back and see what happens. I have several changes on my branch so I don't want to nuke the whole chrome source directory and start fresh.

Sean

[Sean Parent]

On Tue, May 18, 2010 at 9:29 AM, Sean Parent <seanp...@chromium.org> wrote:

And, apparently, it can just suddenly appear. In my case I was building fine, did a sync, and suddenly I'm getting permission errors. I tried an rm/sync on the offending directory, rebooting, and deleting chroot/home/$USER/chrome_root but no luck. Moving the mount point to chroot/tmp/chrome_root worked but also cost a full rebuild - makes me wonder if it is the move that fixes things and the location is a red-herring. I'm going to try moving it back and see what happens. I have several changes on my branch so I don't want to nuke the whole chrome source directory and start fresh.

Moving the mount location back doesn't trigger a rebuild and the ACCESS DENIED problem still exists. Is there someway to force a clean build of chromeos-chrome? doing an emerge-x86-generic --clean didn't do it.

[Trevor Bourget]

i updated issue 3464.

workaround for me was adding

export SANDBOX_WRITE=${SANDBOX_WRITE:+${SANDBOX_WRITE}:}$CHROME_ROOT

before the runhooks in the chromeos_chrome ebuild.

[Trevor Bourget]

the work directory didn't get cleaned up cleanly when it failed?

sudo rm -rf /build/$board/tmp/portage/chromeos-base/chromeos-chrome*
emerge-$board chromeos-chrome