SlackBuilds that work on arm/64
by slac-in-the-box from LinuxQuestions.org on (#5BA6P)
Howdy armed slackers
Although the first post of the SlackBuilds not building on -current thread never specifically mentions architecture, I assume that thread is for x86 and x86_64 architectures, and that ponce has enough to do without posts about SlackBuilds not building on slarm64-current on his thread.
In this slackware-arm forum, I see many threads troubleshooting the compilation of various third party software packages most of which already have SlackBuilds at slackbuilds.org that succeed without modification, and others that fail, but would succeed with modification, and a few that won't build at all because arm or arm64 is not supported yet.
Maybe there is already a thread for this, and if so, just point me to it; but it seems like the slackware-arm and the slarm64 community could benefit from a similar thread focused on assembling a list of SlackBuilds which had to be modified to work on arm or arm64.
Even if the modifications weren't made by the official maintainers, it would give maintainers a resource to check to see if anyone had already done some work at getting their package to build for arm/64, and they could merge such modifications into their official SlackBuilds, or redo them their own way.
The end game goal of having all third party packages that I use build with execution of one script, has been achieved for x64 thanks to sbopkg.
But the same script fails on the pinebook pro -- too many Slackbuilds not updated for arm64 yet. I want to update all my SlackBuilt packages in one shebang! The sooner the official maintainers have arm64 compliant SlackBuilds the better.
So, I'll be hacking away one package after another until this pinebook pro performs the way my 10-year old wants (runescape, minetest, and so on). Every time I successfully modify an official SlackBuild script, I'm going to post that modification to this thread with hopes of being helpful.
Cheers
Although the first post of the SlackBuilds not building on -current thread never specifically mentions architecture, I assume that thread is for x86 and x86_64 architectures, and that ponce has enough to do without posts about SlackBuilds not building on slarm64-current on his thread.
In this slackware-arm forum, I see many threads troubleshooting the compilation of various third party software packages most of which already have SlackBuilds at slackbuilds.org that succeed without modification, and others that fail, but would succeed with modification, and a few that won't build at all because arm or arm64 is not supported yet.
Maybe there is already a thread for this, and if so, just point me to it; but it seems like the slackware-arm and the slarm64 community could benefit from a similar thread focused on assembling a list of SlackBuilds which had to be modified to work on arm or arm64.
Even if the modifications weren't made by the official maintainers, it would give maintainers a resource to check to see if anyone had already done some work at getting their package to build for arm/64, and they could merge such modifications into their official SlackBuilds, or redo them their own way.
The end game goal of having all third party packages that I use build with execution of one script, has been achieved for x64 thanks to sbopkg.
But the same script fails on the pinebook pro -- too many Slackbuilds not updated for arm64 yet. I want to update all my SlackBuilt packages in one shebang! The sooner the official maintainers have arm64 compliant SlackBuilds the better.
So, I'll be hacking away one package after another until this pinebook pro performs the way my 10-year old wants (runescape, minetest, and so on). Every time I successfully modify an official SlackBuild script, I'm going to post that modification to this thread with hopes of being helpful.
Cheers