* Thierry Moreau (thierry.moreau@connotech.com) wrote:
On 29/05/18 04:40 AM, Victor Martinez wrote:
Hello Thierry,
Thanks for the quick and relevant reply. I should install NFS-based swap space (and a CPU cooling arrangement).
There are ports overlays for opt and xorg collections ready for arm64. I've tested them on the pine64 and all is working right with fbdev. I was able to run Mali on the cubieboard but I didn't mess with 64b stuff.
By any chance, would you have any hint about building the opt/webkitgtk port. I had success for every dependencies, but failed for webkitgtk itself on a missing JavaScriptCore/JSContextRef.h file which should have been made at work/src/build/DerivedSources/ForwardingHeaders/JavaScriptCore/JSContextRef.h .
No sorry Thierry. Only firefox and chromium experience here (only firefox for 64b arch).
Arm64 arch was tested the first time in CRUX-ARM 64b 3.3 and it will be officially supported on the next release (3.4) which we are working on currently. The base is ready from the toolchain to the ports overlays as you can see repositories and branches in the development section.
I don't like to play with packages because you need all linked ones. This is hard to manage and not the aim of a source based distro.
Well understood. The small changes I found necessary are all recorded in cloned git repositories. If I was more comfortable with git concepts, I would readily volunteer to share my findings.
E.g. I had to aling the source=(...) entry in a Pkgfile to match the contents of .md5sum in a port in opt-arm; I committed this with git, and now I must fight with git log and/or git rev-list options to remind me which port it was. Patience!
Feel free to share them and I'll check, test and update our tree.
Regards,
- Thierry
Regards, --- Victor Martinez Learning bit by bit | http://vjml.es