Slackware - ARMThis forum is for the discussion of Slackware ARM.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm trying to compile webkitgtk on a Raspberry PI. I have a slackware arm 14.1.
I'm usign the slackbuild taken from Slackbuilds.org for webkitgtk-2.2.2 but after about 8 hours of compilation I get:
error selected processor does not support arm mode 'vmov d1,r4,r2'
error selected processor does not support arm mode 'vcmpe.f64 d0,d1'
I added the --disable-silent-rules and --disable-jit to the configure options and now it is has been 40 hours since I started webkitgtk.SlackBuild. I have a Slackware 14.1 installation on Raspberry Pi:
chris@raspberrypi:~$ uname -a
Linux raspberrypi 3.10.22-091213 #1 PREEMPT Mon Dec 9 03:24:37 GMT 2013 armv6l BCM2708 GNU/Linux
Can anyone report how long this is expected to take?
from what Bart said to me via PM, not less than 60 hours...
Right. With those options enabled (--disable-silent-rules and --disable-jit added to slackbuild taken from Slackbuilds.org) took about 60 hours. Raspberry may also not be suitable for compiling packages but if you need a package that is not present in any repository does not have much choice.
Stuart has some hints on how you might go about a cross compilation environment here.
I had a bad time cross compiling back at the time I was using the Zaurus ... nowdays I tend to try native compilations for ARM but I do that mostly non my AC100 (with a dual core 1Ghz Tegra2 SOC which will probabbly compile things nearly 3 times faster then the Pi).
I'm also considering getting an ODROID-U3 (quad core 1.7Ghz and 2Gb ram) which should get things built pretty quickly.
The problem with webkitgtk is that it will not compile when you compile it with more than one thread. So even on a fast x86 8-core CPU compiling it takes virtually forever, a quad-core ARM CPU will not help that much either. Of course this is only true for some software projects, most of them compile fine multithreaded. Which brought me to an idea: I do not have any experience with emulating ARM on x86, but I know that Qemu is capable of doing that. Can anyone tell me how fast that is? If it is for a single emulated CPU faster than the PI it may be worth to compile webkitgtk in a VM instead, but that solution would, compared with the Pi, really shine for software that can be compiled multithreaded, since you can use more cores in the VM if you have a fast multicore x86 CPU.
it may be worth to compile webkitgtk in a VM instead
The versatile VM is not a performer and is limited to 256Mb ram so I don't think it's going to be any faster then the Pi.
even on a fast x86 8-core CPU compiling it takes virtually forever, a quad-core ARM CPU will not help that much either
Well if each core is running at 1.7Ghx then the cpu bound part con compilation will be more then twice as fast as the 700Mhz Pi even if you are not doing multijob compilation.
Also the ODROID-U3 can run off e-mmc which is supposed to be some 10 times faster then SDHC and the 2Gb ram will also help ... but I'd not buy one for compiling just one package
Did you have a look here: could you not be happy with version 1.8.3 ?
For x86 slackware there are a lot of places where you can get most packages you need but for ARM there are not many. Maybe we should team up and find a place to host the stuff we are building so that others may benefit.