chromium not working

[joao]

starting chromium with: $this->bbcode_second_pass_code('', 'chromium --disable-gpu') removes the error: $this->bbcode_second_pass_code('', 'InitializeSandbox() called with multiple threads in process gpu-process') but the following error persisits:$this->bbcode_second_pass_code('', 'terminated by signal SIGSEGV (Address boundary error)')

[moonman]

Finally compiled. See if this works:
$this->bbcode_second_pass_code('', 'https://olegtown.pw/Public/ArchLinuxArm/Chromium/chromium-49.0.2623.112-1-armv7h.pkg.tar.xz')
mirror: http://www.mediafire.com/download/8408b ... pkg.tar.xz

[wakko]

It's working for me on my odroid-u3.

thx!

[mauri]

it is working for me also on a RPI2

Many many thanks, you made my day

Maurizio

[kalasmannen]

$this->bbcode_second_pass_quote('moonman', 'F')inally compiled. See if this works:

[moonman]

You PKGBUILD seems fine with all the right modifications (well, there should only be the one).
Did you use GCC 5.1?
Also qemu has been known to cause problems in the past. Certain packages behaved erraticaly or segfaulted. It is an emulator after all. You can use distcc to x86 which uses a native compiler that spits out arm code (no emulators) to speed up the process. I didn't do that this time since my distcc helper has GCC 5.3.
It takes around 15 hours on odroid U2 to build chromium. It would be interesting to see how long it takes on RPI

[hmeyer]

moonman: It takes around 15 hours on odroid U2 to build chromium.
... thankyou again for your effort
> mirror: http://www.mediafire.com/download/8408b ... pkg.tar.xz
... why isn't that being put to the official repository?

[kalasmannen]

$this->bbcode_second_pass_quote('moonman', 'D')id you use GCC 5.1?

[moonman]

There is a bug in GCC that causes segfaults. We haven't been able to pinpoint what causes it though. Even current stable GCC 5.1 has the same problem. Somewhere in this thread I've linked to GCC 5.1 packages that work.

But there are more things in play here:
since a while ago ArchLinux and ALAM is switched to the new CXX11 ABI by default. The GCC 5.1 packages I linked to by default spit out binaries that use older ABI. That is why you need to pass -D_GLIBCXX_USE_CXX11_ABI=1 when compiling chromium. AFAIK any version starting wtih GCC 5.0 supports CXX11 ABI, so you could potentially use something older, but then again they might have introduced the same bug into current stable branch of 5.0.

GCC 5.1 can be recompiled to use CXX11 ABI by default, but the sources that were used to create a working GCC 5.1 build are not available anymore because they are too old and as I said before current GCC 5.1 branch has exactly the same bug.

Now the reason why the chromium I compiled is not in the repos is because everything in the repos comes out from the build farm, the build farm uses GCC 5.3 because that is what is current right now.

Now I was unable to compile chromium 50 with the same trick by using -D_GLIBCXX_USE_CXX11_ABI=1 flag. Looks like the flag does not get passed to one of the separate libraries that get compiled along with chromium and final linking fails.

[joao]

Mooman, thanks so much for offering your time to build a crhomium that works for us on Armv7.
Do you know whether the GCC devs are aware of the issue?