Error Building Chromium for use with Chromium OS (Simple Chrome)

[dub...@codeweavers.com]

I am trying to build a Chromium browser for use with my local Chromium OS build by follow the instructions here:

https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md

After this command:

cros chrome-sdk --board=$BOARD --log-level=info

I get a python backtrace ending with:

<snip>

...

 File "/home/duboisj/chromium/src/third_party/chromite/lib/cros_build_lib.py", line 182, in <genexpr>
    return ' '.join(ShellQuote(arg) for arg in cmd)
  File "/home/duboisj/chromium/src/third_party/chromite/lib/cros_build_lib.py", line 83, in ShellQuote
    s = s.encode('utf-8')

"UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1441: ordinal not in range(128)"

This appears right after a message:

 21:52:42: INFO: Installing Goma.

It looks to me like the real problem is that the script is trying this:

curl https://clients5.google.com/cxx-compiler-service/download/downloadurl

but failing with a 401 Unauthorized error (the python string that fails appears to be a short HTML blob saying basically 'permission denied')

Is this script expected to work for non-Goolger's, or have a missed some necessary config option to disable Goma etc.?  

I read a past thread about experimental Goma access for regular contributors, but I'm just trying to build locally.  

Thanks!

[Mike Frysinger]

please file a bug via https://crbug.com/new.  if the goma download fails, it should continue to work.

-mike

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/29be08a3-398b-4916-8175-1466f4a2fefe%40chromium.org.

[dub...@codeweavers.com]

Ok, bug filed:

https://bugs.chromium.org/p/chromium/issues/detail?id=849832

This is still my first time building Chromium for use with Chrome OS - hope it's not my setup.

I think I saw some option to pass to explicitly build without goma - I'll try that for now.

Thanks!

[Albert Bodenhamer]

Depending on your needs, cros-vm or linux-chromeos might be easier/more familiar paths. 

Like Mike says though, what you're doing sounds like it should be working so a bug is warranted.

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/aeafe53a-f405-4861-8289-1258d93d227c%40chromium.org.

--

Albert Bodenhamer | Software Engineer | abodenha@chromium.org 

[dub...@codeweavers.com]

Thanks!  I tried a VM setup once but my steps were not from that document.  I'll check the cros-vm steps out.

Albert Bodenhamer | Software Engineer | abod...@chromium.org 

[Albert Bodenhamer]

On Wed, Jun 6, 2018 at 3:53 AM <dub...@codeweavers.com> wrote:

Thanks!  I tried a VM setup once but my steps were not from that document.  I'll check the cros-vm steps out.

+Achuith Bhandarkar has been putting a lot of work into the VM stuff to simplify Chrome OS flows for Chrome devs.  It'd be good to know where the pain points are so we can address them.

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/07925e46-d267-4b67-98d3-eb6835d09b85%40chromium.org.

--

Albert Bodenhamer | Software Engineer | abodenha@chromium.org 

[Achuith Bhandarkar]

Please send me the link of the out-of-date instructions you followed to setup a VM for chromeos - I can update it.

[dub...@codeweavers.com]

On Wednesday, June 6, 2018 at 4:25:16 PM UTC-5, Achuith Bhandarkar wrote:

Please send me the link of the out-of-date instructions you followed to setup a VM for chromeos - I can update it.

My starting point was this, linked from www.chromium.org:

https://chromium.googlesource.com/chromiumos/docs/+/master/developer_guide.md

and in particular the 'Building an image to run in a virtual machine' section:

https://chromium.googlesource.com/chromiumos/docs/+/master/developer_guide.md#Building-an-image-to-run-in-a-virtual-machine

I'm not certain those steps differ in substance from the cros_vm page linked above, actually (I have not yet gone through the cros_vm page in detail).  

The steps I did follow (those from the general developer guide) resulted in a VM image which would launch, so it wasn't all bad.  The mouse was pretty broken (it's also broken running amd64_generic from a usb flash on my Eve) and I think there was some visual stutter.  But the build itself did appear to work and I could launch it in a VM.

My goal was a local build of Chrome OS, and my interest in making local modifications to Chromium was to get in a revert trying to make crostini work.  It looks like that revert made it upstream now, though, so that particular need may be gone.

During my build yesterday I also hit 2 other points of confusion: I had to run build/install-build-deps.sh but it wasn't obvious that I'd also need install-build-deps-android.sh (seemingly, I did).  Also, install-build-deps-android.sh seemed to succeed in installing Java 8, but complained because it failed to recognize that it had succeeded.  I didn't dig into these issues.

[Achuith Bhandarkar]

The developer guide has instructions on creating a VM, but nothing on how to launch the VM - I'll add those.

From within your chroot, you can launch your locally built VM following these instructions:

https://chromium.googlesource.com/chromiumos/docs/+/master/cros_vm.md#Launch-a-locally-built-VM-from-within-the-chroot

It looks like you got this far, so I'm guessing you followed the instructions that image_to_vm.sh outputs.

The broken mouse pointer is a known issue. I think there is a tracking bug somewhere but couldn't find it.

The simple chrome flow is the most convenient way to update chrome on chromeos, so your approach was correct.

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/779f2617-0839-41ba-9ff4-badafe300841%40chromium.org.