AMule Project FAQ - User contributions [en]

IPFilter

2011-04-15T17:51:15Z

Arichy: /* IP Filter - URLs for Auto-update at startup */ http://emulepawcio.sourceforge.net/ipfilter.dat is _not_ updated monthly

<center>'''English''' | [[IP_Filter-de|Deutsch]]</center>

== Description ==
The [[IP address|IP]] Filter blocks traffic from/to IPs and ranges of [[IP address|IP]]s with our [[client]]. This means that those [[IP address|IP]]s which get blocked will not be able neither to upload to us nor to download from us.

This filter is read from [[ipfilter.dat_file|''~/.aMule/ipfilter.dat'']] and ~/.aMule/ipfilter_static.dat. The content of these files describes the valid and blocked [[IP address|IP]] ranges.

== [[ipfilter.dat file]] ==
The information and details about the [[ipfilter.dat file]] can be found [[ipfilter.dat file|here]].

== Using the [[IP address|IP]] Filter in [[aMule]] ==
The ''Access level'' of the [[IP address|IP]] filter is selected in [[aMule]] through "Preferences" -> "Security" -> "IP Filtering" -> "Filtering level" (in [[aMule]] versions up to 2.0.0-rc8 it is under "Server", instead of "Security").

'''NOTE:''' [[aMule]]'s ''ipfilter.dat'' file is 100% compatible with [[eMule]]'s.

== Using an external [[ipfilter.dat file]] ==

aMule by default uses ~/.aMule/ipfilter.dat for IP filtering. If you enable 'Use system-wide ipfilter.dat if available', it will look for a /usr/share/amule/ipfilter.dat file if loading the local ipfilter.dat fails. This system-wide ipfilter.dat can then be kept up-to-date by another method  so that aMule doesn't have to download a large file every time it starts.

The above paths assume a linux-like system.

This option is located through "Preferences" -> "Security" and is disabled by default in the latest stable 2.2.2 build.

== [[IP address|IP]] Filter sources ==
=== IP Filter - URLs for Auto-update at startup ===
Insert the URL under "Preferences" -> "Security" -> "IP filtering" -> "URL:"

* http://emulepawcio.sourceforge.net/ipfilter.dat (on 2011-04-15 this file was from 2010-08-23)

These lists do not seem to work:

* http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack's normal ipfilter.dat])

* http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ ([http://www.bluetack.co.uk/modules.php?name=FAQ&myfaq=yes&id_cat=6&categories=Blacklists+FAQ Bluetack's paranoid ipfilter.dat])

=== IP Filter sites ===
You can insert the lists from these sites either manually or with a script. Or you can use seperate [[IP address|IP]]-blocking software like Protowall from [http://bluetack.co.uk Bluetack], PeerGuardian from [http://phoenixlabs.org Phoenixlabs] or [http://moblock.berlios.de moblock].

The [http://test.blocklist.org lists] from [http://phoenixlabs.org Phoenixlabs] (formerly known as Methlabs) are still under development. They use the lists from [http://bluetack.co.uk Bluetack] instead.

http://bluetack.co.uk/config/sources.txt (If you follow this link then download the lists as *.gz or *.zip instead of *.txt in order to save Bluetack's bandwith!)

http://emulepawcio.sourceforge.net/nieuwe_site/ipfilter_fake_list.html

== Hard coded [[IP address|IP]] filter in [[aMule]] ==
[[aMule]] has some ranges of [[IP address|IP]]s which it filters by default following the [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330] document. These ranges are:

Address Block Present Use Reference
----------------------------------------------------------------------
"0.0.0.0/8", // "This" Network [RFC1700, page 4]
"10.0.0.0/8", // Private-Use Networks [RFC1918]
"14.0.0.0/8", // Public-Data Networks [RFC1700, page 181]
"24.0.0.0/8", // Cable Television Networks --
"39.0.0.0/8", // Reserved but subject
// to allocation [RFC1797]
"127.0.0.0/8", // Loopback [RFC1700, page 5]
"128.0.0.0/16", // Reserved but subject
// to allocation --
"169.254.0.0/16", // Link Local --
"172.16.0.0/12", // Private-Use Networks [RFC1918]
"191.255.0.0/16", // Reserved but subject
// to allocation --
"192.0.0.0/24", // Reserved but subject
// to allocation --
"192.0.2.0/24", // Test-Net
"192.88.99.0/24", // 6to4 Relay Anycast [RFC3068]
"192.168.0.0/16", // Private-Use Networks [RFC1918]
"198.18.0.0/15", // Network Interconnect
// Device Benchmark Testing [RFC2544]
"223.255.255.0/24",// Reserved but subject
// to allocation --
"224.0.0.0/4", // Multicast [RFC3171]
"240.0.0.0/4" // Reserved for Future Use [RFC1700, page 4]

However, you can un-filter these ranges of [http://www.faqs.org/rfcs/rfc791.html IP]s by unchecking "Preferences"->"Security"->"IP-filtering"->"Always filter bad IPs" (on [[aMule]] versions up to 2.0.0-rc8, this option can be found in "Preferences"->"Server"->"Always filter bad IPs").

HowTo compile on Mac-de

2007-08-25T10:42:45Z

Arichy: typo

<center>[[HowTo_compile_on_Mac|English]] | '''Deutsch'''</center>

Wie bekomme und installiere ich [[aMule]] auf [http://www.apple.com/macosx/ Apple Mac OS X]?

# Du kannst einfach das fertige Programm herunterladen (Binärveröffentlichung) oder
# Du kompilierst es aus einer [[aMule CVS|CVS-Entwicklerversion]].

''Die Vorgängerversion dieser Anleitung, die [[aMule]] 2.0.0rc8 und früher behandelt findest du [[HowTo_compile_on_Mac_v200rc8|hier (englisch)]].''

== Binärveröffentlichungen ==

Wenn du dich nicht mit kompilieren und installieren all dieser Werkzeuge und Quelltexte rumärgern willst, nimm einfach eins der vorkompilierten [[aMule]] Programme. Die offizielle Veröffentlichung wird als 'stabil' betrachtet, aber alle jetzigen und späteren Versionen werden aus den Quelltexten kompiliert, um mehr Menschen die Möglichkeit zu geben neue Funktionen zu testen.

# Aktuelle stabile Veröffentlichung: [http://www.amule.org/files/files.php?cat=30 aMule-2.1.3-Mac]
# Ab und zu kompilierte Entwicklerversion: [http://forum.amule.org/index.php?topic=5051.0 aMule-Forum]

Um das heruntergeladene Programm zu installieren musst du einfach das aMule in einem Ordner deiner Wahl (z.B. ''/Applications'').

Um aMule zu starten, doppelklicke auf das Programmsymbol.

'''Bemerkung:''' Du solltest auch den [[Mac specific usage]] Artikel lesen.

== Aus den Quelltexten kompilieren ==

Kompilieren erlaubt dir aussagekräftigere Fehlermeldungen zu verfassen, da du die [[aMule CVS|CVS-Entwicklerversion]] des jeweiligen Tages verwenden kannst.

Zum kompilieren von [[aMule]] aus den Quelltexten benötigst du ein paar Entwicklungswerkzeuge, die [[wxWidgets]] Bibliothek und den [http://dl.amule.org aMule-Quelltext].

=== Quelltexte und Entwicklungswerkzeuge beziehen ===

==== [http://developer.apple.com/tools/xcode Xcode] ====

[http://developer.apple.com/tools/xcode Xcode] ist [http://www.apple.com Apple]'s Entwicklungsumgebung. Diese brauchen wir für den [http://gcc.gnu.org GCC] compiler.
Du brauchst mindestens Version 2.1 von Xcode, eine aktuellere Version ist vorzuziehen. Xcode ist auf der OS X 10.4 DVD enthalten, aber frühe Versionen von 10.4 wurden mit Xcode 2.0 ausgeliefert, also musst du überprüfen ob die Version auf der DVD mindestens 2.1 ist.
Möglicherweise hast du [http://developer.apple.com/tools/xcode Xcode] auf CD/DVD, z.B. ist es auf der [http://www.apple.com/macosx/ OS X] 10.4 DVD.

Andernfalls kannst du es von [http://www.apple.com/de/ Apple] herunterladen, du musst aber vorher einen kostenlosen Entwickler-Account registrieren. Dieses gibt es nur auf Englisch

# XCode herunterladen von http://developer.apple.com/tools/download
# "Member Site"->"Log In"->"Download Software"->"Developer Tools"->"Download Xcode Tools last release">"Install"

==== [http://www.macports.org MacPorts] (früher bekannt als DarwinPorts) ====

[http://www.macports.org MacPorts] ist ein freier Installer für freie Software die auf [http://macos.apple.com Mac OS X] portiert wurde. aMule benötigt einige dieser Programme um kompiliert werden zu können. Alternativ kannst du auch [http://fink.sourceforge.net Fink] benutzen um diese Werkzeuge zu installieren, oder die Installation komplett von Hand vornehmen.

# Lade die aktuelle Version von [http://www.macports.org MacPorts] herunter
# Lese die [http://trac.macosforge.org/projects/macports/wiki MacPorts' Dokumentation] um zu erfahren wie man mit [http://www.macports.org MacPorts] Programme installieren kann.

Die Werkzeuge die du installieren musst sind:
# automake
# flex
# gettext (Wird nur benötigt wenn du eine andere Sprache als Englisch verwenden willst)
# libpng

==== [[wxWidgets|wxMac]] ====

[[wxWidgets|wxMac]] ist die [http://macos.apple.com Mac OS X] Portierung der [[wxWidgets]] Bibliothek. Diese Bibliothek wird benutzt um [[aMule]] 'multi-platform' werden zu lassen.

# Lade die Quelltexte herunter von: http://www.wxwidgets.org/downloads/ (Source Archives: wxMac)
# Entpacke das Archiv (einfach darauf doppelklicken)

Oder nimm die aktuelle [[wx-cvs|WX-Entwicklerversion]]. Achtung: [[wxMac]] [[wx-cvs|WX-CVS]] ist häfig in schlechtem Zustand (z.B. musst du die vswprintf Implementation die wx benutzt ändern, siehe [http://forum.amule.org/index.php?topic=9915.msg58058#msg58058 hier] für mehr Details).

bash: cd ~/Desktop
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets login
Note: password is 'anoncvs'
bash: cvs -d :pserver:anoncvs@cvs.wxwidgets.org:/pack/cvsroots/wxwidgets checkout wxMac

==== [http://www.amule.org aMule selbst] ====

# Lade die aktuellste [[aMule CVS|CVS-Entwicklerversion]] herunter: [http://www.hirnriss.net/?area=cvs aMule CVS]
# Entpacke das Archiv (einfach darauf doppelklicken)

=== Quelltexte kompilieren ===

Paltziere das ''amule''-Verzeichnis und das ''wxMac''-Verzeichnis am selben Ort, z.B. auf dem Desktop (wenn du einen anderen Ort wählst, achte darauf, dass der Pfad keine Leerzeichen enthält, da es sonst zu "Datei nicht gefunden"-Fehlern bei [[wxMac]] kommen kann).

==== [[wxMac]] Kompilieren====

Dieser Schritt wird nur einmal benötigt, und muss für spätere Versionen von [[aMule CVS]] nicht wiederholt werden.

Alles nachfolgende geht davon aus, das du die Verzeichnisse auf dem Desktop platziert hast.
''cd'' in das ''wxMac'' Verzeichnis, ''configure'' und ''make'':

bash: cd ~/Desktop/wxMac-2.8.4/build
bash: ../configure --disable-shared --enable-unicode --enable-debug --enable-debug_gdb
bash: make

'''Anmerkung:''' Der zweite Befehl oben sorgt dafür, dass wxMac mit Debug-Informationen kompiliert wird. Diese Informationen erlauben es dir einen hilfreichen stacktrace zu für die [[aMule devs|aMule Entwickler]] zu erstellen, falls [[aMule]] abstürzen sollte. Falls du keine Debugversion möchtest, benutze "--disable-debug --disable-debug_gdb".

'''Anmerkung:''' Falls du ein [http://en.wikipedia.org/wiki/Universal_binary Universal Binary] von aMule kompilieren willst (d.h. ein aMule Version die auf PowerPC und Intel basierenden Macs läuft), kannst du "--enable-universal_binary" als Parameter an das Ende des zweiten Befehls anhängen. Wenn du diesen Parameter weglässt werden wxMac und aMule nur für deine Architektur kompiliert.

'''Anmerkung:''' Der make Befehl kann bis zu 45 Minuten dauern, abhängig von deinem Prozessor und den gewählten Parametern.

==== [[aMule]] kompilieren ====

Jetzt ''cd'' in das ''amule''-Verzeichnis, ''./configure'' und ''make'':

'''Anmerkung:''' Die 4 Zeilen für ''./configure'' kannst du in einem Rutsch kopieren.

bash: cd ~/Desktop/amule-cvs
bash: ./configure --disable-systray --disable-gtk --enable-embedded_crypto \
--with-wx-config=../wxMac-2.8.4/build/wx-config \
--enable-cas --enable-webserver --enable-amulecmd \
--enable-debug --disable-optimize

bash: make
bash: ./src/utils/scripts/mac_packager

'''Anmerkung:''' Wenn du aMule nicht mit Debuginformationen kompilieren willst (siehe oben) solltest du "--disable-debug --enable-optimize" im configure Schritt verwenden.

'''Anmerkung:''' Um aMule als Universal Binary zu kompilieren (siehe oben) musst du folgendes an den configure Befehl anhängen:
--disable-dependency-tracking \
CFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk" \
CXXFLAGS="-arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk"

==== [[aMule]] starten ====
Wenn das mac_packager Script fertig ist, kannst du das aMule Programm aus dem amule-cvs Verzeichnis überall hin auf deiner Festplatte verschieben.

HowTo Compile In Debian/Ubuntu

2007-05-01T08:38:42Z

Arichy: algorith to see what developement packages are needed

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Info: What aMule release needs what wxwidgets release?==
* Debian Etch includes aMule 2.1.3 and wxwidgets 2.6.3

* aMule 2.1 needs wxwidgets 2.6. You cannot compile it with newer versions of wxwidgets.
* aMule 2.2 needs wxwidgets 2.8. You cannot compile it with older versions of wxwidgets.

==What developement packages do I need for compiling?==
Hint: You don't need to read this if You use Debian Etch.

To find out, what Debian developement packages You need to compile program ''p'', look if there is a package of ''p'' in Your Debian repository with <tt>apt-cache search ''p''</tt>. If there is, type <tt>apt-cache showsrc ''packagename''</tt>
In the output, ''Build-Depends:'' lists the developement packages that You need to compile the ''packagename'' source code. With some luck, also newer sources of program ''p'' can be compiled with these developement packages.

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: <tt># apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev</tt>
# Download current aMule stable release source code tar ball from <tt>http://www.amule.org</tt> (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# <tt>$ tar xvjf aMule-''version''.tar.bz2</tt>
# <tt>$ cd aMule-''version''</tt>
# To have a look what features of aMule You can enable or disable: <tt>$ ./configure --help</tt>
# You should be right with <tt>$ ./configure --disable-debug --enable-optimize</tt>
# <tt>$ make</tt>
# <tt># make install</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T13:49:30Z

Arichy: =Info: What aMule release needs what wxwidgets release?= more info

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Info: What aMule release needs what wxwidgets release?==
* Debian Etch includes aMule 2.1.3 and wxwidgets 2.6.3

* aMule 2.1 needs wxwidgets 2.6. You cannot compile it with newer versions of wxwidgets.
* aMule 2.2 needs wxwidgets 2.8. You cannot compile it with older versions of wxwidgets.

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: <tt># apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev</tt>
# Download current aMule stable release source code tar ball from <tt>http://www.amule.org</tt> (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# <tt>$ tar xvjf aMule-''version''.tar.bz2</tt>
# <tt>$ cd aMule-''version''</tt>
# To have a look what features of aMule You can enable or disable: <tt>$ ./configure --help</tt>
# You should be right with <tt>$ ./configure --disable-debug --enable-optimize</tt>
# <tt>$ make</tt>
# <tt># make install</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T13:41:31Z

Arichy: =Info: What aMule release needs what wxwidgets release?= Debian Etch includes wxwidgets 2.6

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Info: What aMule release needs what wxwidgets release?==
* Debian Etch includes wxwidgets 2.6

* aMule 2.1 needs wxwidgets 2.6. You cannot compile it with newer versions of wxwidgets.
* aMule 2.2 needs wxwidgets 2.8. You cannot compile it with older versions of wxwidgets.

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: <tt># apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev</tt>
# Download current aMule stable release source code tar ball from <tt>http://www.amule.org</tt> (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# <tt>$ tar xvjf aMule-''version''.tar.bz2</tt>
# <tt>$ cd aMule-''version''</tt>
# To have a look what features of aMule You can enable or disable: <tt>$ ./configure --help</tt>
# You should be right with <tt>$ ./configure --disable-debug --enable-optimize</tt>
# <tt>$ make</tt>
# <tt># make install</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T13:36:59Z

Arichy: =Info: What aMule release needs what wxwidgets release?= more general

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Info: What aMule release needs what wxwidgets release?==
* aMule 2.1 needs wxwidgets 2.6. You cannot compile it with newer versions of wxwidgets.
* aMule 2.2 needs wxwidgets 2.8. You cannot compile it with older versions of wxwidgets.

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: <tt># apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev</tt>
# Download current aMule stable release source code tar ball from <tt>http://www.amule.org</tt> (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# <tt>$ tar xvjf aMule-''version''.tar.bz2</tt>
# <tt>$ cd aMule-''version''</tt>
# To have a look what features of aMule You can enable or disable: <tt>$ ./configure --help</tt>
# You should be right with <tt>$ ./configure --disable-debug --enable-optimize</tt>
# <tt>$ make</tt>
# <tt># make install</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T13:32:49Z

Arichy: Info: What aMule release needs what wxwidgets release?

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Info: What aMule release needs what wxwidgets release?==
* aMule 2.1 needs wxwidgets 2.6. You cannot compile it with wxwidgets 2.8.
* aMule 2.2 needs wxwidgets 2.8. You cannot compile it with wxwidgets 2.6.

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: <tt># apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev</tt>
# Download current aMule stable release source code tar ball from <tt>http://www.amule.org</tt> (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# <tt>$ tar xvjf aMule-''version''.tar.bz2</tt>
# <tt>$ cd aMule-''version''</tt>
# To have a look what features of aMule You can enable or disable: <tt>$ ./configure --help</tt>
# You should be right with <tt>$ ./configure --disable-debug --enable-optimize</tt>
# <tt>$ make</tt>
# <tt># make install</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T13:23:18Z

Arichy: =Compiling and installing aMule= legende

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: <tt># apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev</tt>
# Download current aMule stable release source code tar ball from <tt>http://www.amule.org</tt> (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# <tt>$ tar xvjf aMule-''version''.tar.bz2</tt>
# <tt>$ cd aMule-''version''</tt>
# To have a look what features of aMule You can enable or disable: <tt>$ ./configure --help</tt>
# You should be right with <tt>$ ./configure --disable-debug --enable-optimize</tt>
# <tt>$ make</tt>
# <tt># make install</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T13:21:32Z

Arichy: =Preparing: Compiling and installing wxwidgets= legende

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

$ = command executed with normal user account 
<nowiki>#</nowiki> = command executed with root account

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: <tt># apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev</tt>
# Download current aMule stable release source code tar ball from <tt>http://www.amule.org</tt> (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# <tt>$ tar xvjf aMule-''version''.tar.bz2</tt>
# <tt>$ cd aMule-''version''</tt>
# To have a look what features of aMule You can enable or disable: <tt>$ ./configure --help</tt>
# You should be right with <tt>$ ./configure --disable-debug --enable-optimize</tt>
# <tt>$ make</tt>
# <tt># make install</tt>

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:57:24Z

Arichy: =Compiling and installing aMule=

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: <tt># apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev</tt>
# Download current aMule stable release source code tar ball from <tt>http://www.amule.org</tt> (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# <tt>$ tar xvjf aMule-''version''.tar.bz2</tt>
# <tt>$ cd aMule-''version''</tt>
# To have a look what features of aMule You can enable or disable: <tt>$ ./configure --help</tt>
# You should be right with <tt>$ ./configure --disable-debug --enable-optimize</tt>
# <tt>$ make</tt>
# <tt># make install</tt>

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:54:27Z

Arichy: =Preparing: Compiling and installing wxwidgets= tt-font for code

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: <tt># apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central</tt>
# Download current wxwidgets wxGTK stable release source code tar ball from <tt>http://www.wxwidgets.org/downloads/</tt>
# <tt>$ tar xvzf wxgtk-''version''.tar.gz</tt>
# <tt>$ cd wxGTK-''version''</tt>
# <tt>$ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise</tt>
# <tt>$ make</tt>
# <tt># make install</tt>
# <tt># ldconfig</tt>

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: # apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# To have a look what features of aMule You can enable or disable: $ ./configure --help
# You should be right with $ ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:50:46Z

Arichy: =Preparing: Compiling and installing wxwidgets= ldconfig added

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: # apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central
# Download current wxwidgets wxGTK stable release source code tar ball from http://www.wxwidgets.org/downloads/
# $ tar xvzf wxgtk-<version>.tar.gz
# $ cd wxGTK-<version>
# $ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise
# $ make
# # make install
# # ldconfig

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: # apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# To have a look what features of aMule You can enable or disable: $ ./configure --help
# You should be right with $ ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:50:02Z

Arichy: See also general Compilation Installation

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

See also general [[Compilation Installation]]

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: # apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central
# Download current wxwidgets wxGTK stable release source code tar ball from http://www.wxwidgets.org/downloads/
# $ tar xvzf wxgtk-<version>.tar.gz
# $ cd wxGTK-<version>
# $ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise
# $ make
# # make install

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: # apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# To have a look what features of aMule You can enable or disable: $ ./configure --help
# You should be right with $ ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:29:33Z

Arichy: =Compiling and installing aMule= needed libraries added

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: # apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central
# Download current wxwidgets wxGTK stable release source code tar ball from http://www.wxwidgets.org/downloads/
# $ tar xvzf wxgtk-<version>.tar.gz
# $ cd wxGTK-<version>
# $ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise
# $ make
# # make install

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# On Debian Etch: # apt-get install autotools-dev quilt libglib2.0-dev zlib1g-dev libgd2-xpm-dev libreadline5-dev libcrypto++-dev
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# To have a look what features of aMule You can enable or disable: $ ./configure --help
# You should be right with $ ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:27:22Z

Arichy: =Preparing: Compiling and installing wxwidgets= need libraries added

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# On Debian Etch: # apt-get install flex bison gettext libgtk2.0-dev python-all-dev zlib1g-dev libjpeg62-dev libpng12-dev libtiff4-dev libgl-dev libglu-dev libesd0-dev libgnomeprintui2.2-dev python-central
# Download current wxwidgets wxGTK stable release source code tar ball from http://www.wxwidgets.org/downloads/
# $ tar xvzf wxgtk-<version>.tar.gz
# $ cd wxGTK-<version>
# $ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise
# $ make
# # make install

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# To have a look what features of aMule You can enable or disable: $ ./configure --help
# You should be right with $ ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:18:22Z

Arichy: =Compiling and installing aMule= little correcture

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# Download current wxwidgets wxGTK stable release source code tar ball from http://www.wxwidgets.org/downloads/
# $ tar xvzf wxgtk-<version>.tar.gz
# $ cd wxGTK-<version>
# $ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise
# $ make
# # make install

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# To have a look what features of aMule You can enable or disable: $ ./configure --help
# You should be right with $ ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:15:00Z

Arichy: =Preparing: Compiling and installing wxwidgets= typo

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# Download current wxwidgets wxGTK stable release source code tar ball from http://www.wxwidgets.org/downloads/
# $ tar xvzf wxgtk-<version>.tar.gz
# $ cd wxGTK-<version>
# $ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise
# $ make
# # make install

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# $ ./configure --help (to have a look what features of aMule You can enable or disable)
# $ You should be right with ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:13:29Z

Arichy: =Preparing: Compiling and installing wxwidgets=

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How to uninstall wxWidgets]] and [[Check if wx is installed twice]])
# Download current wxwidgets wxGTK stable release source code tar ball from http://www.wxwidgets.org/downloads/
# $ tar xvzf <wxgtk-<version>.tar.gz>
# $ cd wxGTK-<version>
# $ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise
# $ make
# # make install

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# $ ./configure --help (to have a look what features of aMule You can enable or disable)
# $ You should be right with ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2007-04-28T10:12:42Z

Arichy: more general and easy algorithm, better structure

<center>'''English''' | [[HowTo_Compile_In_Debian-es|Español]]</center>

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

== Are you sure you want to compile? ==

If not, (which is pretty common) decide if you want the [[aMule]] stable release or the [[aMule CVS]] release.

=== [[aMule]] stable release ===

'''These packages are for Debian 3.1 Sarge only!'''

You can just install latest stable [[aMule]] version through [http://packages.debian.org deb]s adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://amule-debian.dyndns.org/ debian/

Now run <code>apt-get update && apt-get install amule</code>

Packages in this repository:
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

'''NOTES:'''
* If [[aMule]] exits with error message complaining about being unable to open libbfd-2.15.so this usually means you are NOT running Debian Sarge. Don't start making symlinks or doing other workarounds, they can quite easily bork your whole system.

* http://dude.gemil.de is deprecated. http://amule-debian.dyndns.org is (for now) just a redirect, but this might change in the future (if the repository has to move due to traffic limitations).

=== [[aMule CVS]] release ===

'''These packages are for Debian testing aka Etch only!'''

You can also get the latest [[aMule CVS]] through debs adding the following line into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule

packages are GPG sighned, so follow this steps:
''gpg --keyserver wwwkeys.eu.pgp.net --recv 50D0AE60''
''gpg -a --export 50D0AE60 > /tmp/key''
''apt-key add /tmp/key'' (requires superuser privileges)

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:

'''[[aMule CVS]]'''
*amule
*amule-utils
*amule-utils-gui
*amule-ed2k
*amule-cas
*amule-wxcas
*amule-xas
*amule-common
*amule-theme-default
*amule-theme-php-default
*amule-theme-chicane
*amuleweb
*amule-remote-gui
*amule-daemon
*amule-alc
*amule-alcc
*amule-cmd
*amule-i18n-ar
*amule-i18n-bg
*amule-i18n-ca
*amule-i18n-da
*amule-i18n-de
*amule-i18n-en-gb
*amule-i18n-en-us
*amule-i18n-es
*amule-i18n-es-mx
*amule-i18n-et-ee
*amule-i18n-eu
*amule-i18n-fi
*amule-i18n-fr
*amule-i18n-gl
*amule-i18n-hr
*amule-i18n-hu
*amule-i18n-it-ch
*amule-i18n-it
*amule-i18n-ko-kr
*amule-i18n-nl
*amule-i18n-pl
*amule-i18n-pt-br
*amule-i18n-pt-pt
*amule-i18n-ru
*amule-i18n-sl
*amule-i18n-zh-cn
*amule-i18n-zh-tw

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

For [[aMule CVS]]: ''apt-get install amuleweb''

For [[aMule]] stable: ''apt-get install amule-console-utils''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

==Preparing: Compiling and installing wxwidgets==
This algorithm works for Debian Sarge and Etch.

To compile aMule, You need to have a current version of [[wxWidgets]] installed. To achieve that:
# Uninstall every possibly previously installed wxwidgets stuff (see [[How_to_uninstall_wxWidgets]] and [[Check_if_wx_is_installed_twice]])
# Download current wxwidgets wxGTK stable release source code tar ball from http://www.wxwidgets.org/downloads/
# $ tar xvzf <wxgtk-<version>.tar.gz>
# $ cd wxGTK-<version>
# $ ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise
# $ make
# # make install

==Compiling and installing aMule==
Now that You have installed current wxGTK, go on to compile aMule:
# Download current aMule stable release source code tar ball from http://www.amule.org (note: aMule 2.1.3 can only be compiled with wxwidgets 2.6. If You have wxwidgets 2.8 installed, You have to use a newer version of aMule (if there is no newer release, use aMule SVN).
# $ tar xvjf aMule-<version>.tar.bz2
# $ cd aMule-<version>
# $ ./configure --help (to have a look what features of aMule You can enable or disable)
# $ You should be right with ./configure --disable-debug --enable-optimize
# $ make
# # make install

That's it! Now You can start aMule with commando "amule".

== Compiling on Debian 3.0 aka Woody ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be updated to Sarge doing apt-get dist-upgrade.

'''''Note 3:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 7:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 2.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 8:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

=== Using [[wxWidgets]] 2.6 ===

[[Debian|Etch]] and [[Debian|Sid]] users can use wxWidgets 2.6 instead of wxWidgets 2.4 (Woody and Sarge users, forget about it. Go straight to the next chapter of this article).

To use wxWidgets 2.6 instead of 2.4, just replace in all the above commands the terms ''libwxbase2.4-dev'' and ''libwxgtk2.4-dev'' with ''libwxbase2.6-dev'' and libwxgtk2.6-dev'' respectively.

Whether or not you should use wx 2.6 insetad of wx 2.4 is up to you. It has both advantages and disadvantages. Anyway, in most cases, you will be grateful to use wx 2.6, so it is recommended.

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 9:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 10:''' Please take a look at the [[configure|configure article]].''

'''''Note 11:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 12:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.