Building Amarok on one machine, running it on another ...

Bernd Wechner bwechner at yahoo.com
Tue Mar 1 08:19:39 UTC 2016


Forgive me if this should be a naive newb question. By all means point 
me away to better means of learning if that's appropriate. But:

1) I have Amarok building just fine from the latest source. On a well 
resourced development box inxi output):

CPU~Quad core Intel Core i7-4790 (-HT-MCP-) speed/max~3600/4000 MHz 
Kernel~3.16.0-38-generic x86_64 Up~5 days Mem~9124.3/32052.5MB 
HDD~3688.8GB(71.2% used) Procs~275 Client~Shell inxi~2.2.28

2) I am running Amarok on a leaner media server:

CPU~Dual core Intel Core i5-4250U (-HT-MCP-) speed/max~1196/2600 MHz 
Kernel~3.19.0-32-generic i686 Up~1 day Mem~1235.8/16107.5MB 
HDD~250.1GB(9.0% used) Procs~206 Client~Shell inxi~2.2.28

both are running Linux Mint 17.3 (latest release).

Here's the rub, that I don't understand:

I build on the dev box, copy the binary (amarok) to the media server and 
it won't run. Says: "cannot execute binary file: Exec format error"

To rule out any issues copying it from the one machine to the other, I 
confirmed that the files on both machines have same md5sum.

Now this binary runs on machine 1) and not 2) and yet, the amarok 
package is a binary package and so a single binary that ports across 
Linux boxes is something I presupposed to exist.

On both machines the installed package reports:

    Qt: 4.8.6
    KDE Development Platform: 4.14.2
    Amarok: 2.8.0

And yet, the md5 sum of /usr/bin/amarok is different on both machines - 
a clue that the package is choosing a different binary to install on 
each machine I guess and that I don't understand as much as I 
could/should about how .deb packages work.

Dev machine:
bernd at bigfoot ~ $ md5sum /usr/bin/amarok
8ae9338ae6f3e79e1bffb4c12d4e3eef  /usr/bin/amarok

Media server:
polyphemus at cyclops ~ $ md5sum /usr/bin/amarok
7634af456143a6bef1039c412365d1d2  /usr/bin/amarok

So I'm needing to get my head around this before I can start any 
sensible work and testing with Amarok builds. Any tips are seriously 
appreciated as they save me time ... it is not instead of researching 
actively in the docs that I post, but in parallel.

Regards,

Bernd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok-devel/attachments/20160301/e4b45569/attachment.html>


More information about the Amarok-devel mailing list