building epiphany on armv6

[bonbonbaron]

The armv6 repo appears to only have two options for internet browsers: Lynx and Dillo3. (In fact, the armv6 lacks a lot of things... I drool at the options hiding away in the other repos.)

Seeing epiphany was on armv7, I figured it ought to be doable building it for armv6. I git cloned the source code, got meson for building, and... It complained I didn't have linkers gcc-ar, ar, or gar. Playing around, I tried to run gcc-ar, and it says,

Code: [Select]

"Error whie loading shared libraries: libfl.so.2: cannot open shared object file: No such file or directory."I may be in over my head building this thing. I've never used meson before, only gcc for C projects. I'm not asking for the answer to how to do it, just a general procedure of how to solve this type of problem. Or any words of widsom for that matter. Please be kind to the newb.

Thanks for your time,
Michael

[Rich]

Hi bonbonbaron
Maybe the compile instructions found here will be of some help:
http://tinycorelinux.net/9.x/armv7/tcz/src/epiphany/

[bonbonbaron]

Hi bonbonbaron
Maybe the compile instructions found here will be of some help:
http://tinycorelinux.net/9.x/armv7/tcz/src/epiphany/

Thanks for the suggestion. I tried it, but I get an error:

Code: [Select]

ninja: error: loading 'build.ninja': No such file or directoryBut that kind of makes sense, because when you look at the ninja stuff at the bottom of that webpage, there appears to be a typo:

Code: [Select]

ninja [1m 46.37s]

[Rich]

Hi bonbonbaron

... But that kind of makes sense, because when you look at the ninja stuff at the bottom of that webpage, there appears to be a typo:

Code: [Select]

ninja [1m 46.37s]

The  [1m 46.37s]  is probably a note to document how long it took  ninja  to execute, not a typo.

[Juanito]

The epiphany extension posted in the piCore 9.x armv7 repo should work with armv6 - I didn't put it in the repo because I do not have suitable hardware to test it on.

[bonbonbaron]

The epiphany extension posted in the piCore 9.x armv7 repo should work with armv6 - I didn't put it in the repo because I do not have suitable hardware to test it on.

Thanks for the tip. I was able to load it manually with wget. After that, I tce-loaded (-wi) all the dependencies it complained about-- always trying armv6 first, and when it wasn't there, I resorted to armv7. Surprisingly, it worked. But my hardware must be unsuitable as well, because the browser took about 30 seconds to open. Then loading www.github.com took well over five minutes lol.

Dillo3 crashes a lot, so maybe I ought to use lynx. However, it doesn't have --with-ssl, barring off every HTTPS site in the world.

Researching to see what my best bet is here...

[Rich]

Hi bonbonbaron

...  But my hardware must be unsuitable as well, because the browser took about 30 seconds to open. Then loading www.github.com took well over five minutes lol. ...

Try starting it from the command line and see if it's throwing any errors.

[bonbonbaron]

Try starting it from the command line and see if it's throwing any errors.

Code: [Select]

(epiphany:10082) WARNING**: AT-SPI: Could not obtain desktop path or name
(epiphany:10082) WARNING**: atk-bridge: GetRegisteredEvents returend message with unknown signature
(epiphany:10082) WARNING**: atk-bridge: get_device_events_reply: unknown signature
(epiphany:10082) WARNING**: atk-bridge: get_device_events_reply: unknown signature
(WebKitWebProcess:10110) WARNING**: AT-SPI: Could not obtain desktop path or name
(WebKitWebProcess:10110) WARNING**: atk-bridge: GetRegisteredEvents returend message with unknown signature
** Message: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files.
(WebKitWebProcess:10110): WARNING**: failed to search secrets in password schema: The name org.freedesktop.secrets was not provided by any .service files.

I hand-typed all that, so please mind any potential typos.

[Rich]

Hi bonbonbaron
Does it work any better if you do this:

Code: [Select]

export NO_AT_BRIDGE=1
epiphany

[Juanito]

You could try /usr/local/lib/webkit2gtk-4.0/MiniBrowser to see if it is any quicker.

[bonbonbaron]

Hi bonbonbaron
Does it work any better if you do this:

Code: [Select]

export NO_AT_BRIDGE=1
epiphany

Epiphany is slightly faster (opens in 20 seconds) after I export that variable.

You could try /usr/local/lib/webkit2gtk-4.0/MiniBrowser to see if it is any quicker.

Thanks for the suggestion. I tried it, it opened in a few seconds, and... then the brower's a tad too big for my 12" monitor, and there's a message on the page that says "Invalid TLS Certificate. Failed to load https://www.webkitgtk.org/: Do you want to continue ignoring the TLS errors?" I tried tabbing and hitting Enter over and over in hopes I would hit an offscreen OK button, but no dice. My usual Alt+D and Ctrl+L hotkeys, which work in most browsers, fail to bring my focus to the search bar too.

In the terminal, it shows that both browsers are giving me a

Code: [Select]

GLib-GIO-CRITICAL **: g_tls_connection_get_peer_certificate_errors: assertion 'G_IS_TLS_CONNECTION (conn)' failed.Interesting.

Geez, there's gotta be some viable internet browser for armv6 piCore 9.x. I'm open to any recommendations at this point.

[Rich]

Hi bonbonbaron

... and... then the brower's a tad too big for my 12" monitor, ...

If a program is too big for the screen, try hitting  Ctrl-Alt-M  a couple of times. You can also try:

Code: [Select]

/usr/local/lib/webkit2gtk-4.0/MiniBrowser --helpand see if there is a  geometry  option that lets you specify the size.

[curaga]

Webkit dropped armv6 support years ago, Chrome never had it, etc. They only run in "software" mode, making them very slow on an already very slow device. It's not a particularly good setup to use for browsing.

[bonbonbaron]

Webkit dropped armv6 support years ago, Chrome never had it, etc. They only run in "software" mode, making them very slow on an already very slow device. It's not a particularly good setup to use for browsing.

Good to know, thanks. Sadly it seems I've proven Tiny Core isn't a good fit for my purposes on the Pi0W. The amount of options for ARMV6 is too restrictive.