similar to: Samba on Chrome OS

> On Apr 20, 2020, at 1:47 PM, James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > But the most recent NaCL toolchain release is based on LLVM 3.7 from 2015. > > Unless you're planning to upgrade the NaCL toolchain to use a new release based on LLVM devhead (which would seem a rather expensive thing to attempt now, given the plan to desupport it in a

Hi Fangrui, As you noted we are working on helping our NaCl users transition to WebAssembly and new web APIs that cover the functionality offered by NaCl. In terms of actually turning down the platform features, we recently announced a timeline at https://blog.chromium.org/2020/01/moving-forward-from-chrome-apps.html. In terms of LLM, I would prefer to keep the support we have in the tree until

Hi all, LLVM/Clang supports an OS called 'NaCl' (llvm/include/llvm/ADT/Triple.h). It apparently hasn't had any development since 2015. This page https://developer.chrome.com/native-client/migration mentions that NaCl is deprecated. Is it still used? If not, I would propose that we remove it. I created a patch https://reviews.llvm.org/D78441 which I think can delete 90% of the

Google Chrome Terms of Service(Google Chrome executable),?BSD?(source code and Chromium executable except chromium 5 beta),BSD License?with proprietary parts (source code and chromium 5 beta executable, as it integrates?Adobe Flash Player?10.1[1])[2] http://en.wikipedia.org/wiki/Google_Chrome in my?interpretation, this means Google Chrome is fully open-source, only the flash player has proprietary

> From the provided documentation I understood that in memory data > structures of a PNaCl program are incompatible to the host program because > ABIs are different (e.g. PNaCl pointers are always 32-bit even when running > on x86_64 platform). > So PNaCl program can't access any data structures of the host program > directly. The only communication way is by using syscalls,

Hello, I have heard that Chrome OS is Linux based, so I am wondering if there is anyway to use R on a Google Chromebook using one of your Linux packages. If not, do you plan on making a version of R that is compatible with chromebooks or cloud based? [[alternative HTML version deleted]]

Am 19.06.2013 18:01, schrieb JF Bastien: > > From the provided documentation I understood that in memory data > structures of a PNaCl program are incompatible to the host program > because ABIs are different (e.g. PNaCl pointers are always 32-bit > even when running on x86_64 platform). > So PNaCl program can't access any data structures of the host >

On 18 June 2013 15:27, Dmitri Rubinstein <dmitri.rubinstein at googlemail.com>wrote: > Is it possible to use PNaCl infrastructure (i.e. translation and execution > in a sandbox) without a Chrome ? > > I mean a something like a standalone VM like Java or Mono/C#. > Yes. The NaCl tool 'sel_ldr' will run a program inside a sandbox outside of the web browser. We do a

From the provided documentation I understood that in memory data structures of a PNaCl program are incompatible to the host program because ABIs are different (e.g. PNaCl pointers are always 32-bit even when running on x86_64 platform). So PNaCl program can't access any data structures of the host program directly. The only communication way is by using syscalls, but the document does not

On Thu, 28 Feb 2019 08:16:05 +0000, Greg KH <gregkh at linuxfoundation.org> wrote: Hi both, > > On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote: > > Hello, > > > > In my testing of crosvm[1] with Linux 4.4.175, I am observing failures > > on a 'kevin' Chromebook (RK3399) device - the guest kernel does not > > even get to the

On Thu, 28 Feb 2019 08:16:05 +0000, Greg KH <gregkh at linuxfoundation.org> wrote: Hi both, > > On Wed, Feb 27, 2019 at 04:36:39PM -0800, Daniel Verkamp wrote: > > Hello, > > > > In my testing of crosvm[1] with Linux 4.4.175, I am observing failures > > on a 'kevin' Chromebook (RK3399) device - the guest kernel does not > > even get to the

Hello all, The rich history of binary distribution formats based on LLVM [0][1][2][3][4] has proven LLVM's viability as a launchpad for stable platforms. However, issues with compilation time and compiler size have suggested that the translator must do too much, i.e. LLVM IR isn't a low-level enough virtual machine. So we introduce DAGIR ("dagger"), a new portable close to the

On a centos-7 machine where I was having this issue, updating just chrome from: google-chrome-stable-45.0.2454.101-1.x86_64 to: google-chrome-stable-46.0.2490.71-1.x86_64 seemed to resolve this problem. I realize that the OP is reporting this issue, on C6, with the release I just updated to. By the way, I haven't run into this problem with the versions from their beta release channel.

> On Sep 2, 2015, at 1:36 PM, zep <zgreenfelder at gmail.com> wrote: > > > > On 09/02/2015 03:12 PM, Wes James wrote: >> I use chrome on CentOS because I wrote a web socket web app and I can only get chrome to work properly with web sockets. >> >> I have a local web app created with erlang. It works like ms sccm to wake, freeze/thaw deepfreeze PCs and

On 10/19/2015 04:11 PM, Richard wrote: > > I was seeing issues like that on centos-7 with a couple of the > recent releases of chrome. What I found was that chrome didn't seem > to be shutting down fully -- leaving a process and the > ".com.google.Chrome..." lock file in /tmp. After cleaning those up > chrome would restart without issue. The release that you're

Hi all. I've updated google-chrome to recent version and it gets unbooted, when I fired google-chrome up I got messages like these: /usr/bin/google-chrome: /lib/libz.so.1: no version information available (required by /usr/bin/google-chrome) /usr/bin/google-chrome: /lib/libz.so.1: no version information available (required by /usr/bin/google-chrome) /opt/google/chrome/chrome:

I've installed Google Chrome using the Richard Lloyd 'install-chrome.sh' script (http://chrome.richardlloyd.org.uk/), and am finding a couple of nagging issues. (Current install is google-chrome-stable-46.0.2490.71-1.x86_64). First, every time I shut down Chrome and start it back up, it whines about not having been shut down "properly." Second, and worse, at start up,

Has anyone tested installing the newer kernels from elrepo (or somewhere else) in order to keep google-chrome updated beyond version 27? Actually, i assumed a newer kernel would come with a newer glibc but i do not see a newer glibc via elrepo, just newer kernels. hmmm. # yum --disablerepo=* --enablerepo=elrepo* info glibc | grep -i repo only lists my already installed glibc packages from

Having found no mention of Google's Chrome OS in the rsync archives, nor any useful* pointers via Google, I'm wondering if anyone here knows of an implementation of rsync client for Chrome OS in normal (not developer) mode, i.e. as an app or extension. * It seems that rsync is available in "test" builds of Chrome OS, but not in normal release builds. As far as I can tell,

I tried to install Google Chrome and received the dependencies error. Is Centos too old for the new Chrome or is there an older Chrome version that is compatible? Todd -- Ariste Software Petaluma, CA 94952 http://www.aristesoftware.com