Greetz
I very much want to install lua and luajit on my Aarch64 Slackware system in order to get both Conky and E25 installed and working for starters but I'm also trying to build a web admin interface and the simplest way seems to be conversion of existing debs or rpms,. but maybe I just need some pointers at altering Slackbuild scripts for ARM. Before I just "try stuff", what is recommended from those with experience in ARM?

Thank you, sndwvs, that got me quite a bit further but I still need to understand any helpful requirements for either building from source or converting other distro's packages. For example I also need tolua++ for conky and scim's meson build for E25. I have yet to tackle trying to build anything like Cockpit but I'm sure it will take a lot since not even rpms exist for all of Cockpit and they divide a handful of requirements up into separate packages.

Incidentally tolua++ might be especially problematic as I notice Suse's ARM rpm packages for Conky leave it out and it runs rather badly with a number of graphics "issues", especially with overlapping fonts.

ARM is not like x86 when it comes to converting packages from rpms or debs. You may end up with a lot of inconsistencies. There are some recent threads you may find interesting.

https://www.linuxquestions.org/quest...64-4175711491/
https://www.linuxquestions.org/quest...-a-4175686377/

Generally, you will not need to make many changes in the scripts on SlackBuilds.org. You can also use ponce's repository that focuses on -current build scripts. alienBOB's repository has reliable build scripts too. I suggest you use those build scripts and modify them. In most cases modifying the $ARCH and $LIBSUFFIXDIR to build on Aarch64 is all that is needed.

You can use sbopkg package manager along with it's utility, sqg, to generate queue files to pick up dependencies. Another good tool is slackrepo for large builds. Slackrepo can be confusing to configure for ARM/Aarch64.

1 members found this post helpful.

Thank you once again, mralk3, that's good info on the modifications to slackbuilds. I'm not likely to ever use sbopkg. I actively dislike and eschew automated dependency resolution.

UPDATE - That works very well! Thank you once again mralk3.

I now have Enlightenment E25 running on my RockPro64

Attached Thumbnails

 

1 members found this post helpful.

Nice! What did you need to change in the SlackBuilds to finish?

I had tried unsuccessfully to run the "enlighten-me.sh" script usually failing on scim. This seemed odd to me since I tried installing scim separately and that worked but the enlighten-me script still failed.

On your advice, mralk3, I simply went into each component's directory and edited each foo.Slackbuild to include as you noted

It took a very long time and possibly unnecessarily since somehow even after a hard set with ntpdate and localtime, out of the blue it reverted to 2013 and complained Makefile was in the future. It was taking so long I took a chance and reset time. It finished, immediately had Enlightenment in the SDDM Login/Chooser and launched without a single glitch. Runs very nicely and uses almost half the RAM of Plasma.

E25 has considerable influence to run well with a touchscreen in full GUI Desktop but has the choice to run as a Tiling Manager. which is highly configurable and very comfortable and potent. If I can figure out how EDP works and can find a matching display and cable, I may get to play around with some touch enabled. It is my understanding that there's a lot more to it than just the difference between 30pin and 42pin but I have yet to find a manufacturer specific pinout. I have a non-touch TFT from a T60 Thinkpad I'm not using that'd be fun to get up on the RockPro.