Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Apparently, your assembler (literally named: as) disagree that this instruction is valid for your target CPU architecture.
That could be generated by a GCC issue, sometimes by a smart ass programmer who inserted some assembler code in those files, but usually by the tentative to build for a unsupported CPU architecture.
For example, trying to use ARMv7 hardfloat code in a ARMv6 softfloat architecture.
As a side note, I hope that you are aware that SBO guys does not support ARM architecture, and they simply do no test against it.
So can be very well, just that your SBO SlackBuild to not be compatible with your beloved SlackwareARM, specially that limited armv6l architecture.
Last edited by Darth Vader; 04-20-2018 at 10:16 AM.
I remember our ARM Doctor drmozes instructed how to modify the SlackBuilds in order to compile properly on ARM in a post (can't find it ... sorry).
Try modifying the webkitgtk.SlackBuild:
- in the $ARCH checking section:
Code:
else
SLKCFLAGS="-O2 -march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi=soft"
LIBDIRSUFFIX=""
fi
I didnt manage to complie webkit even with your advices/sugestions for $ARCH (i tried armv6zk, armv5te).
Too bad, because this is required package to complie Midori browser.
Have a look on this old bug report, might be useful to try: "manually disable LLInt by passing DEFINES+=ENABLE_LLINT=0 to qmake" https://bugreports.qt.io/browse/QTBUG-35681
Hi Abga, thank you for this information.
Though, I need here little bit of your help here.
"manually disable LLInt by passing DEFINES+=ENABLE_LLINT=0 to qmake"
I understand that:
I should edit makefile OR config file for makefile in webkitgtk-2.4.9.
--- OR ---
I should edit makefile OR config file for makefile in Qt and recomplie Qt.
Basically, you should try to disable the LLINT usage/build in the makefile of webkigtk-2-4.9, because that's where your compilation is failing.
I had a short look at the configure script of the of webkigtk-2-4.9 package and there might be other easier ways to achieve that. Edit the slackbuild, go in the ./configure section and add after "--disable-static " the following (first try only the first, then add the second, finally all 3):
Some other notes:
- your binutils version on Slackware ARM should be 2.26.xxx, that's in case you've updated your system, and according to the QT bugtrack link, that version should be OK for LLINT
- I'm not sure about the performance impact that you'll get when disabling the JIT/optimizations in the build. Have a look what it's all about (sorry - it was TL;DR for me): https://webkit.org/blog/3362/introdu...ebkit-ftl-jit/
- there is assembler code in the source files of LLINT and "generic" ARM together with ARMv7 is mentioned in the comments: https://github.com/WebKit/webkit/tre...riptCore/llint
- try to use the latest code, either adapt the SlackBuild or do some dirty work, pack it into the webkitgtk-2.4.9.tar.xz (renaming also the source folder to match) and feed it to the SlackBuild: https://webkit.org/getting-the-code/...g-out-with-git
- last but not least, not sure what Raspberry Pi you're using (not detailed in your first post), but if you use an ARMv7/ARMv8 (Pi2/Pi3), then you could load Slackware ARM -current on it and try the compilation again without disabling anything.
Hi Abga, thank you very much for this input.
I have added "--disable-jit" and that let going/compiling webkit for more than 24h on my Raspberry. I had to stop it and once have a little bit more time, I will set qemu environment to finish it.
This is Raspberry PI model B.
I forgot to warn you that it'll take ages to compile the webkigtk. While looking after ways to disable the LLINT compilation on the Internet I remember reading some reports about a 40-50 hours compilation time.
You have a Pi 1 Model B (discontinued) that has a BCM2835 single core armv6 CPU, BCM2708 is the family/generic name of which BCM2835 belongs to https://www.adafruit.com/product/998
You have a Pi 1 Model B (discontinued) that has a BCM2835 single core armv6 CPU, BCM2708 is the family/generic name of which BCM2835 belongs to https://www.adafruit.com/product/998
As far as manufacturing goes, it is relatively expensive to halt a modern production line and reconfigure it for batches of older models (i.e. the Raspberry Pi 1). Apparently, it's only done when there are enough orders to make it worthwhile. So, it's not officially discontinued, but production of the RPi 1 is only done when consumer demand justifies it.
Certain distributers may list the RPi 1 device as 'discontinued' but are only referring to their own stock. I can't find any official statement which supports your claim(s).
Please ignore Penthux's off-topic and rather confusing reply. Off-topic because it has nothing to do with your reported problem, confusing because he's referring to a reseller (provided link) that offers Raspberry Pi 1 Model B+ boards and not Raspberry Pi 1 Model B, the Pi 1 Model B+ already replaced the Pi 1 Model B back in 2014.
On topic, you have an armv6 CPU and you cannot load Slackware ARM -current on it - last point in my post #8
Please ignore Penthux's off-topic and rather confusing reply. Off-topic because it has nothing to do with your reported problem, confusing because he's referring to a reseller (provided link) that offers Raspberry Pi 1 Model B+ boards and not Raspberry Pi 1 Model B, the Pi 1 Model B+ already replaced the Pi 1 Model B back in 2014.
On topic, you have an armv6 CPU and you cannot load Slackware ARM -current on it - last point in my post #8
OK. Let's spilt hairs over versions of an ARM device which is basically the same except one has 40 GPIO pins instead of 26 GPIO pins and 4 USB ports instead of 2 USB ports. Which for this issue doesn't matter at all. I'm sure there's a few other differences which you would argue that it makes a difference with regards to Slackware ARM. However, it doesn't. The point is no version of the Raspberry Pi (at this moment in time) has been officially discontinued. I dare say if there was enough demand for the Raspberry Pi model B (256MB) then there'd be a production run for it.
The Raspberry Pi model B (256MB/512MB RAM), Raspberry Pi model B+, Raspberry Pi model A, Raspberry Pi model A+, Raspberry Pi Zero and Raspberry Pi Zero W, all use the same system-on-chip; Broadcom BCM2708 700MHz ARM11 ARM1176JZF-S core (ARMv6).
Slackware ARM release history dictates that Slackware ARM -current has a minimum requirement of ARMv7-a architecture and cannot be installed on a Raspberry Pi 1 (any version/revision) which features ARMv6 architecture. Slackware ARM -current can only be installed on a Raspberry Pi 2 and Raspberry Pi 3.
Hey, I just want to let know that hint from Abga (post #8) worked to me (many thanks Abga btw).
This is modified "configure" part in webkitgtk.SlackBuild:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.