[chromium-dev] Chromium PPC64 port

[d***@free.fr]

Hello,

Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.

Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.

We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium

For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.

Don't hesitate to join #talos-workstation on Freenode to ask questions and
eventually contribute.

[d***@free.fr]

We finished porting sandbox, webrtc and currently finishing breakpad /
crashpad, and then we can start with Chromium's core code (if necessary).
We will probably have an important amount of work to port for big endian
PowerPC here. Little Endian PowerPC exists so it will be working there
first.

See https://wiki.raptorcs.com/wiki/Porting/Chromium for updated details.
Don't hesitate to comment here to show your interest.

Post by d***@free.fr
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions and
eventually contribute.

[Dan Horák]

Hi, I'm definitely interested, QT WebEngine is based on Chromium and
becomes mandatory for a growing number of projects, some switching from
QtWebKit.

[Shawn Anastasio]

A quick status update.

Major progress had been made and the browser now compiles, runs, and
performs well in multiple online javascript benchmarks.

The biggest issue as of now is the presence of major motion-related
artifacting when rendering VP9 videos, as demonstrated in this screenshot:
Loading Image...

It is my understanding that chromium's VP9 rendering is handled through
libvpx, which already boasts ppc64le support and passes all unit tests when
compiled out-of-tree.

If anybody is able to offer any insight on the issue, it would be greatly
appreciated.

-- Shawn

Post by d***@free.fr
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions and
eventually contribute.

[Shawn Anastasio]

Upon further investigation by tpearson, it seems that all relevant media
unit tests pass which makes this issue even more perplexing.

Specifically, the tests produced by the ninja target "media_unittests" all
pass, with the exception of one which also fails on ARM:
https://chromium.googlesource.com/chromium/src/+/b355adc86e9d4635a3f1a23567035f96bd39d428.

This, at the very least, seems to indicate that chromium's unit tests for
vp9 playback are incomplete or faulty.
Some input from those involved with the chromium media bits would be
greatly appreciated.

--Shawn

Post by Shawn Anastasio
A quick status update.
Major progress had been made and the browser now compiles, runs, and
performs well in multiple online javascript benchmarks.
The biggest issue as of now is the presence of major motion-related
http://imgbin.ca/image.uploads/22-09-2018/original-9675b6216b0c19e519ef2a11a9a2c5fa.png
It is my understanding that chromium's VP9 rendering is handled through
libvpx, which already boasts ppc64le support and passes all unit tests when
compiled out-of-tree.
If anybody is able to offer any insight on the issue, it would be greatly
appreciated.
-- Shawn

Post by d***@free.fr
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions
and eventually contribute.

[PhistucK]

For media related discussions, I suggest
https://groups.google.com/a/chromium.org/d/forum/media-dev.

☆*PhistucK*

Post by Shawn Anastasio
Upon further investigation by tpearson, it seems that all relevant media
unit tests pass which makes this issue even more perplexing.
Specifically, the tests produced by the ninja target "media_unittests" all
https://chromium.googlesource.com/chromium/src/+/b355adc86e9d4635a3f1a23567035f96bd39d428
.
This, at the very least, seems to indicate that chromium's unit tests for
vp9 playback are incomplete or faulty.
Some input from those involved with the chromium media bits would be
greatly appreciated.
--Shawn

Post by Shawn Anastasio
A quick status update.
Major progress had been made and the browser now compiles, runs, and
performs well in multiple online javascript benchmarks.
The biggest issue as of now is the presence of major motion-related
http://imgbin.ca/image.uploads/22-09-2018/original-9675b6216b0c19e519ef2a11a9a2c5fa.png
It is my understanding that chromium's VP9 rendering is handled through
libvpx, which already boasts ppc64le support and passes all unit tests when
compiled out-of-tree.
If anybody is able to offer any insight on the issue, it would be greatly
appreciated.
-- Shawn

Post by d***@free.fr
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions
and eventually contribute.

--

--
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
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/e6edd18d-7ad3-4023-b3c8-8e7a39abc0b8%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/e6edd18d-7ad3-4023-b3c8-8e7a39abc0b8%40chromium.org?utm_medium=email&utm_source=footer>
.

[Timothy Pearson]

Here's a screenshot of the browser working on ppc64. Note the VP9 issue
as the only remaining blocker; once that's fixed we should be good to
start upstreaming / provide built binaries via the various Linux distros.

After looking into the flaw some, I'm unclear as to whether libvpx,
ffmpeg (libavcodec), or something else is handling the decode. libvpx
seems to be functioning correctly when built out of tree in order to run
the unit tests. I am not sure why it would be failing inside Chrome
unless there is another library in play.
Which decoder library or libraries are actually used to display vp9
content in the latest Chrome source tree?
Thanks!

Post by Shawn Anastasio
A quick status update.
Major progress had been made and the browser now compiles, runs, and
performs well in multiple online javascript benchmarks.
The biggest issue as of now is the presence of major motion-related
http://imgbin.ca/image.uploads/22-09-2018/original-9675b6216b0c19e519ef2a11a9a2c5fa.png
It is my understanding that chromium's VP9 rendering is handled through
libvpx, which already boasts ppc64le support and passes all unit tests
when compiled out-of-tree.
If anybody is able to offer any insight on the issue, it would be
greatly appreciated.
-- Shawn
Hello,
Along with the #talos-workstation community on Freenode IRC, I've
been working on porting Chromium to PPC, we've got a development
environment on ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name
of Talos II (I own one), we currently lack a browser with JS JIT,
Chromium seems like the shortest path to this goal along with
WebKit, which is why we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
<https://wiki.raptorcs.com/wiki/Porting/Chromium>
For now it is just a very dirty draft of the instructions to get the
dev env working, to actually start porting code, then the goal is to
get changes merged upstream. This page will probably become a more
structured resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask
questions and eventually contribute.

--
Timothy Pearson
Raptor Engineering
[phone] (direct line)
[phone] (switchboard)
https://www.raptorengineering.com

[Timothy Pearson]

Since my messages were posted to the list out of order, I figured I
should follow up with current status.

Thanks to the hints at
https://groups.google.com/a/chromium.org/forum/#!topic/media-dev/sh3dVaFPAqY
we have determined it is a libvpx issue related to VSX / AltiVec
acceleration. We have since rebuilt the browser with libvpx using
generic code, and the result appears to be working properly. We will be
starting to submit code for upstreaming shortly and will post links here
to the various patches on the code review system.

Post by Timothy Pearson
Here's a screenshot of the browser working on ppc64. Note the VP9 issue
as the only remaining blocker; once that's fixed we should be good to
start upstreaming / provide built binaries via the various Linux distros.

After looking into the flaw some, I'm unclear as to whether libvpx,
ffmpeg (libavcodec), or something else is handling the decode. libvpx
seems to be functioning correctly when built out of tree in order to run
the unit tests. I am not sure why it would be failing inside Chrome
unless there is another library in play.
Which decoder library or libraries are actually used to display vp9
content in the latest Chrome source tree?
Thanks!

Post by Shawn Anastasio
A quick status update.
Major progress had been made and the browser now compiles, runs, and
performs well in multiple online javascript benchmarks.
The biggest issue as of now is the presence of major motion-related
http://imgbin.ca/image.uploads/22-09-2018/original-9675b6216b0c19e519ef2a11a9a2c5fa.png
It is my understanding that chromium's VP9 rendering is handled through
libvpx, which already boasts ppc64le support and passes all unit tests
when compiled out-of-tree.
If anybody is able to offer any insight on the issue, it would be
greatly appreciated.
-- Shawn
Hello,
Along with the #talos-workstation community on Freenode IRC, I've
been working on porting Chromium to PPC, we've got a development
environment on ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name
of Talos II (I own one), we currently lack a browser with JS JIT,
Chromium seems like the shortest path to this goal along with
WebKit, which is why we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
<https://wiki.raptorcs.com/wiki/Porting/Chromium>
For now it is just a very dirty draft of the instructions to get the
dev env working, to actually start porting code, then the goal is to
get changes merged upstream. This page will probably become a more
structured resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask
questions and eventually contribute.

--
Timothy Pearson
Raptor Engineering
[phone] (direct line)
[phone] (switchboard)
https://www.raptorengineering.com

[Timothy Pearson]

The first of these patches is now up for review here:

https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1242633

Post by Timothy Pearson
Since my messages were posted to the list out of order, I figured I
should follow up with current status.
Thanks to the hints at
https://groups.google.com/a/chromium.org/forum/#!topic/media-dev/sh3dVaFPAqY
we have determined it is a libvpx issue related to VSX / AltiVec
acceleration. We have since rebuilt the browser with libvpx using
generic code, and the result appears to be working properly. We will be
starting to submit code for upstreaming shortly and will post links here
to the various patches on the code review system.

Post by Timothy Pearson
Here's a screenshot of the browser working on ppc64. Note the VP9 issue
as the only remaining blocker; once that's fixed we should be good to
start upstreaming / provide built binaries via the various Linux distros.

After looking into the flaw some, I'm unclear as to whether libvpx,
ffmpeg (libavcodec), or something else is handling the decode. libvpx
seems to be functioning correctly when built out of tree in order to run
the unit tests. I am not sure why it would be failing inside Chrome
unless there is another library in play.
Which decoder library or libraries are actually used to display vp9
content in the latest Chrome source tree?
Thanks!

Post by Shawn Anastasio
A quick status update.
Major progress had been made and the browser now compiles, runs, and
performs well in multiple online javascript benchmarks.
The biggest issue as of now is the presence of major motion-related
http://imgbin.ca/image.uploads/22-09-2018/original-9675b6216b0c19e519ef2a11a9a2c5fa.png
It is my understanding that chromium's VP9 rendering is handled through
libvpx, which already boasts ppc64le support and passes all unit tests
when compiled out-of-tree.
If anybody is able to offer any insight on the issue, it would be
greatly appreciated.
-- Shawn
Hello,
Along with the #talos-workstation community on Freenode IRC, I've
been working on porting Chromium to PPC, we've got a development
environment on ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name
of Talos II (I own one), we currently lack a browser with JS JIT,
Chromium seems like the shortest path to this goal along with
WebKit, which is why we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
<https://wiki.raptorcs.com/wiki/Porting/Chromium>
For now it is just a very dirty draft of the instructions to get the
dev env working, to actually start porting code, then the goal is to
get changes merged upstream. This page will probably become a more
structured resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask
questions and eventually contribute.

--
Timothy Pearson
Raptor Engineering
[phone] (direct line)
[phone] (switchboard)
https://www.raptorengineering.com

[Sandip Giri]

Post by d***@free.fr
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions and
eventually contribute.
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions and
eventually contribute.

Hi,



I'm trying to validate the chrome on power8 using the steps provided here -
https://wiki.raptorcs.com/wiki/Porting/Chromium

However, 7 patches are failing (might be due to the recent changes in
chromium source). PFA file for the details.



Has anyone updated these patches to work with latest chromium source? or
These patches were created for specific chromium branch or commit ?



Thanks,

Sandip

[Shawn Anastasio]

Hi Sandip,

I've updated the wiki with patches that apply against the latest chromium
git. Note that the crashpad patch failure is harmless and a few of the
patches are no longer needed, including one of the pdfium patches and the
gcc-only patches.
That leaves the following patches which needed updating:
0001-DONTMERGE-Disable-v8-unit-tests.patch
0001-pdfium-allocator-Use-64k-page-sizes-on-ppc64.patch
0001-Properly-detect-little-endian-PPC64-systems.patch
0001-services-service_manager-sandbox-linux-Fix-TCGETS-de.patch

Please try again with the latest versions of the above patches from the
wiki.

Thanks,
Shawn

Post by Sandip Giri

Post by d***@free.fr
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions
and eventually contribute.
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions
and eventually contribute.

Hi,
I'm trying to validate the chrome on power8 using the steps provided here
- https://wiki.raptorcs.com/wiki/Porting/Chromium
However, 7 patches are failing (might be due to the recent changes in
chromium source). PFA file for the details.
Has anyone updated these patches to work with latest chromium source? or
These patches were created for specific chromium branch or commit ?
Thanks,
Sandip

[Sandip Giri]

Thanks Shawn! Now all the patches have been applied successfully and Chrome built without any issue.
$ ./out/Default/chrome --version
Chromium 72.0.3611.0

1) I have validated the chrome-headless on ubuntu ppc vm , looks like it's working fine.
To validate chrome-headless , I have used the steps mentioned here - https://developers.google.com/web/updates/2017/04/headless-chrome , see below :

Starting Headless (CLI)
The easiest way to get started with headless mode is to open the Chrome binary from the command line. If you've got Chrome 59+ installed, start Chrome with the --headless flag:
$ chrome --version
Chromium 72.0.3611.0
$ chrome --headless --disable-gpu --remote-debugging-port=9222 https://www.chromestatus.com --no-sandbox
DevTools listening on ws://127.0.0.1:9222/devtools/browser/8d226099-b69a-4b78-b4f4-7ff2d1a81f01

Command line features
In some cases, you may not need to programmatically script Headless Chrome. There are some useful command line flags to perform common tasks.
**Printing the DOM**
The --dump-dom flag prints document.body.innerHTML to stdout:
$ chrome --headless --disable-gpu --dump-dom https://www.chromestatus.com/
**Create a PDF**
The --print-to-pdf flag creates a PDF of the page:
$ chrome --headless --disable-gpu --print-to-pdf https://www.chromestatus.com/ --no-sandbox
[1116/065342.750493:INFO:headless_shell.cc(534)] Written to file output.pdf
**Taking screenshots**
To capture a screenshot of a page, use the --screenshot flag:
$ chrome --headless --disable-gpu --screenshot https://www.chromestatus.com/ --no-sandbox
[1116/065440.525950:INFO:headless_shell.cc(534)] Written to file screenshot.png.
# Size of a standard letterhead.
$ chrome --headless --disable-gpu --screenshot --window-size=1280,1696 https://www.chromestatus.com/ --no-sandbox
[1116/065533.417761:INFO:headless_shell.cc(534)] Written to file screenshot.png.

And few more commands are there for testing the chrome-headless browser.


2) Now started validation of chrome.
To validate chrome need VNC setup. Installed and Configured VNC on Ubuntu vm.

Tried to launch the chrome browser on VNC setup , however currently it's failing with the below error :
$ chrome --version
Chromium 72.0.3611.0
$ chrome www.google.com --no-sandbox
(process:1953): Gtk-WARNING **: 12:01:17.442: Locale not supported by C library.
Using the fallback 'C' locale.

(chrome:1953): Gtk-WARNING **: 12:01:17.443: cannot open display: localhost:5903

Looking into this.

3) Also, I have started validating the chrome and chrome-headless with one of the node module which needs chrome/chrome-headless to execute the tests.
git clone https://github.com/recharts/recharts.git
cd recharts
npm install
npm test # Test execution needs CHROME browser

Initially I was getting the below error :
15 11 2018 12:44:09.505:INFO [karma-server]: Karma v3.1.1 server started at http://0.0.0.0:9876/
15 11 2018 12:44:09.505:INFO [launcher]: Launching browsers Chrome with concurrency unlimited
15 11 2018 12:44:09.633:INFO [launcher]: Starting browser Chrome
15 11 2018 12:44:09.635:ERROR [launcher]: No binary for Chrome browser on your platform.
Please, set "CHROME_BIN" env variable.

The issue got resolved after setting CHROME_BIN="/path/to/chrome/binary"
However , currently I'm getting the below issue :
15 11 2018 12:46:22.421:INFO [karma-server]: Karma v3.1.1 server started at http://0.0.0.0:9876/
15 11 2018 12:46:22.421:INFO [launcher]: Launching browsers Chrome with concurrency unlimited
15 11 2018 12:46:22.425:INFO [launcher]: Starting browser Chrome
15 11 2018 12:46:22.459:ERROR [karma-server]: { Error: spawn EACCES
at _errnoException (util.js:1022:11)
at ChildProcess.spawn (internal/child_process.js:323:11)
at exports.spawn (child_process.js:502:9)
at spawnWithoutOutput (/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/process.js:166:26)
at Object.ProcessLauncher._execCommand (/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/process.js:75:21)
at Object.ProcessLauncher._start (/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/process.js:33:10)
at Object.<anonymous> (/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/process.js:19:10)
at emitOne (events.js:121:20)
at Object.emit (events.js:211:7)
at Object.BaseLauncher.start (/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/base.js:43:10)
at Object.jobs.add [as j] (/home/build-user/browser-test/recharts/node_modules/karma/lib/launcher.js:85:17)
at Object.setTimeout.bind.j (/home/build-user/browser-test/recharts/node_modules/qjobs/qjobs.js:143:18)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
at Timer.listOnTimeout (timers.js:277:5) code: 'EACCES', errno: 'EACCES', syscall: 'spawn' }
npm ERR! Test failed. See above for more details.

Looking into this.


Thanks,
Sandip

[Sandip Giri]

Hi ,



*Chrome and ChromeHeadless validation Summary on ppc64le*:



1. Chrome built successfully using the steps provided here -
https://wiki.raptorcs.com/wiki/Porting/Chromium
2. Launched both the browsers successfully.


1. Chrome command :

$ chrome --no-sandbox


1. ChromeHeadless command :

$ chrome --headless --disable-gpu --remote-debugging-port=9222 https:
//www.chromestatus.com --no-sandbox

DevTools listening on ws://
127.0.0.1:9222/devtools/browser/8d226099-b69a-4b78-b4f4-7ff2d1a81f01
<http://www.google.com/url?q=http%3A%2F%2F127.0.0.1%3A9222%2Fdevtools%2Fbrowser%2F8d226099-b69a-4b78-b4f4-7ff2d1a81f01&sa=D&sntz=1&usg=AFQjCNHhdPFSG4N_IT0JMcjbBYOFk8ugcg>



1. Also , successfully validated both the browsers with one of the node
module , which needs these browsers to execute the tests.

Thanks,

Sandip

Post by Sandip Giri
Thanks Shawn! Now all the patches have been applied successfully and
Chrome built without any issue.
$ ./out/Default/chrome --version
Chromium 72.0.3611.0
1) I have validated the chrome-headless on ubuntu ppc vm , looks like it's working fine.
To validate chrome-headless , I have used the steps mentioned here -
https://developers.google.com/web/updates/2017/04/headless-chrome , see
Starting Headless (CLI)
The easiest way to get started with headless mode is to open the Chrome
binary from the command line. If you've got Chrome 59+ installed, start
$ chrome --version
Chromium 72.0.3611.0
$ chrome --headless --disable-gpu --remote-debugging-port=9222
https://www.chromestatus.com --no-sandbox
DevTools listening on ws://
127.0.0.1:9222/devtools/browser/8d226099-b69a-4b78-b4f4-7ff2d1a81f01
Command line features
In some cases, you may not need to programmatically script Headless
Chrome. There are some useful command line flags to perform common tasks.
**Printing the DOM**
$ chrome --headless --disable-gpu --dump-dom https://www.chromestatus.com/
**Create a PDF**
$ chrome --headless --disable-gpu --print-to-pdf
https://www.chromestatus.com/ --no-sandbox
[1116/065342.750493:INFO:headless_shell.cc(534)] Written to file output.pdf
**Taking screenshots**
$ chrome --headless --disable-gpu --screenshot
https://www.chromestatus.com/ --no-sandbox
[1116/065440.525950:INFO:headless_shell.cc(534)] Written to file screenshot.png.
# Size of a standard letterhead.
$ chrome --headless --disable-gpu --screenshot --window-size=1280,1696
https://www.chromestatus.com/ --no-sandbox
[1116/065533.417761:INFO:headless_shell.cc(534)] Written to file screenshot.png.
And few more commands are there for testing the chrome-headless browser.
2) Now started validation of chrome.
To validate chrome need VNC setup. Installed and Configured VNC on Ubuntu vm.
Tried to launch the chrome browser on VNC setup , however currently it's
$ chrome --version
Chromium 72.0.3611.0
$ chrome www.google.com --no-sandbox
(process:1953): Gtk-WARNING **: 12:01:17.442: Locale not supported by C library.
Using the fallback 'C' locale.
(chrome:1953): Gtk-WARNING **: 12:01:17.443: cannot open display: localhost:5903
Looking into this.
3) Also, I have started validating the chrome and chrome-headless with one
of the node module which needs chrome/chrome-headless to execute the tests.
git clone https://github.com/recharts/recharts.git
cd recharts
npm install
npm test # Test execution needs CHROME browser
15 11 2018 12:44:09.505:INFO [karma-server]: Karma v3.1.1 server started
at http://0.0.0.0:9876/
15 11 2018 12:44:09.505:INFO [launcher]: Launching browsers Chrome with
concurrency unlimited
15 11 2018 12:44:09.633:INFO [launcher]: Starting browser Chrome
15 11 2018 12:44:09.635:ERROR [launcher]: No binary for Chrome browser on your platform.
Please, set "CHROME_BIN" env variable.
The issue got resolved after setting CHROME_BIN="/path/to/chrome/binary"
15 11 2018 12:46:22.421:INFO [karma-server]: Karma v3.1.1 server started
at http://0.0.0.0:9876/
15 11 2018 12:46:22.421:INFO [launcher]: Launching browsers Chrome with
concurrency unlimited
15 11 2018 12:46:22.425:INFO [launcher]: Starting browser Chrome
15 11 2018 12:46:22.459:ERROR [karma-server]: { Error: spawn EACCES
at _errnoException (util.js:1022:11)
at ChildProcess.spawn (internal/child_process.js:323:11)
at exports.spawn (child_process.js:502:9)
at spawnWithoutOutput
(/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/process.js:166:26)
at Object.ProcessLauncher._execCommand
(/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/process.js:75:21)
at Object.ProcessLauncher._start
(/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/process.js:33:10)
at Object.<anonymous>
(/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/process.js:19:10)
at emitOne (events.js:121:20)
at Object.emit (events.js:211:7)
at Object.BaseLauncher.start
(/home/build-user/browser-test/recharts/node_modules/karma/lib/launchers/base.js:43:10)
at Object.jobs.add [as j]
(/home/build-user/browser-test/recharts/node_modules/karma/lib/launcher.js:85:17)
at Object.setTimeout.bind.j
(/home/build-user/browser-test/recharts/node_modules/qjobs/qjobs.js:143:18)
at ontimeout (timers.js:482:11)
at tryOnTimeout (timers.js:317:5)
'EACCES', syscall: 'spawn' }
npm ERR! Test failed. See above for more details.
Looking into this.
Thanks,
Sandip

[Vaibhav Sood]

Hi,

I am trying to apply the breakpad
patch https://wiki.raptorcs.com/w/images/f/f7/0001-Implement-ppc64-support-on-linux.patch
to standalone breakpad sources (cloned sources as per
here: https://chromium.googlesource.com/breakpad/breakpad/)

The patch applies correctly, breakpad depends on the LSS header file so
applied this patch to the LSS
header: https://wiki.raptorcs.com/wiki/File:0001-WIP-ppc64-support.patch

This however leads to build errors. However, as per this thread, all
patches(including breakpad) apply/build/run correctly when applied to the
Chrome source tree

My queries:

1) Is breakpad ported completely to ppc64le?
2) If yes, is there a difference to get breakpad to run correctly in
standalone versus when it is part of the Chrome source?

My observations: under built Chrome sources with all power patches from
this thread applied, :~/chromium/src/out/Default/obj/third_party/breakpad
binary exists.
However, breakpad in standalone has processor/minidump_stackwalk,
processor/minidump_dump etc binaries which i could not find under the built
Chrome source tree

Post by d***@free.fr
Hello,
Along with the #talos-workstation community on Freenode IRC, I've been
working on porting Chromium to PPC, we've got a development environment on
ppc64le, build system is working.
Raptor Computing Systems sells Desktop POWER9 systems under the name of
Talos II (I own one), we currently lack a browser with JS JIT, Chromium
seems like the shortest path to this goal along with WebKit, which is why
we're putting effort in this port.
We'll be trying to keep track on that page,
https://wiki.raptorcs.com/wiki/Porting/Chromium
For now it is just a very dirty draft of the instructions to get the dev
env working, to actually start porting code, then the goal is to get
changes merged upstream. This page will probably become a more structured
resource to know what is left to do.
Don't hesitate to join #talos-workstation on Freenode to ask questions and
eventually contribute.