New issue
Advanced search Search tips

Issue 610392 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

aarch64 compilation failure in mojo shell

Reported by three...@gmail.com, May 9 2016

Issue description

When attempting to compile Chromium 51+ from source, compilation fails because of 2 syscalls that are not available on aarch64.


../../services/shell/runner/host/linux_sandbox.cc: In function ‘intptr_t shell::{anonymous}::SandboxSIGSYSHandler(const sandbox::arch_seccomp_data&, void*)’:
../../services/shell/runner/host/linux_sandbox.cc:41:10: error: ‘__NR_access’ was not declared in this scope
     case __NR_access:
          ^
../../services/shell/runner/host/linux_sandbox.cc:44:10: error: ‘__NR_open’ was not declared in this scope
     case __NR_open:
          ^

I have a patch that I am using that works, but I'm not entirely sure it's the best way to do it.

In Chromium 51, the path to the file is mojo/shell/runner/host/linux_sandbox.cc in 52 (and up, I assume), it's mojo/services/shell/runner/host/linux_sandbox.cc
 
0001-no-access-or-open-on-arm64.patch
988 bytes Download
Labels: Te-NeedsFurtherTriage
Components: Internals>Mojo

Comment 3 by sa...@chromium.org, Mar 23 2017

Status: Archived (was: Unconfirmed)

Sign in to add a comment