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.
This might well be for the general Slackware, but on arm we rely solely on Slackbuilds for aMule, and for x86 Slackware, there are (working) 3rd party packages at hand:
1. aMule-2.3.1 fails to run on Slackware-arm
2. aMule-2.3.1 is obsoleted by 2.3.2
3. aMule-2.3.2 fails to build with the provided Slackbuild (for 2.3.1)
Is the maintainer aware of this?
Is there any maintainer for arm?
aMule 2.3.2 builds fine here on slackware current, i586 and x86_64, it has just changed its main dependency from wxPython to wxGTK3.
for personal curiosity I'm trying a build on slackwarearm-current, but it will need some time (also because I have to build wxGTK3 too).
note that SlackBuilds.org officially support only the above x86 architectures so, AFAIK, nobody is actively maintaining for the arm architecture all of the third-party scripts that SBo provides.
another couple of things not related strictly to building this app but, IMHO, to consider are:
- a gui app for the edonkey network is not the best choice for an headless solution like the arm boards: maybe something like mldonkey (AFAIK, untested too on slackwarearm) could be a better choice (lighter and usable via a remote web interface); (EDIT: nevermind this, I forgot aMule can be built with an internal webserver)
- all of the edonkey apps completely thrash your storage, so consider that too before installing them on devices with delicate ones like usually arm boards are.
Hello ponce,
kind thanks for the info, I happen to use some svn version on ix86 here?
Do note, while able to finish building here too, the v2.3.1 amuled just crashes, after creating all the files and configs?
I'm on my way to attempt the v2.3.2 build, but had a crash on my Orange pi PC probably due to heat (from sub zero this winter, first above 12C week ).
I siliconed an tiny "south bridge" heat-sink and will give it another try...
It goes without saying that make is -j4, or bust. (and bust it was :P )
You can run a script which regularly checks /sys/class/thermal/thermal_zone*/temp (or whatever the temperature sensors path) and lower cpufreq for a period of time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.