LinuxQuestions.org - aMule slackbuild falling behind

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - aMule slackbuild falling behind (https://www.linuxquestions.org/questions/slackware-arm-108/amule-slackbuild-falling-behind-4175600698/)

aMule slackbuild falling behind

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?

hi SCerovec,

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 )

while 2.3.2 builds fine on x86, on slackwarearm-current it seems to get to the end here if patched like this (latest svn snapshot)

Code:

diff -Naur aMule.orig/0001-desktop-files-GenericName.patch aMule/0001-desktop-files-GenericName.patch

--- aMule.orig/0001-desktop-files-GenericName.patch        1970-01-01 01:00:00.000000000 +0100

+++ aMule/0001-desktop-files-GenericName.patch        2017-02-26 08:15:49.000000000 +0100

@@ -0,0 +1,65 @@

+diff -Naur a/amule.desktop b/amule.desktop

+--- a/amule.desktop        2015-12-05 12:17:44.000000000 +0800

++++ b/amule.desktop        2016-01-28 17:59:27.159722045 +0800

+@@ -5,6 +5,6 @@

+ Terminal=false

+ Type=Application

+ Categories=Network;P2P;

+-Comment=A client for the eD2k network

+-Comment[fr]=Un client pour le réseau eD2k

+-Comment[tr]=eD2k ağı için istemci

++GenericName=A client for the eD2k network

++GenericName[fr]=Un client pour le réseau eD2k

++GenericName[tr]=eD2k ağı için istemci

+diff -Naur a/amulegui.desktop b/amulegui.desktop

+--- a/amulegui.desktop        2015-12-05 12:17:44.000000000 +0800

++++ b/amulegui.desktop        2016-01-28 18:00:09.484782640 +0800

+@@ -5,8 +5,8 @@

+ Terminal=false

+ Type=Application

+ Categories=Network;P2P;

+-Comment=aMule remote control

+-Comment[de]=aMule-Fernsteuerung

+-Comment[fr]=Contrôle à distance d'aMule

+-Comment[hu]=aMule távoli vezérlő

+-Comment[tr]=aMule uzaktan kumandası

++GenericName=aMule remote control

++GenericName[de]=aMule-Fernsteuerung

++GenericName[fr]=Contrôle à distance d'aMule

++GenericName[hu]=aMule távoli vezérlő

++GenericName[tr]=aMule uzaktan kumandası

+diff -Naur a/src/utils/aLinkCreator/alc.desktop b/src/utils/aLinkCreator/alc.desktop

+--- a/src/utils/aLinkCreator/alc.desktop        2015-12-05 12:17:44.000000000 +0800

++++ b/src/utils/aLinkCreator/alc.desktop        2016-01-28 17:56:59.532032109 +0800

+@@ -5,8 +5,8 @@

+ Terminal=false

+ Type=Application

+ Categories=Network;P2P;

+-Comment=aMule ed2k link creator

+-Comment[de]=ed2k-Linkersteller

+-Comment[fr]=Créateur de liens ed2k d'aMule

+-Comment[hu]=ed2k hivatkozás készítő

+-Comment[tr]=aMule için ed2k bağlantı yaratıcısı

++GenericName=aMule ed2k link creator

++GenericName[de]=ed2k-Linkersteller

++GenericName[fr]=Créateur de liens ed2k d'aMule

++GenericName[hu]=ed2k hivatkozás készítő

++GenericName[tr]=aMule için ed2k bağlantı yaratıcısı

+diff -Naur a/src/utils/wxCas/wxcas.desktop b/src/utils/wxCas/wxcas.desktop

+--- a/src/utils/wxCas/wxcas.desktop        2015-12-05 12:17:44.000000000 +0800

++++ b/src/utils/wxCas/wxcas.desktop        2016-01-28 17:58:46.434702658 +0800

+@@ -5,8 +5,8 @@

+ Terminal=false

+ Type=Application

+ Categories=Network;P2P;

+-Comment=aMule online statistics

+-Comment[de]=aMule-Onlinestatistik

+-Comment[fr]=Statistiques d'aMule en ligne

+-Comment[hu]=aMule online statisztikák

+-Comment[tr]=Çevrim içi aMule istatistikleri

++GenericName=aMule online statistics

++GenericName[de]=aMule-Onlinestatistik

++GenericName[fr]=Statistiques d'aMule en ligne

++GenericName[hu]=aMule online statisztikák

++GenericName[tr]=Çevrim içi aMule istatistikleri

+

diff -Naur aMule.orig/aMule.SlackBuild aMule/aMule.SlackBuild

--- aMule.orig/aMule.SlackBuild        2016-06-18 22:47:37.000000000 +0200

+++ aMule/aMule.SlackBuild        2017-02-28 07:11:06.867267962 +0100

@@ -5,7 +5,7 @@

 # Maintained by Ozan Türkyılmaz ozan.turkyilmaz@gmial.com

 

 PRGNAM=aMule

-VERSION=${VERSION:-2.3.1}

+VERSION=${VERSION:-r10983}

 BUILD=${BUILD:-1}

 TAG=${TAG:-_SBo}

 

@@ -31,6 +31,9 @@

 elif [ "$ARCH" = "x86_64" ]; then

  SLKCFLAGS="-O2 -fPIC"

  LIBDIRSUFFIX="64"

+elif [ "$ARCH" = "arm" ]; then

+  SLKCFLAGS="-O2 -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=hard"

+  LIBDIRSUFFIX=""

 else

  SLKCFLAGS="-O2"

  LIBDIRSUFFIX=""

@@ -122,11 +125,12 @@

  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \

  -exec chmod 644 {} \;

 

-# Fix for gcc-4.7.x

-sed -i "s|NotifyObservers|this->NotifyObservers|" src/ObservableQueue.h

+patch -p1 < $CWD/0001-desktop-files-GenericName.patch

+

+sh autogen.sh

 

 CFLAGS="$SLKCFLAGS" \

-CXXFLAGS="$SLKCFLAGS" \

+CXXFLAGS="-fPIC $SLKCFLAGS" \

 ./configure \

  --prefix=/usr \

  --libdir=/usr/lib${LIBDIRSUFFIX} \

diff -Naur aMule.orig/aMule.info aMule/aMule.info

--- aMule.orig/aMule.info        2016-06-18 22:47:37.000000000 +0200

+++ aMule/aMule.info        2017-02-28 07:12:01.687267988 +0100

@@ -1,10 +1,10 @@

 PRGNAM="aMule"

-VERSION="2.3.1"

+VERSION="r10983"

 HOMEPAGE="http://www.amule.org"

-DOWNLOAD="http://downloads.sourceforge.net/amule/aMule-2.3.1.tar.xz"

-MD5SUM="5f5707ad2073d37100409870aa5d3f93"

+DOWNLOAD="http://ponce.cc/slackware/sources/repo/aMule-r10983.tar.xz"

+MD5SUM="c2aaa1321e93a582b672d75a18bbc991"

 DOWNLOAD_x86_64=""

 MD5SUM_x86_64=""

-REQUIRES="cryptopp wxPython"

+REQUIRES="cryptopp wxGTK3"

 MAINTAINER="Ozan Türkyılmaz"

 EMAIL="ozan.turkyilmaz@gmail.com"

note that the build here (Banana Pi Pro) crashed three times before getting to the end (I had to restart it each time).

EDIT: FYI, mldonkey built fine at the first try (and has no external deps).

Nicely done, but...
How come crashes tree times until it finishes?
Isn't each Slackbuild - untar and begin from scratch?

re MLdonkey - I'll give it a shot

I need some non torrent p2p on occasion...

Quote:

Originally Posted by SCerovec (Post 5677913)

Nicely done, but...
How come crashes tree times until it finishes?
Isn't each Slackbuild - untar and begin from scratch?

It crashed here most probably because the cpu overheats.

@ponce:
somehow get an "south bridge" class heat-sink and glue it with some silicone adhesive (really any silicone type will do)?

south bridge heat-sink @ aliexpress

I had it (O-pi-PC) suddenly restart, and it was warm (hot?) at the touch, so I went ahead and had a heat-sink glued.

Just in case I continued compiling with -j 3...

The heat-restart shouldn't kick in at all, and if it does, do take steps to avoid it? I would hate to hear any of those failing any soon?

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.