Update on this. I managed to build with the ENABLE_GLES2 flag. This workaround was also required:
https://bugs.webkit.org/show_bug.cgi?id=195251
Unfortunately, this doesn't seem to let webkit pick up on panfrost. Instead, I get the error
with or without LD_LIBRARY_PATH=/opt/gl4es, whereas without the ENABLE_GLES2 flag, I was at least able to get the warning silenced by including the gl4es libGL.so in the ld library path.
So summing up: webkit needs these two workarounds from webkit's bug tracker, and I don't know how to make webkit at all performant on pinebook pro manjaro. All three versions (vanilla, w/gl4es, and w/ENABLE_GLES2) get a 1.00 on https://browserbench.org/motionmark, although subjectively gl4es feels the most responsive.
For what it's woth, midori on stock debian initially shows better performance on motionmark, but it freezes halfway through and can't actually get a score.
I'd love some help with this if anybody has any ideas for how to get webkit running better.
https://bugs.webkit.org/show_bug.cgi?id=195251
Unfortunately, this doesn't seem to let webkit pick up on panfrost. Instead, I get the error
Code:
** (luakit:150481): WARNING **: 14:07:15.988: GDK is not able to create a GL context, falling back to glReadPixels (slow!): Unable to create a GL contextwith or without LD_LIBRARY_PATH=/opt/gl4es, whereas without the ENABLE_GLES2 flag, I was at least able to get the warning silenced by including the gl4es libGL.so in the ld library path.
So summing up: webkit needs these two workarounds from webkit's bug tracker, and I don't know how to make webkit at all performant on pinebook pro manjaro. All three versions (vanilla, w/gl4es, and w/ENABLE_GLES2) get a 1.00 on https://browserbench.org/motionmark, although subjectively gl4es feels the most responsive.
For what it's woth, midori on stock debian initially shows better performance on motionmark, but it freezes halfway through and can't actually get a score.
I'd love some help with this if anybody has any ideas for how to get webkit running better.
