Problem building chrome in chrome os

98 views
Skip to first unread message

Eugene Nalimov

unread,
Oct 17, 2011, 1:56:51 PM10/17/11
to Chromium OS dev
I am trying to build chrome as part of chromium os. I am following
instructions

http://www.chromium.org/chromium-os/developer-guide
http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/building-chromium-browser

I was able to build chromium os using pre-built binary and boot it on
my system. Now I am trying to build my own chrome, and here is the
problem. I updated my chrome enlistment, adding chromium os
dependencies, and launched cros_sdk pointing to the location of that
chrome. I set up FEATURES="-usersandbox" and
CHROME_ORIGIN=LOCAL_SOURCE, but now build fails trying to run gclient:

hromeos-chrome-16.0.909.0_rc-r1: * CHROME_ORIGIN VALUE is
LOCAL_SOURCE
chromeos-chrome-16.0.909.0_rc-r1: * /home/enal/chrome_root should be
set here properly
chromeos-chrome-16.0.909.0_rc-r1: * ERROR:
chromeos-base/chromeos-chrome-16.0.909.0_rc-r1 failed (prepare phase):
chromeos-chrome-16.0.909.0_rc-r1: * EGCLIENT at
/home/enal/depot_tools/gclient does not exist

Looks that script is trying to run gclient and expects it is stored in
~/depot_tools, but build environment has its own ~. and there is no
depot_tools there.

Problem happens when running both ./build_packages and emerge-x86-
alex.

Any ideas?

Thanks,
Eugene

Ami Fischman

unread,
Oct 17, 2011, 1:57:57 PM10/17/11
to en...@chromium.org, ChromiumOS-dev
Install depot_tools into ~/depot_tools in the chroot?

-a


--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
   http://groups.google.com/a/chromium.org/group/chromium-dev

Mike Frysinger

unread,
Oct 17, 2011, 2:37:05 PM10/17/11
to Ami Fischman, en...@chromium.org, ChromiumOS-dev
cros_sdk automatically mounts ~/depot_tools/ inside of the chroot when
it is run. but it only does this if gclient is in your $PATH outside
of the chroot.

$ cros_sdk
(cr) (cros_sdk) $ mount | grep depot_tools
/dev/mapper/jonwall-usr+local+google on /home/vapier/depot_tools type
ext4 (rw,relatime,barrier=1,data=writeback)
-mike

> --
> 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
>

Mike Frysinger

unread,
Oct 17, 2011, 3:32:45 PM10/17/11
to Eugene Nalimov, Ami Fischman, en...@chromium.org, ChromiumOS-dev
correct, cros' ebuild does not have an exported knob for you to
disable nacl. if you really want, you can edit the ebuilds in
third_party/chromiumos-overlay/chromeos-base/chromeos-chrome/ like so:
use_nacl() { return 1 ; }
-mike

On Mon, Oct 17, 2011 at 15:30, Eugene Nalimov <en...@google.com> wrote:
> Now I have next problem: I am getting syntax errors when compiling
> native client. On my Linux box I just turned off native client build
> by adding "disable_nacl":1 to include.gypi. Unfortunately, in cros_sdk
> environment, neither adding export GYP_DEFINES="disable_nacl=1" to
> ~./bashrc, nor adding ~/.gyp/include.gypi does not help...

Mike Frysinger

unread,
Oct 17, 2011, 3:45:22 PM10/17/11
to Eugene Nalimov, Ami Fischman, en...@chromium.org, ChromiumOS-dev
i'm guessing you're building it in the cros_sdk rather than
cross-compiling it for a board ? we test it for all the boards and
those seem to be working fine.
-mike

On Mon, Oct 17, 2011 at 15:38, Eugene Nalimov <en...@google.com> wrote:
> So, why I am getting errors when compiling native clients? Google
> "error: PP_GRAPHICS3DATTRIB_ALPHA_SIZE" and yo'll see I am not the
> only one... Recommended fix is just to disable build of native client.


>
> On Mon, Oct 17, 2011 at 12:32 PM, Mike Frysinger <vap...@chromium.org> wrote:
>> correct, cros' ebuild does not have an exported knob for you to
>> disable nacl.  if you really want, you can edit the ebuilds in
>> third_party/chromiumos-overlay/chromeos-base/chromeos-chrome/ like so:
>> use_nacl() { return 1 ; }
>>

Mike Frysinger

unread,
Oct 17, 2011, 4:02:09 PM10/17/11
to Eugene Nalimov, Ami Fischman, en...@chromium.org, ChromiumOS-dev
are you doing `emerge chromeos-chrome` or `emerge-x86-generic chromeos-chrome` ?

someone else will probably have to answer. i'm not terribly familiar
with chrome building itself.
-mike

On Mon, Oct 17, 2011 at 15:49, Eugene Nalimov <en...@google.com> wrote:
> Yes, I am building from cros_sdk, following instructions from
> http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/building-chromium-browser.
> It specifically says that LOCAL_BINARY is not recommended...

Jay Civelli

unread,
Dec 15, 2012, 7:01:48 PM12/15/12
to chromiu...@chromium.org
I had the same problem.
Adding depot_tools to my PATH in the shell before starting chroot did the trick.

Jay
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages