AMule Project FAQ - User contributions [en]

AMule devs

2008-03-20T02:50:24Z

Thedude0001: /* Becoming a Developer */

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

== The [[aMule]] Project ==
The aMule project is led by a bunch of people (tho some rumours say they are monkeys) who toil away in front of their computers, so that you can enjoy a stable and featureful P2P client.
This page is about them.

== The Team ==
These are the people who work on aMule:

=== Developers ===
* [[User:deltaHF|deltaHF]]: Webmaster, Admin and from-time-to-time-coder ;)
* [[User:falso|falso]]: [[CAS]] coder.
* [[User:GonoszTopi|GonoszTopi]]: [[External Connections]] developer.
* [[User:Hetfield|Hetfield]]: Ex-Admin, pretty-no-free-time coder.
* [[User:Jacobo221|Jacobo221]]: Our man-for-all
* [[User:ken|Ken]]: The big [http://www.apple.com/macosx Mac] guy.
* [[User:lfroen|lfroen]]: Core/GUI dedicated guy.
* [[User:Phoenix|Phoenix]]: Code janitor junior and Admin.
* [[User:thepolish|thepolish]]: [[aMule]] [[FAQ_utils|tools]] coder.
* [[User:Xaignar|Xaignar]]: Code janitor extraordinaire!

=== Testers ===
* [[User:Citroklar|Citroklar]]: Tester, slave-work-coder (sometimes)
* ender`: Tester
* [[User:lionel77|lionel77]]: Tester and provider of binaries for Mac OS
* nachbarnebenan: Tester, and life-complicator by using large&strange nicks ;-P
* nich: Tester
* skolnick: Solaris tester
* [[User:Stefanero|Stefanero]]: Supporter, Tester, and [[aMuleWeb]] Guru
* [[User:thedude0001|thedude0001]]: Tester

=== Special Gold Guest Members ===
* [[User:Bigbob|Bigbob]]: Also known as ''[[User:Bigbob|Creteil]]''; [[aMule]] project creator.
* [[User:Madcat|Madcat]]: The one and only kitty dev.
* [[User:Tiku|Tiku]]: And God said: Let there be [[lMule]]!

=== Others ===
* [[User:Bootstrap|bootstrap]]: [[IRC]] bot (''bootbox'') and [[aMule CVS]] hoster
* [[User:uberpenguin|uberpenguin]]: uberpenguin is extremely difficult to classify... Let us call him the 'official bystander to *mule'.
* niet: [http://www.dns.net/dnsrd DNS] stuff, [[XAS]], tester.

=== Former Team-members ===
These are people who have worked on [[aMule]] in the past.
Please note that this list doesn't include the people from before [[aMule]] forked off from [[xMule]], nor does it include people from the [[lMule]] days. If you wish to learn more about those, please visit the websites of those projects.

==== Developers ====
* shakraw: [[aMuleWeb]] mantainer.
* [[User:Kry|Kry]]: Main developer and Admin, now retired.
* [[User:Unleashed|Unleashed]]: Sometimes around ;), not anymore.

==== Testers ====

=== Is this Team competent enough? ===

There is a private IRC channel where aMule developers talk about future plans, developing roadmaps and help each other. Many people wonder how's life in that channel. It is well known that a good working environment grants an efficient development. Now, [[A_random_day_in_aMule_development|get a random example of what the Team's working environment is]] ('''Parental advisory:''' Keep your children away from this link!).

== Helping ==
We can always use another helping hand, and if you are interested, then I'd encourage you to contact us and see if you can help us. Currently, what we need the most is developers and testers, though also translators and others.

=== Becoming a Developer ===
To become a [[aMule]] Developer (tm), you'll need, at the very least, a working knowledge of C++, since C++ is the language in which [[aMule]] is written. You'll also need to learn about the GUI toolkit used by [[aMule]]: [[wxWidgets]]. In addition, you are required to our [[Coding Style]] rules or we will beat you to death with a sockful of rocks. We do not require that you be an expert, only that you are willing to help and learn.

If you are interested, then simply drop by the [[IRC|IRC Channel]] and let us know. Currently, we use a private SVN server, but after you've submitted a patch or two you can easily get r/w access to it. You can also post patches on the [http://www.amule-project.net/amule/board.php?boardid=47 Development] forum, however, virtually all discussions regarding development happens on [[IRC]].

We can especially use your skills if you are using one of the platforms: [http://www.unix.org Unix], *[http://www.bsd.org BSD], [http://www.sun.com/solaris Solaris], [http://www.apple.com Macs] and [http://www.microsoft.com/windows Windows]. If your operating system of choice isn't on that list, then perhaps you can contribute.

=== Becoming a Tester ===
We need people who are willing to create complete bug-reports, as the standard is pretty low regarding user reports. This is rather simple, but takes patience. Please contact us on [[IRC]] for more information and read [[Backtraces|this guide on creating useful backtraces]].

=== Becoming a Translator ===
[[aMule]] already includes translations for a number of languages, however, we'll always welcome more, and even if your language of choice has been done already, then perhaps you can help improve it. Please see the [http://forum.amule.org/board.php?boardid=40 Translations forum] for more information on current translations, or contact us on [[IRC]]. Also, take a look at the [[Translations|aMule translation howto]].

BTW, you can also help with [[Translating_Wiki|translating aMule wiki]] articles. There's always lots of work to do. =)

== Contact ==

Contacting the aMule Team is easy. Choose between any of the listed ways in the [[contact|contact article]]. Just please do it once, avoiding spam or floods.

Ed2k links handling

2006-08-10T05:06:08Z

Thedude0001: Removed ancient versions of firefox & mozilla. Nobody should use these programs any longer and they're confusing lusers

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

The way to have [[aMule]] handle your [[ed2k link]]s on your favorite WebBrowser will depend on which WebBrowser you use. So, here's a list of mini-HowTos for each of the most popular WebBrowsers.
Have in mind that everywhere on this document, ''/path/to/ed2k'' should be replaced with ''/usr/local/bin/ed2k'', ''/usr/bin/ed2k'', ''C:\Program Files\aMule\ed2k.exe'' or whatever, depending on your own system's configuration.

As a general idea, in most [http://www.kernel.org Linux] systems, self-compiled [[aMule]]s will install the [[FAQ_ed2k_command|ed2k]] utility in ''/usr/local/bin/ed2k'', while package-installed [[aMule]]s will install it in ''/usr/bin/ed2k''. As an exception, it is known that [http://www.suse.com SuSE] packages install it in ''/usr/local/bin/ed2k''.

== [http://www.microsoft.com/windows/ie Internet Explorer] ==
'''by ''[[User:Jacobo221|Jacobo221]]'''''

Go to "Start" -> "Run" and run "regedit" (without quotes).

Now, in regedit, go to ''HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ed2k\shell\open\command''

'''NOTE:''' It could happen that ''ed2k'' and/or it's subfolders didn't exist. In such case, create them one-by-one by selecting "New" -> "Key" and entering ''ed2k'' or whatever as it's value.

http://www.amule.org/dev-up/ed2k-win1.jpg

Now just double click on "(Default)" (or "(Standad)" or whatever the first value is there) and enter the path to the ed2k application, followed by ''"%1"'' (with quotes), so you should end with some value like ''C:\Program Files\aMule2\ed2k "%1"''.

http://www.amule.org/dev-up/ed2k-win2.jpg

Finally, do the same in ''HKEY_CLASSES_ROOT\ed2k\shell\open\command''

== [http://www.konqueror.org Konqueror] ==
'''by ''gfdsa'''''

''/usr/kde/3.1/share/services'' you can find it by file names ended with ''.protocol'' kinda ''`find /usr -name "*.protocol"`'' or ''`find /opt -name "*.protocol"`'' or even put ''/'' to path if you want.

If the search was successful, create a file named like ''ed2k.protocol'' in
the mentioned directory:

<code>[Protocol] 
exec=/path/to/ed2k "%u" 
protocol=ed2k 
input=none 
output=none 
helper=true 
listing=false 
reading=false 
writing=false 
makedir=false 
deleting=false</code>

Now just restart [http://www.konqueror.org Konqueror].

'''NOTE:''' You might get a security warning. don't worry. it is just warning you that the link is being sent to an external application.

'''NOTE2:''' If after clicking ''OK'' on the security warning the link is still not being sent to [[aMule]], just right-click on the [[ed2k link]] and tell [http://www.konqueror.org Konqueror] to open it in a new window/tab.

== [http://galeon.sourceforge.net Galeon] ==

=== Method 1 ===

In the [http://freshmeat.net/projects/gnomecc GNOME Control Center] go to "Complex" -> "File Types and Programs" -> "Internet Services" -> "Add Service...".

In the protocol filed enter ''ed2k''

In the Program field enter ''ed2k %s''

Unselect "Run in terminal" if it is selected.

Click ''OK'' and you're done!

=== Method 2 ===

Execute the following three commands to create the appropriate ''gconf'' keys:
*''gconftool-2 -t string -s /desktop/gnome/url-handlers/ed2k/command "/usr/local/bin/ed2k %s"''
*''gconftool-2 -t bool -s /desktop/gnome/url-handlers/ed2k/enabled true''
*''gconftool-2 -t bool -s /desktop/gnome/url-handlers/ed2k/needs_terminal false''
Replace "''/usr/local/bin/ed2k''" above with the path and name of the ''ed2k'' executable on your system.

Uninstalling this protocol handler is similarly simple:
*''gconftool-2 -u /desktop/gnome/url-handlers/ed2k --recursive-unset''

== [http://www.opera.com Opera] ==
'''by ''thermoman (Marcel Meckel)'', ''ender'' and ''[[User:Jacobo221|Jacobo221]]''

=== Clean way ===

In [http://www.opera.com Opera] go to ''Tools->Preferences->Paths and Programms->Add...''

In the "Protocol" field enter ''ed2k''

In the "Path" or "Open with another application" field enter ''/path/to/ed2k''

http://www.amule.org/dev-up/ed2k-op.jpg

=== Dirty way ===

If he above instructions didn't work, you can try edit ''/etc/opera6rc'' as root or ''~/.opera/opera6.ini'' as non-root and setting:

''[User Prefs]'' 
''TrustedExternalURLProtocols=ed2k'' 
''[Trusted Applications]'' 
''ed2k=ed2k''

=== Opera 6 bug ===

'''[http://www.opera.com Opera] 6''' doesn't pass complete URL to external programs; only URL without protocol. The way to walk around this follows.

==== [http://www.kernel.org Linux] or some other [http://www.unix.org Unix]-like flavour ====

Create ''amule_submit.sh'' with this content:

<code>#!/bin/sh 
/path/to/ed2k "ed2k://$1"</code>

Now in ''Tools->Preferences->Paths and Programms->Add...->Path'' or in the ''opera6rc'' file change ''ed2k=/path/to/ed2k'' with ''ed2k=/path/to/amule_submit.sh''

==== [http://www.microsoft.com/windows Windows] ====

Create ''amule_submit.bat'' with this content:

''X:\path\to\ed2k.exe "ed2k://%1"''

Change ''ed2k=/path/to/ed2k ed2k://%u'' with ''ed2k=X:\path\to\amule_submit.bat ed2k://%u''

== [http://www.mozilla.org Mozilla] 1.7 (or later) & [http://www.mozilla.org/products/firefox Firefox] 0.9 (or later)==
'''by ''GhePeU'''''

Mozex doesn't work anymore with [http://www.mozilla.org Mozilla] 1.7 and [http://www.mozilla.org/products/firefox Firefox] 0.9. There is an alternate method that seems to be working with both of them:

*Remove [http://mozex.mozdev.org/installation.html MozEx] if installed or at least remove the ed2k input from it (only if [http://mozex.mozdev.org/installation.html MozEx] is installed)

*Insert ''about:config'' in the address bar

*Right click on the list, select '''New''', then '''Boolean'''; insert ''network.protocol-handler.external.ed2k'' as '''Preference Name''' and ''true'' as '''Value'''

*Now another right click, select '''New''' and '''String'''; insert ''network.protocol-handler.app.ed2k'' as '''Preference Name''' and ''/path/to/ed2k'' (path to where the file is installed on your system) as '''Value'''.

http://www.amule.org/dev-up/ed2k-ff9.jpg

'''NOTE 1:''' Since version 1.5.x of Mozilla Firefox this method doesn't work any longer for the windows version. You must use the Internet Explorer method with the registry entries instead.

== [http://xray.sai.msu.ru/~karpov/links-hacked Links] ==
(Probably this will work for the usual links and/or [[ed2k link|elinks]], too)

add to ''url.c'' behind the lines about telnet and tn3270:
''--snip''
''{"ed2k", 0, NULL, ed2k_func, 0, 0, 0},''
''--snap''

add to ''links.h'' behind the definitions of /* mailto.c */:
''--snip''
''void ed2k_func(struct session *, unsigned char *);''
''--snap''

add to ''mailto.c'' at the end:
''--snip''
''void ed2k_func(struct session *ses, unsigned char *url)''
''{''
''tn_func(ses, url, options_get("network_program_ed2k"), TEXT(T_ED2K), TEXT(T_BAD_ED2K_URL));''
''}''
''--snap''

add to ''options_register.c'' behind telnet and tn3270:
''--snip''
''register_option_char("network_program_ed2k", TEXT(T_ED2K_PROG),NULL,2);''
''--snap''

add to ''intl/*.lng'' behind
''"T_TN3270_PROG": T_ED2K_PROG, "ed2k program",'' (or whatever that is in your language), behind
''"T_TN3270": T_ED2K, "ed2k",'' and behind
''"T_BAD_TN3270_URL": T_BAD_ED2K_URL'' (I guess you've got the picture)

If you want to automatize this stuff, execute the following commands:
''cd intl''
''for l in *.lng; do''
''cp $l $l.bak''
''cat $l.bak | sed -e "/T_TN3270_PROG*/aT_ED2K_PROG\, \"ed2k program\"\," \''
''-e "/T_TN3270,\ */aT_ED2K\, \"ed2k\"\," \''
''-e "/T_BAD_TN3270_URL*/aT_BAD_ED2K_URL\, \"Bad ed2k url\"\," > $l''
''done''

Anyway, run afterwards before recompiling links-hacked:
''./synclang''
''cd ..''

Now you can compile with
''./configure'' (add your favourite options here) ''&&''
''make &&''
''make install''

Because links somewhat malforms the urls, we need a small bash script handler:
''cat > /usr/bin/ed2k4links.sh << "EOF"''

''#!/bin/bash''

''ed2k $(echo "ed2k://$1" | sed s/_/\|/g)''
''EOF''
''chmod a+x /usr/bin/ed2k4links.sh''

Do not forget to setup links (Options->Network Options->Mail and Telnet Programs) to call our ''ed2k4links.sh'' for [[ed2k link]]s:
''ed2k4links.sh %''

Attention: The Percent Mark is important! Now links should work with [[ed2k link]]s.

== Remotely handling links ==

You can also handle links remotely, which means that you click over an [[ed2k link]] in a browser somewhere in the world and it gets into your home's [[aMule]] queue.

How?

Easy enough: using [[aMuleCMD]] (thanks '''djtm''' for this tip). Instead of using the [[ed2k command]], use the following as the command to use:

''/'''path'''/'''to'''/amulecmd -rh $server -pw $pw -c "Add %u"''

Obviously, you'll have to replace ''$server'' and ''$pw'' with your server's [[IP]] (or [http://www.webopedia.com/TERM/D/DNS.html DNS]) and your [[External Connections]] password.

Please note that the above tip is only available since [[aMule]] 2.0.0rc8.

'''NOTE 1:''' In [http://www.mozilla.org Firefox], it is not possible to start a command with parameters. An easy solution is a shell script with the command described above. You only have to replace %u with $1. This shell script must be executable (chmod +x ed2k.sh) and defined as external ed2k app in Firefox.

'''NOTE 2:''' If you prefer simple tools, try this shell script (for [http://www.kernel.org Linux]) - can be used with the above mentioned tip:

#!/bin/bash
beep -f 100 -l 40 -r2
(sleep 1; echo dllink $1; sleep 2; echo q;) | nc '''''IP''''' '''''PORT'''''
beep -l 15 -r3

''nc'' is [http://netcat.sourceforge.net Netcat], but you can use telnet too (that's a bit simpler in [http://www.cygwin.com Cygwin]), ''beep'' is a simple program for beeping. ''IP'' and ''PORT'' should be replaced with the [[IP address]] and [[port]] of your remote server. That's it.

***N O T E***
I found the perfect way to do this.

To make FireFox launch ed2k links correctly (in aMule) you have to
follow some simple steps to tell it how to handle a new external
protocol. This should get rid of the dreaded "ed2k is not a registered
protocol" error you were most likely getting before.

* Enter about:config in the address bar.
* Right click on the list, select New, then Boolean; enter
network.protocol-handler.external.ed2k as Preference Name and true as Value
* Now right click, select New and String; enter
network.protocol-handler.app.ed2k as Preference Name and /usr/bin/ed2k

FAQ eD2k-Kademlia

2006-05-17T11:10:07Z

Thedude0001: =Are there any limitations on the ED2K network?=

<center>
<h4>F.A.Q. on eD2k-Kademlia</h4>

'''English''' | [[FAQ_eD2k-Kademlia-es|Español]] | [[FAQ_eD2k-Kademlia-it|Italiano]] | [[FAQ_eD2k-Kademlia-de|Deutsch]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]] | [[FAQ_eD2k-Kademlia-pl|Polish]] | [[FAQ_eD2k-Kademlia-ru|Russian]]
</center>

== What is ED2K? ==

ED2K is a protocol originally used by the P2P (Peer-to-Peer) client [[eDonkey2000]], which is where the name comes from. It is a server-client based protocol, with the ability to exchange sources between clients.

The ED2K network is server based like many other P2P networks such as [[Kazaa]] (Kazaa is server based, but hides the server connection from the user), which means that the first thing you do when you run [[aMule]] is to connect to a server (either manually or automatically).

Once successfully connected to a server, the client can search, either locally (the connected server) or globally (all servers), for any file and the servers asked will provide the client with a list of all the files which match search parameters.

If the user starts a download, the client will then ask the server for sources, which the server will return in the form of IP addresses for the clients that have told the server that they have the specific file.

Then the remote client will begin to upload a whole chunk to your client as soon as you are the [[FAQ_eD2k-Kademlia#What_is_all_this_talk_about_credits,_ratings_and_scoring_about?|first in the queue]], and when the chunk has been completly sent, you will be taken back to its upload queue. This way different chunks get spread around the ED2K network, so that, although no-one may have at a same given moment the complete file, it may be completed by downloading the different chunks from different people (it is well known that users tend to stop sharing a file once it has been completed).

Note that clients upload only '''one''' chunk at a time to another client. Even if a client is in the upload queue of two different files of a same user and gets to the top of both, that user will only upload one of the files to that client (the other upload, depending on the ED2K application the client uses, will probably remain as a maximum priority upload, but will not begin until the other chunk has been successfully uploaded).

If both users have HighID (see [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|What is LowID and HighID?]]) the transfer will be done directly from client to client (Peer-to-Peer), but if one of the clients have LowID, the connection will be established through the server, since LowID cannot accept incoming connections. As a result, two LowID clients '''cannot''' connect to each other.

== What is Kademlia? ==

Kademlia is a natural evolution of the ED2K network. Kademlia is the future. See [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|Are there any limitations on the ED2K network?]] for more information on why Kademlia is necessary.

Since Kademlia is a decentralized network, it removes the bottleneck that was previously caused by the need for servers (though [[Lugdunum]] has done great work in reducing this bottleneck). Now, instead of connecting to a server, you just connect to a client (with a known IP-address and port), which supports the network [[Kademlia]]. This is called the Boot Strapping.

Once connected, depending on your ability to accept incoming connections, you are given either "open" or "firewalled" status, which is similar to the HighID and LowID of the ED2K network. Then you are given an ID.

When searching, each client acts as a small server and is given responsibility for certain keywords or sources. This adds to the complexity of finding sources, as you no longer have a central server to ask, but instead will have to propagate the query through the network.

Kademlia is supported in aMule since the 2.1.0 version.

== Is Kademlia the same as Overnet? ==

Short and clear: No. Overnet is the natural serverless evolution of the eDonkey software, while Kademlia is the natural serverless evolution of *Mule clients. Both are based on the original [[Kademlia]] algorithm but have been applied in different ways and therefore are incompatible. So, it's the same philosophy, but different rules. To learn about how Overnet works, refer to http://www.edonkey2000.com/documentation/how_on.html but, keep in mind, Overnet's development is closed until it reaches version 1.0, while Kademlia's development is completly open from the very beginning.

== What is a chunk? ==

In the ED2K protocol, to avoid sharing corrupt files, each file is divided into various parts, which are known as ''chunks'', and then each chunk is hashed (read below to know what a [[FAQ_eD2k-Kademlia#What_is_a_hash?|hash]] is). Each chunk is 9.28MB in size, so a 15MB file will be divided into two chunks (9.28MB + 5.72MB), a 315KB file will be a single chunk and a 100MB file will be divided into 11 chunks (10x9.28MB + 7.2MB).

== What is a hash? ==

Dividing each file into chunks (see [[FAQ_eD2k-Kademlia#What_is_a_chunk?|What is a chunk?]]) will avoid the problem of downloading a whole corrupted file since only the corrupted chunk will have to be downloaded again, but a method to identify corrupted chunks is needed. This is done by using MD4 hashes.

A [[MD4 hash]] is a unique value each chunk is given and is the result of a mathematical operation on every single bit on the chunk. This means that modifying a single bit in a chunk would result in a completely different hash. That means that the [[client]] needs to verify the integrity of each part of a file as it is downloaded.

Not only are the chunks hashed but also, in order to get a file-hash, all chunks's hashes are concatenated one after the other in their file order (that is: chunk1's_hash+chunk2's_hash+chunk3's_hash+...) and the resulting string is hashed. This way, each file on the ED2K network has a unique identifier. The file hash isn't taken from hashing the whole file, but from hashing the value of the chunk's hashes.

In reality, you need both the hash of a file and its size. These pieces of information is embedded in the ED2k URLs found in many places.

Take this for example:

ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

The interesting parts are the fifth part, "2407949", which is the size of the file in bytes and the last part, "CC8C3B104AD58678F69858F1F9B736E9", which is the hash itself, stored as hex-decimals, 32 letters long.

The filename itself is irrelevant in the process of identifying the file.

== Why after searching, some files which are the same appear as a different file in the results, although they even have the same name? ==

If you understood "What is a hash" you will understand this quickly. When a search is started, the server tells the ED2K client the filename of the found file and the hash of the complete file for each file which matches the search. If two files, although being the same, have some difference in their content, no matter if it's big or small, the hash is different, so they are considered as a different file. That's also the reason why two file with different file name appear as the same file: on the ED2K network, the filename isn't important, the hash is.

== What is LowID and HighID? ==

Each client is assigned an ID (Identification) number which is unique and will distinguish the client from all other clients on the server. If this ID is below 16777216 (16 million) then you have a LowID and anything over is a HighID. Whether your client receives a high or low ID will depend on your client and whether or not the Client TCP port is open. Client TCP Port is an customisable option located in Preferences -> Connection. The default port is 4662 which is fine. If you understand [[FAQ_ed2k#What_is_ED2K?|what ED2K is]], odds are you'll understand the chances that clients with LowIDs may be unable to connect to other clients with LowIDs which reduces transfer rates significantly. This is the reason why having port 4662 TCP (or the one set in Preferences) is so important. Some of the larger servers refuse clients with LowIDs and disallow connections since LowID clients have data transfered through the server, rather than directly from the other client, which in turn adds more overhead for the server.

For clients with a HighID, their ID is the result of a mathematical operation with their IP which corresponds to A + 256*B + 256*256*C + 256*256*256*D, where the IP is A.B.C.D. Keep in mind that this ID has identification purposes as well. Apart from having an ID over or under 16777216, it does not matter if the ID is bigger or smaller. This means a client with an ID of 50000000 isn't any better than a client with an ID of 49999999. The only exception is at times servers are either incorrectly configured or are very busy and issue LowIDs to clients even though port 4662 TCP is open. These are rare exceptions but it can happen sometimes.

If you're unsure about having proper port settings, you can test your ports [http://www.amule.org/testport.php here].

== Which ports do I have to configure in a firewall or router to run aMule? ==

One has to distinguish between incoming and outgoing connections. Normally, all ports of a router are open for sending data (outgoing connection).

So, in this normal case, You only have to configure the ports for ''incoming'' connections:

aMule works even with no specific ports opened, but you won't get a HighID in this case. As mentioned above, to be given a HighID, port 4662 TCP (or the one set in the Preferences) must be listening (i.e. opened in your firewall and forwarded in your router).

Apart from that port, to have an optimal ED2K experience, two more port should be enabled for listening as well: UDP ports 4672 and 4665 (that is, TCP_PORT+3) (both can be changed to any other number in the Preferences).

If you are using Kad and your router is doing NAT (Network Address Translation), you should prevent your router from remapping the port of outgoing UDP port 4672 packets. This might help if you have a high ID but Kad status is 'firewalled'.

== What does each port do? ==

Well, since most ports can be configured to be set to any other number, the defaults will be listed. The traffic direction is from client perspective (you):
*4661 TCP (outgoing): Port, on which a server listens for connection (defined by server).
*4662 TCP (outgoing and incoming): Client to client transfers.
*4665 UDP (outgoing): Used for global server searches and global source queries. This is always Client TCP port + 3
*4672 UDP (outgoing and incoming): Extended eMule protocol, Queue Rating, File Reask Ping
*4711 TCP: WebServer listening port.
*4712 TCP: External Connection port. Used to communicate aMule with other applications such as aMule WebServer or aMuleCMD.
== Are there any limitations on the ED2K network? ==

Not much, but yes, there are: two natural limits and a "forced" limitation. The two natural limits have already been mentioned before. First, the issues on LowID users (their transfers involve data through the server and two LowID clients can't share between them). The second, although ED2K is a p2p protocol, it needs servers to establish the p2p connection. This has lots of problems relating to bottlenecks, privacy and scalability (if one single server is disconnected, a big part of the network is dosconnected with it). This latter one is solved in the Kademlia protocol.

About the "forced" limitation, it's only a limit to make sure that clients share, so that the ED2K network will not disappear: clients which have an upload limit of X KBps, where X is between 0 and 3.99 (both included) can download at a maximum of X*3 KBps. Clients which have an upload limit of Y KBps, where Y is between 4 and 9.99 (both included) can download at a maximum of Y*4 KBps. Clients with an upload limit of 10KBps or more have no downloading limitations. This restriction is set in the client application so it could be by-passed by hacking the code, but that would probably result in being banned from the servers you connect to.

Also, any client is forced to allow at least three upload slots, so it's not possible to allow more than upload_limit/3 KBps per slot.

There is one last limit: Maximum file size is exactly 256GB (274877906944 bytes). Older limit (up to eMule 0.46 and aMule 2.1.*) was slightly under 4GB aproximately (exactly 4294967295 bytes, although aMule would only support files up to 4290048000 bytes).

Additionally, this is not an eD2k limitation but a server limitation, servers will only send 300 results for your searches, so don't expect any more results.

And on the clients side, filenames are usually limited to 161 [[character]]s.

== Are there any limitations on the Kademlia network? ==

*As it is a network derived from the ed2k network and, therefore, has to maintain compatibility when it comes to identify files uniquely, the 256GB maximum file size limit exisits in the Kademlia network too.
*Same happens with the 161 characters limit.

== In search window, what filter stands for which filetype? ==

Keep in mind that the filters in the search window don't depend on the file type, but on the extensions of the filenames, in the following way:
*'''Archive:''' ''.ace .arj .rar .tar.bz2 .tar.gz .zip .Z''
*'''Audio:''' ''.aac .ape .au .mp2 .mp3 .mp4 .mpc .ogg .wav .wma''
*'''CDImage:''' ''.bin .ccd .cue .img .iso .nrg .sub''
*'''Picture:''' ''.bmp .gif .jpeg .jpg .png .tif''
*'''Program:''' ''.com .exe''
*'''Video:''' ''.avi .divx .mov .mpeg .mpg .ogg .ram .rm .vivo .vob''

So, a movie file that has the name "Birthday.zip" will appear in the Archive filter, but not in the Video filter.

== What is a source? ==

A source is a client which is sharing some chunk in some file you have in your downloading queue which you still have not completed. Obviously, the more sources you can get for a given file, the more possibilities you have to download the file and the quicker you'll download it. Keep in mind that there's a difference between "sources" and "available sources" if you're on LowID, since "sources"s stands for clients sharing a chunk or file you still haven't completed, while "available sources" stands for clients sharing a chunk or file you still haven't completed and from who you can download (that is, a source who is on HighID).

== What is all this talk about credits, ratings and scoring about? ==

All three concepts have to do with the way in which the ED2K network establishes the uploading queues preferences.

The score is the most important value: the client with the higher score will be the next client which you'll provide a slot to. The way in the score value is set is this: score = rate x time_waiting_in_seconds / 100
So, to understand this, we must known what rate is.

Rate can be understood as an objective preference. This is, the preference which a client is given without caring how much time it's been waiting. When a client is added to the uploading queue, it gets a rate of 100. This value is modified following according to this:

According to the amount of credits, the rate will be multiplied by 1x to 10x.
Depending on the file priority, it will be multiplied by 0.2x to 1.8x (Release 1.8x, High 0.9x, Normal 0.7x, Low 0.6x, Very Low: 0.2x). 
Users on specific old clients which load too much the network traffic will get penalized by multiplying their rate by 0.5x.

Banned clients will instantly get no rate (that is, their rate will by multiplied by 0).

This multiplying values are known as "modifiers". Clients with a modifier value strictly bigger than 1 will be marked as yellow in the icon.

So we only have credits left to known. Credits are a prize you get for uploading files to a specific user. Credits are exchanged between two specific clients, they are not global, so your own credits can't be viewed, although you can know the credits any other user has on you (that is, the credits you owe that client). Since credits are managed by the uploading client, you might be uploading to some client with no credits support, so you will gain no credits on him, although that client will actually get credits on you if it uploads to you, since you do have credits support. This credits are stored in clients.met file.

The credits modifier used by rate is the lower between these two: (upload_total x 2)/download_total or sqrt(upload_total+2) where both upload_total and download_total are measured in MBs.

If the result is lower than 1, then it is set to 1 and if it is bigger than 10, it is set to 10. In addition, if the uploaded total is less than 1MB, the modifier is set to 1 and if the downloaded total is equal to 0, then the modifier is set to 10.

== What is a slot? ==

When uploading files, your upload bandwidth (which may vary depending on the upload limit or the natural connection-type upload limit) will be divided into slots. So, each slot is an amount of KBps which will be assigned to each client who tries to download from you.

Talk:HowTo Compile In Debian/Ubuntu

2006-03-28T16:26:34Z

Thedude0001: =Problem with wxWidgets and GTK2=

To successully compile aMule in my Sarge I had to create a link like this:

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

because the make process searchs for config.h in cryptopp directory, not in crypto++.

'''They might have hanged the pathnames again. Thanks for the info :-) '''
'''The problem is that both crypto++ and Debian's crypto++ package have been changing the pathnames in order to suit, and this has become a mess. hehehe '''
'''Anyway, since next [[aMule]] release (it is currenly already implemented into aMule CVS) crypto++ will no longer be needed since it's necessary functions have been coded into aMule. '''
'''Again, thanks for the info!'''

----

28/09/04 - stk : A small error in step 8 : remplace "ls -s /usr/include/crypto++ /usr/include/cryptopp" by "ln -s /usr/include/crypto++ /usr/include/cryptopp" ;)

'''Thanx a lot! Fixed.'''

----

other info : In my Sarge, with libcrypto++5.1_5.1-5_i386.deb and libcrypto++-dev_5.1-5_i386.deb package, I have an error : ld cannot find lcryptopp..

so, I have made a link with this command : "ln -s /usr/lib/libcrypto++5.1.so /usr/lib/libcryptopp.so" and run ldconfig -> it work !

'''I completly forgot to answer to you :-( i added your comment to the howto some long time ago. thanks :)'''

----

jeremie :

Installing 200rc6 is a piece of cake with your advices. (sarge on 20041019)

No more fuss about crypto++ and so on, just apt-get the packages, then configure / make / make install.

It takes 5 minutes.

Thanks for the names of the dependancies.

'''Very much thanks for your words! Makes me feel batter :)'''

----

Works just fine in Ubuntu

I just wanted to let you know that this HowTo also applies just fine to "HowTo Compile in Unbuntu". Sure, anyone would have probably guessed that, but I can confirm it now... :-)

'''Hey! Thanx! THat is indeed an important note since Ubunto is being so successful and popular lately. I'll try to fix it somewhere to link ubunto users there too :)'''

----

Hi, I had problems with the ''libcurl2-dev''. Is ''libcurl3-dev'' the actual package?

'''Yes, you can use libcurl3-dev without any problems. In fact, thatnks for the note, i just changed it to point to liburl3 in the guide ;-)'''

-----

17/05/2005
Hi, I don't want compile amule :-), so I add ''deb http://www.vollstreckernet.de/debian/ testing amule'' and
''deb http://www.vollstreckernet.de/debian/ testing wx'' in my /etc/apt/sources.list. But ''apt-get update && apt-get install amule'' don't work... I find an error in ''http://www.vollstreckernet.de/debian/dists/testing/amule/binary-i386/Packages.gz
''. In fact, Packages.gz is broken!!!

'''Please contact Vollstrecker in http://forum.amule.org or mail him. He is the deb packager for CVS builds. Thanks :-)'''
---------------
22/05/05
When I run (Debian Sarge and Amule 2.0.1)

cd ~/aMule-compilation/aMule-2.0.1/ && ./configure && make

I get (after compilation process):

#bash: make: command not found

And I cannot execute make install....

I warn you that I did the compilation following absolutely all the steps that this page says: http://www.amule.org/wiki/index.php/HowTo_Compile_In_Debian
??????

Thanks in advance

Richard

'''Heh, well, you're right, I didn't think anyone would not have ''make'' installed ;-)'''

'''Ok, so just ''apt-get install make'''''

'''Now follow the article again, it will work now (I guess. If it still doesn't, please ask again :-))'''

Mmmmmmmm.... what ganso I am... You were right, I had not installed make (installed Sarge with manual selection of packages... and... you know, are a few and one gets dizzy...).
But now I request another aid to you that will serve, I suppose, for many users. Tell me exactly how to share in a same PC downloads of Win's emule in Linux's amule and vice versa...
Because I have put in a partition FAT32 the directories "incoming" and "temp" of Emule and I have mounted those same directories in Sarge (those directories are NOT mounted in the default folder of Amule, but in "/" (like this: /amule/incoming/temp).
But when I watch in "Traffic" of Amule does not see any of downloads that are in the directories mounted from FAT32....
Regards
Richard

'''Well, there's no trick. Just make sure aMule -> Preferences -> Directories points to the right directories ;-) Also take a look at [[FAQ_aMule#Can_I_use_eMule's_files_and_settings_and_vice-versa?]]'''

'''Please refer to http://forum.amule.org for non Debian-article-related stuff ;-) So any further questions regarding using your eMule files, please post them at the forums :-)'''

'''Greets.'''

== Problem with wxWidgets and GTK2 ==

When i configure amule 2.0.3 in my sarge
i see this line
checking if wxWidgets was linked with GTK2... no

And when configure script finish i watch that

"Configure script has finished system check.

Configured aMule 2.0.3 for 'i686-pc-linux'.

aMule enabled options:

**** aMule Core ****
Prefix where aMule should be installed? /usr/local
Should aMule be compiled with i18n support? yes
Should aMule be compiled in debug mode? yes
Should aMule be compiled with profiling? no
Should aMule be compiled with optimizations? no
Should aMule be compiled with taskbar icon support? yes
Should aMule be compiled with old GTK taskbar icon? yes
Should aMule be compiled with UTF-8 taskbar icon support? no
Should aMule be linked against patched gsocket? yes
Should aMule monolithic application be built? yes
Should aMule daemon version be built? no
Should aMule remote gui be built? (EXPERIMENTAL) no
Crypto++ library/headers style? embedded

**** aMule TextClient ****
Should aMule Command Line Client be built? no
Should aMule GUI Client be built? no

**** aMule WebServer ****
Should aMule WebServer be built? no
Should aMule WebServer GUI be built? no

**** aMule ED2K Links Handler ****
Should aMule ED2K Links Handler be built? yes

**** aMuleLinkCreator ****
Should aMuleLinkCreator GUI version (alc) be built? no
Should aMuleLinkCreator for console (alcc) be built? no

**** aMule Statistics ****
Should C aMule Statistics (CAS) be built? no
Should aMule GUI Statistics (wxCas) be built? no

**** General Libraries and Tools ****
Should ccache support be enabled? no
Libraries aMule will use to build:
wxWidgets 2.4.2
GTK Not detected
crypto++ embedded
zlib 1.2.2

WARNING! gd-lib >= 2.0.0, or a functional gd.h (from gd-devel) not found.
amuleweb will be compiled but file download progress bar images will NOT be generated.
See the above error on gd check for solutions.
"
How can I fix it?

'''There's nothing to fix. Just run ''make'' now. It didn't detect the GTK version but that doesn't prevent it from compiling as long as it detected wxGTK correctly.'''

----

Hi, Im getting the same output as the guy above and when making it complains about an undeclared definition. Ive done my homework trying to find in google in what file this definition is, without any luck

/usr/bin/ld: warning: libstdc++.so.5, needed by /usr/lib/libwx_gtk-2.4.so, may conflict with libstdc++.so.6
amule-ExternalConn.o: En la función `pair':
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_pair.h:85: referencia a `CValueMap::CValueMap(CValueMap const&)' sin definir
amule-ExternalConn.o: En la función `~pair':
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_pair.h:69: referencia a `CValueMap::~CValueMap()'sin definir
amule-ExternalConn.o: En la función `pair':

/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_pair.h:69: referencia a `CValueMap::CValueMap(CValueMap const&)' sin definir
amule-ExternalConn.o: En la función `__gnu_cxx::__mt_alloc_base<CMD4Hash>::destroy(CMD4Hash*)':
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/ext/mt_allocator.h:614: referencia a `CMD4Hash::~CMD4Hash()' sin definir
amule-ExternalConn.o: En la función `std::map<void*, CValueMap, std::less<void*>, std::allocator<std::pair<void* const, CValueMap> > >::operator[](void* const&)':
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_map.h:339: referencia a `CValueMap::~CValueMap()'sin definir
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_map.h:339: referencia a `CValueMap::~CValueMap()'sin definir
collect2: ld returned 1 exit status
make[3]: *** [amule] Error 1
make[3]: Leaving directory `/usr/src/aMule-2.0.3/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/aMule-2.0.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/aMule-2.0.3'
make: *** [all] Error 2

"referencia a" && "sin definir" means "undefined reference to"

Thanks

'''A mi me parece que el error viene por ''/usr/bin/ld: warning: libstdc++.so.5, needed by /usr/lib/libwx_gtk-2.4.so, may conflict with libstdc++.so.6''. Parece que algo está mal en tus librerias estándar de C++. Prueba a reinstalar gcc y g++ y asegurate de que no los tienes doblemente instaladas...'''

--------

To successully compile aMule in my Sarge I had to create a link like this:

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

because the make process searchs for config.h in cryptopp directory, not in crypto++.

'''They might have hanged the pathnames again. Thanks for the info :-) '''
'''The problem is that both crypto++ and Debian's crypto++ package have been changing the pathnames in order to suit, and this has become a mess. hehehe '''
'''Anyway, since next [[aMule]] release (it is currenly already implemented into aMule CVS) crypto++ will no longer be needed since it's necessary functions have been coded into aMule. '''
'''Again, thanks for the info!'''

----

28/09/04 - stk : A small error in step 8 : remplace "ls -s /usr/include/crypto++ /usr/include/cryptopp" by "ln -s /usr/include/crypto++ /usr/include/cryptopp" ;)

'''Thanx a lot! Fixed.'''

----

other info : In my Sarge, with libcrypto++5.1_5.1-5_i386.deb and libcrypto++-dev_5.1-5_i386.deb package, I have an error : ld cannot find lcryptopp..

so, I have made a link with this command : "ln -s /usr/lib/libcrypto++5.1.so /usr/lib/libcryptopp.so" and run ldconfig -> it work !

'''I completly forgot to answer to you :-( i added your comment to the howto some long time ago. thanks :)'''

----

jeremie :

Installing 200rc6 is a piece of cake with your advices. (sarge on 20041019)

No more fuss about crypto++ and so on, just apt-get the packages, then configure / make / make install.

It takes 5 minutes.

Thanks for the names of the dependancies.

'''Very much thanks for your words! Makes me feel batter :)'''

----

Works just fine in Ubuntu

I just wanted to let you know that this HowTo also applies just fine to "HowTo Compile in Unbuntu". Sure, anyone would have probably guessed that, but I can confirm it now... :-)

'''Hey! Thanx! THat is indeed an important note since Ubunto is being so successful and popular lately. I'll try to fix it somewhere to link ubunto users there too :)'''

----

Hi, I had problems with the ''libcurl2-dev''. Is ''libcurl3-dev'' the actual package?

'''Yes, you can use libcurl3-dev without any problems. In fact, thatnks for the note, i just changed it to point to liburl3 in the guide ;-)'''

-----

17/05/2005
Hi, I don't want compile amule :-), so I add ''deb http://www.vollstreckernet.de/debian/ testing amule'' and
''deb http://www.vollstreckernet.de/debian/ testing wx'' in my /etc/apt/sources.list. But ''apt-get update && apt-get install amule'' don't work... I find an error in ''http://www.vollstreckernet.de/debian/dists/testing/amule/binary-i386/Packages.gz
''. In fact, Packages.gz is broken!!!

'''Please contact Vollstrecker in http://forum.amule.org or mail him. He is the deb packager for CVS builds. Thanks :-)'''
---------------
22/05/05
When I run (Debian Sarge and Amule 2.0.1)

cd ~/aMule-compilation/aMule-2.0.1/ && ./configure && make

I get (after compilation process):

#bash: make: command not found

And I cannot execute make install....

I warn you that I did the compilation following absolutely all the steps that this page says: http://www.amule.org/wiki/index.php/HowTo_Compile_In_Debian
??????

Thanks in advance

Richard

'''Heh, well, you're right, I didn't think anyone would not have ''make'' installed ;-)'''

'''Ok, so just ''apt-get install make'''''

'''Now follow the article again, it will work now (I guess. If it still doesn't, please ask again :-))'''

Mmmmmmmm.... what ganso I am... You were right, I had not installed make (installed Sarge with manual selection of packages... and... you know, are a few and one gets dizzy...).
But now I request another aid to you that will serve, I suppose, for many users. Tell me exactly how to share in a same PC downloads of Win's emule in Linux's amule and vice versa...
Because I have put in a partition FAT32 the directories "incoming" and "temp" of Emule and I have mounted those same directories in Sarge (those directories are NOT mounted in the default folder of Amule, but in "/" (like this: /amule/incoming/temp).
But when I watch in "Traffic" of Amule does not see any of downloads that are in the directories mounted from FAT32....
Regards
Richard

'''Well, there's no trick. Just make sure aMule -> Preferences -> Directories points to the right directories ;-) Also take a look at [[FAQ_aMule#Can_I_use_eMule's_files_and_settings_and_vice-versa?]]'''

'''Please refer to http://forum.amule.org for non Debian-article-related stuff ;-) So any further questions regarding using your eMule files, please post them at the forums :-)'''

'''Greets.'''

== Problem with wxWidgets and GTK2 ==

When i configure amule 2.0.3 in my sarge
i see this line
checking if wxWidgets was linked with GTK2... no

And when configure script finish i watch that

"Configure script has finished system check.

Configured aMule 2.0.3 for 'i686-pc-linux'.

aMule enabled options:

**** aMule Core ****
Prefix where aMule should be installed? /usr/local
Should aMule be compiled with i18n support? yes
Should aMule be compiled in debug mode? yes
Should aMule be compiled with profiling? no
Should aMule be compiled with optimizations? no
Should aMule be compiled with taskbar icon support? yes
Should aMule be compiled with old GTK taskbar icon? yes
Should aMule be compiled with UTF-8 taskbar icon support? no
Should aMule be linked against patched gsocket? yes
Should aMule monolithic application be built? yes
Should aMule daemon version be built? no
Should aMule remote gui be built? (EXPERIMENTAL) no
Crypto++ library/headers style? embedded

**** aMule TextClient ****
Should aMule Command Line Client be built? no
Should aMule GUI Client be built? no

**** aMule WebServer ****
Should aMule WebServer be built? no
Should aMule WebServer GUI be built? no

**** aMule ED2K Links Handler ****
Should aMule ED2K Links Handler be built? yes

**** aMuleLinkCreator ****
Should aMuleLinkCreator GUI version (alc) be built? no
Should aMuleLinkCreator for console (alcc) be built? no

**** aMule Statistics ****
Should C aMule Statistics (CAS) be built? no
Should aMule GUI Statistics (wxCas) be built? no

**** General Libraries and Tools ****
Should ccache support be enabled? no
Libraries aMule will use to build:
wxWidgets 2.4.2
GTK Not detected
crypto++ embedded
zlib 1.2.2

WARNING! gd-lib >= 2.0.0, or a functional gd.h (from gd-devel) not found.
amuleweb will be compiled but file download progress bar images will NOT be generated.
See the above error on gd check for solutions.
"
How can I fix it?

'''There's nothing to fix. Just run ''make'' now. It didn't detect the GTK version but that doesn't prevent it from compiling as long as it detected wxGTK correctly.'''

----

Hi, Im getting the same output as the guy above and when making it complains about an undeclared definition. Ive done my homework trying to find in google in what file this definition is, without any luck

/usr/bin/ld: warning: libstdc++.so.5, needed by /usr/lib/libwx_gtk-2.4.so, may conflict with libstdc++.so.6
amule-ExternalConn.o: En la función `pair':
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_pair.h:85: referencia a `CValueMap::CValueMap(CValueMap const&)' sin definir
amule-ExternalConn.o: En la función `~pair':
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_pair.h:69: referencia a `CValueMap::~CValueMap()'sin definir
amule-ExternalConn.o: En la función `pair':

/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_pair.h:69: referencia a `CValueMap::CValueMap(CValueMap const&)' sin definir
amule-ExternalConn.o: En la función `__gnu_cxx::__mt_alloc_base<CMD4Hash>::destroy(CMD4Hash*)':
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/ext/mt_allocator.h:614: referencia a `CMD4Hash::~CMD4Hash()' sin definir
amule-ExternalConn.o: En la función `std::map<void*, CValueMap, std::less<void*>, std::allocator<std::pair<void* const, CValueMap> > >::operator[](void* const&)':
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_map.h:339: referencia a `CValueMap::~CValueMap()'sin definir
/usr/lib/gcc/i486-linux-gnu/4.0.1/../../../../include/c++/4.0.1/bits/stl_map.h:339: referencia a `CValueMap::~CValueMap()'sin definir
collect2: ld returned 1 exit status
make[3]: *** [amule] Error 1
make[3]: Leaving directory `/usr/src/aMule-2.0.3/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/aMule-2.0.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/aMule-2.0.3'
make: *** [all] Error 2

"referencia a" && "sin definir" means "undefined reference to"

Thanks

'''A mi me parece que el error viene por ''/usr/bin/ld: warning: libstdc++.so.5, needed by /usr/lib/libwx_gtk-2.4.so, may conflict with libstdc++.so.6''. Parece que algo está mal en tus librerias estándar de C++. Prueba a reinstalar gcc y g++ y asegurate de que no los tienes doblemente instaladas...'''

--------

== Problem with ubuntu ==

I have just installed amule with the "deb http://amule-debian.dyndns.org/ debian/" source but while i'm loading amule, I've got the following error message :

amule: error while loading shared librairies : libbfd-2.15.so: cannot open shared object file

I'm running the last stable version of ubuntu whith gnome.

Thanks for help !! 
gallou

'''just install libbfd & libbfd-dev or binutils & binutils-dev'''

--------

I have installed binutils-dev but I have still this problem.
I found the following file : /usr/lib/libbfd-2.16.1.so , is it a version problem ? 
gallou

'''hi, yes.. the version is the problem. I can tell you more at the weekend as I have no time now. sorry.''

''But you could look for some Ubuntu forum and ask the ppl there about aMule.''

'''cheers,
'''deltaHF'''

Fixed by linking libbdf new version with old version 
ln /usr/lib/libbdf-2.16.1.so /usr/lib/libbfd-2.15.so
 (maybe not a good idea but it's works without bugs actually !)
 gallou

== undefined reference to CValueMap ==

Hi,
I have the following errors while building amule2.0.1 (I dont want the latest version cause it needs wx2.6 which i dont want to install) :

amule-ExternalConn.o: In function `Get_EC_Response_GetSharedFiles(CFileEncoderMap<CKnownFile, CKnownFile_Encoder, CSharedFileList>&, CObjTagMap&)':ExternalConn.cpp:(.text+0x40c6): undefined reference to `CValueMap::CValueMap(CValueMap const&)'
...

more "undefined reference to CValueMap..." follow the one I mention.
Theses errors occured after a g++ call.

I didnt manage to locate the library needed... :(

EDIT : It seems to be a g++-4.0 issue, fixed in 2.1.0

== undefined reference to CValueMap ==

Hi,
I have the following errors while building amule2.0.1 (I dont want the latest version cause it needs wx2.6 which i dont want to install) :

amule-ExternalConn.o: In function `Get_EC_Response_GetSharedFiles(CFileEncoderMap<CKnownFile, CKnownFile_Encoder, CSharedFileList>&, CObjTagMap&)':ExternalConn.cpp:(.text+0x40c6): undefined reference to `CValueMap::CValueMap(CValueMap const&)'
...

more "undefined reference to CValueMap..." follow the one I mention.
Theses errors occured after a g++ call.

I didnt manage to locate the library needed... :(

EDIT : It seems to be a g++-4.0 issue, fixed in 2.1.0

HowTo Compile In Debian-es

2006-01-11T14:04:16Z

Thedude0001: =Versión de aMule CVS=

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

COMO compilar [[aMule]] en [[Debian]] o [http://www.ubuntulinux.org Ubuntu] por ''[[User:Jacobo221|Jacobo221]]'' y los ayudantes [http://www.gnu.org GNU] [http://www.kernel.org Linux]

Traducción por ''[[User:seath|T. Bernaschina]]''

¡Gracias muy especiales a ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' y ''klando'' por sus pruebas!!

'''NOTA:''' Este COMO estará enfocado también en [http://www.ubuntulinux.com Ubuntu Linux].

== ¿Está seguro de que quiere compilar? ==

Si no, (que es bastante común) decida si quiere la versión estable de
[[aMule]] o la última versión del [[aMule CVS]].

=== Versión estable de [[aMule]] ===

Puede instalar la última versión estable de [[aMule]] a través de los [http://packages.debian.org deb]s, para esto tiene que añadir la siguiente línea en su archivo ''/etc/apt/sources.list'':

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

Ahora ejecute <code>apt-get update && apt-get install amule</code>

'''NOTA:''' Si al intentar instalar [[aMule]] aparece un mensaje de error quejandose por <code>libbfd-2.xx.so</code>, solamente cambie a superusuario ''root'' y vaya a ''/usr/lib'' y haga <code>ln -s libbfd.so libbfd-2.xx.so</code>

'''NOTA:''' Esto de arriba no funcionó para mí, pero esto si: <code>ln -s libbfd-2.16.1.so libbfd-2.15.so</code>

=== Versión de [[aMule CVS]] ===

Puede conseguir la última versión de [[aMule CVS]] a través de los debs, tiene que añadir la siguiente línea en su archivo ''/etc/apt/sources.list'':

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

Ahora ejecute ''apt-get update && apt-get install amule''

Puede que desee ver las otras utilidades disponibles para [[aMule]]:

'''[[aMule CVS]]'''
*amule
*amule-common
*amuled
*amule-remote-gui
*amuleweb
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

'''[[aMule]] estable'''
*amule
*amule-daemon
*amule-remote-gui
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (amule-console-utils & amule-gui-utils)

Por ejemplo, si cree que la [[Webserver|interfaz de Web]] del [[aMule]] es buena y desea tenerla también, ejecute la siguiente linea después de la de arriba:

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

Para [[aMule]] estable: ''apt-get install amule-console-utils''

Si todavía desea compilar [[aMule]] en vez de instalar un binario, siga leyendo...

== Notas antes de comenzar ==

'''Importante:''' Tenga en mente que este COMO fue hecho para aMule 2.0.0 o superior en [[Debian]] 3.0 (Woody/Sarge/Sid).

Este COMO está basado en la utilización de apt-get la herramienta de instalación de paquetes, lo que significa que tendrá que ser capaz de tener acceso de superusuario (root). También, apt-get requiere que las dependencias de paquetes esten perfectamente instaladas en el sistema. Si por lo general usa apt-get para para instalar cualquier aplicación, saltese esto y vaya a la siguiente sección. Si raras veces usa apt-get, pero en cambio, usa dpkg, puede;

A) (Recomendado) Soluciona todos los problemas de dependencias en su sistema.
Esto puede ser hecho viendo la salida de <code>"dpkg -C"</code> e instalando/quitando/actualizando los paquetes que esto menciona según se requieren. Esta opción es la recomendada ya que no sólo asegurará que su compilación de aMule será la más correcta, sino que también hará su sistema lo más estable posible y desde ahora será capaz de usar apt-get no sólo para hacer las instalaciones más fáciles, sino que también mejorarara su sistema.

B) Forzar a apt-get para ignorar los problemas de dependencias usando -f o --fix-broken switches (solamente uno de estos, ya que son exactamente lo mismo, entonces podría ser, por ejemplo <code>"apt-get install -f ..."</code>). Esta opción puede causar una instalación corrupta de algunos paquetes que pueden hacer que la aplicación no funcione. También tenga en mente que utilizar esto pone en marcha un sistema con problemas de dependencias y puede hacer que el sistema se rompa completamente si el paquete instalado es un paquete base (aunque no es el caso).

C) Seguir estas instrucciones, pero, en vez de usar <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> donde foo es el paquete para instalar. Recuerde que los paquetes deben ya estar en el sistema cuando instale paquetes con dpkg. Acuérdese también de descargar cualquier paquete de "Depends (dependencias)" ya que seguramente será necesario para compilar [[aMule]] satisfactoriamente. Evite usar cualquiera de las siguientes opciones de dpkg: --force-all --force-depends-version --force-depends --force-conflicts

Si por lo general instala aplicaciones desde los archivos fuente, lea deltaHF's [[Compilation_Installation|"Compilación de aMule / Como instalación"]] ya que su sistema no podría conformar las dependencias del paquete del aMule de Debian aunque con <code>"dpkg -C"</code> no muestre ningún error.

== Lo más fácil: Preparación del sistema ==

Una vez que decidió usar apt-get, debe asegurarse que descargará las últimas versiones de los paquetes (el equipo de aMule ha descubierto fallas en algunos paquetes de deb que harían a aMule imposible de compilar sobre Debian sin compilar algunas otras bibliotecas también. Estas fallas han sido fijadas en paquetes de debian, entonces es muy importante estar seguro de tener los paquetes actualizados). Esto se logra haciendo:

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

'''''Nota 1:''' Debe ser superusuario para hacer esto. Ingrese como superusuario o como <code>"su"</code> o use <code>"sudo"</code>. NB: <code>"sudo"</code> debe ser especificado en ambos comandos del apt-get, de esta forma:''

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

''<code>"sudo"</code> no es un comando base, puede que no esté instalado en su sistema, aunque lo más probable es que si. Esté enterado que siguiendo este Como enteramente como root puede traer algunos problemas más adelante, por ejemplo no poder suprimir ciertos archivos como usuario normal, entonces por favor use los privilegios de root cuando sea necesario.''

'''''Nota 2:''' Usuarios Woody (es decir, la gente pegada en el rama estable de Debian 3.0) no podrá instalar el wxGTK, wxbase y bibliotecas de Crypto++ puesto que no estaban disponibles en las versiones compatibles mínimas actuales (2.4.2 y 2.5.1 respectivamente) cuando Woody fue liberado.''

''Lo mejor para los usuarios de Woody es cambiar al rama de Sarge o de Sid. Eso se puede hacer con el siguiente comando (otra vez, usted debe ser root)''

perl -pi.$$ -e "s/(\bstable|woody)/testing/g" /etc/apt/sources.list

''o''

perl -pi.$$ -e "s/(\bstable|woody)/sarge/g" /etc/apt/sources.list

''para cambiar a la rama de Sarge/testing, o con''

perl -pi.$$ -e "s/(\bstable|woody)/unstable/g" /etc/apt/sources.list
''o''

perl -pi.$$ -e "s/(\bstable|woody)/sid/g" /etc/apt/sources.list

''para cambiar a la rama de Sid/unstable.''

''Si los usuarios de Woody no estan interesados en cambiar a Sarge necesitarán descargar los paquetes debian Woody-backported agregando la siguiente línea a /etc/apt/sources.list (recuerde hacer un <code>"apt-get update"</code> después de agregar esta línea):''

deb <nowiki>http://debian.thermoman.de/</nowiki> woody wxwindows2.4 libcrypto++

''Que más, detener el trabajo de [http://www.thermoman.de thermoman] en el backports del [[aMule]] para [http://www.debian.org Woody] en la versión [[aMule]] 2.0.0-rc5, los lanzaminetos más nuevos de backports de [[aMule]] son inasequibles. Disculpen.''

'''''Nota 3:''' Los usuarios de Sarge no tendrán ningún problemas de dependencia, ya que tanto crypto++ y wxWidgets ahora han sidos colocados en Sarge. Por lo tanto ya no hay necesidad de actualizar el archivo 'sources.list'' en las distribuciones de Debian Sarge.''

'''''Nota 4:''' Los usuarios de Sid (es decir, la gente que lleva a cabo la rama inestable de Debian 3.0) podría sufrir problemas de paquetes no completamente puestos en práctica o con dependencias rotas (ambas cosas son normales en la rama inestable). Es muy importante tener esto presente puesto que un compilador (g++) será instalado y que podría estar con fallas y arrastrar las fallas a la mayoría de los paquetes que se compilaron con él (hasta que sea actualizado, desde luego). Si un paquete estuviera con fallas, para retroceder puede usar la opción --force-downgrade con dpkg.''

Si por alguna razón piensa que todo esto es muy complicado, puede esperar un par de días hasta que aparezca una versión binaria de aMule para su arquitectura (como un archivo .deb)

== Lo más rápido: Instalación de los paquetes necesarios ==

Recuerde que necesita ser superusuario (root) para instalar sus aplicaciones usando apt-get, ya que apt-get instala las aplicaciones con sus dependencias. Sino ingresa como superusuario (root), use "su" o añada "sudo" antes de cada comando mostrado aqui.

Los siguientes son los paquetes que deben ser instalados:

1) Instale el último compilador estable de g++ y la Libreria Standar de C++

apt-get install g++

las librerias requeridas para compilar [[aMule]] (wxbase realmente no es una libreria requerida para compilar aMule, pero a menos que sepa lo que está haciendo, asegurese de instalarlo. No demostraré en esta esta guía cómo forzar la compilación de aMule sin wxbase):

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

Alternativamente puede utilizar <code>apt-get build-dep amule</code> para conseguir todas las dependencias requeridas para la compilación. De todas formas, este último método no es seguro que funcione, puesto que dependerá de la última versión en el depósito de Debian o las versiones de CVS que puden tener diferentes dependencias.
Y una utilidad requerida para compilar [[aMule]]:

apt-get install gettext make

'''''Nota 5:''' Todo esto se puede hacer en un sólo comando, lo que puede ser más comodo para los usuarios usando <code>"sudo"</code> para obtener privilegios de superusuario (root):''

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

'''''Nota 6:''' Del aMule 2.0.0-rc1 al aMule 2.0.0-rc5 (inclusive) el paquete ''libcrypto++-dev'' es necesario para compilar aMule, sólo si está compilando alguna de estas versiones, también debería hacer un apt-get libcrypto++-dev.

También, podría estar interesado en la instalación de libgd2-noxpm-dev, si planea compilar CAS (Habilitación de columna de direcciones). Esta no es una biblioteca requerida para compilar CAS (Habilitación de columna de direcciones), esta biblioteca sólo es usada por CAS (Habilitación de columna de direcciones) para crear imágenes (desde v2.0.0-rc3) sobre el estado actual de aMule (ejecutando <code>cas -o</code>). Si usted planea usar esta caracteristica de CAS, usted tiene que instalar LibGD2. De todos modos, CAS compilará perfectamente incluso si LibGD2 no es instalada, ya que es detectada, en tiempo de compilación, si dicha biblioteca está instalada.''

'''''Nota 7:''' Los usuarios de Woody probablemente no podrán conseguir libgd2-xpm-dev y libcurl3-dev ya que esos paquetes no están disponibles para Woody. Para libcurl3-dev sólo puede instalar libcurl2-dev i continuar, todo estará bien para libgd2-xpm, en este momento no hay backport disponible pero, ya que esta biblioteca es utilizada solamente por CAS (y sugerido, incluso no requerido), no dará ningún problema en tiempo de compilación. Solamente esté consciente que <code>cas -o</code> no funcionará.''

2) Descargue la última versión del codigo fuente de [[aMule]] desde [http://www.amule.org/files/files.php?cat=6 aquí] (o vea [[AMule_CVS|aquí]] para actualizar el enlace).

'''''Nota 8:''' Desde ahora, Supondré que estamos instalando aMule 2.0.0-rc3''

3) Arreglo de la Libreria Crypto++ 5.1 if si es que la usa.

Desde [[aMule]] 2.0.0-rc1 hasta aMule 2.0.0-rc5 (inclusive) esta libreria es requerida porque [[aMule]] ahora está soportando SecureIdent (recuerde, desde aMule 2.0.0-rc6, libcrypto++ es opcional y no se necesita por defecto), pero el paquete de [[Libcrypto|Crypto++]] [[Debian]] ha tenido fallas de compilación y todavía tiene una (aunque el resto se han descubierto después de los informes del equipo del aMule). Recuerde que debe hacer un update y un dist-upgraded con apt-get antes de instalar cualquier paquete de [[Debian]] en este Como, si no, usted podría instalar (o haber instalado ya) un paquete Crypto++ con fallas y este problema no satisfacerá sus necesidades. Para arreglar el último paquete de [[Libcrypto|crypto++]] [[Debian]] sólo es necesario un enlace simbólico:''

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

''Si todavía no puede compilar crypto++, intente compilarlo después de ejecutar el siguiente comando:''

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

'''''Nota 9:''' Ya que este enlace necesita permisos de escritura en /usr/lib, los privilegios de superusuario (root) son necesarios. Una vez más esto se puede hacer facilmete con <code>"su"</code> o <code>"sudo"</code>.''

=== Usando [[wxWidgets]] 2.6 ===

Los usuarios de [[Debian|Etch]] y [[Debian|Sid]] pueden usar wxWidgets 2.6 en lugar de wxWidgets 2.4 (los usuarios de Woody y Sarge olvidadlo. Pasad directamente al capítulo siguiente).

Para usar wxWidgets 2.6 en lugar de 2.4, simplemente reemplazad en los comandos menionados hasta ahora los términos ''libwxbase2.4-dev'' y ''libwxgtk2.4-dev'' por ''libwxbase2.6-dev'' y libwxgtk2.6-dev'' respectivamente.

Si se debe o no usar wx 2.6 en lugar de wx 2.4 es una decision personal. Tiene ventajas y desventajas. De todas maneras, en la mayoría de casos, se agradece usar wx 2.6, así que está recomendado.

== Lo más duro: Compilación [[aMule]] ==

4) Extraiga las fuentes. Lo siguiente creará una carpeta en el directorio home de su usuario donde extraerá las fuentes con la opción -C en ella (el siguiente comando entiende que las fuentes de [[aMule]] están en el directorio actual):

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

'''''Nota 10:''' Recuerde que estoy suponiendo que está extrayendo [[aMule]] 2.0.0-rc3. Cambie el nombre de archivo si no corresponde con el nombre del archivo del codigo fuente.''

5) ¡Compile [[aMule]]! El siguiente comando cambiará al directorio que contiene [[aMule]] 2.0.0rc3 y lo compilará:

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

'''''Nota 11:''' Por favor vea el [[configure|articulo de configuración]].''

'''''Nota 12:''' Usted debe comprobar la salida de
./configure --help | more
para ver si hay cualquier cambio en la configuración que puede ser de su interés, por ejemplo --disable-debug --enable-optimise o --bindir= ''

'''''Nota 13:''' si aparece un mensaje de error, mientras compila, similar a: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", lo más probable es que tenga problemas con wxWidgets. Intente con''

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

''el cuál reinstalará wxWidgets y probablemente arreglará el error de compilación.''

== Reunión de satisfacción: ¡Instalación de aMule! ==

8) ¿Qué es falta? Instale aMule (recuerde que usted debe ser superusuario (root), entonces conéctese como la superusuario (root) o use code>"su"</code> o <code>"sudo"</code>):

make install

Ahora puede remover los fuentes para liberar espacio en el disco duro, debe ejecutar:

rm -rf ~/aMule-compilation/

== El final: Comprobaciónes finales ==

Si usted alguna vez ha instalado aMule de los paquetes de Debian (no importa si el paquete viene de http://gunnm.org/~soda), usted tendrá binarios aMule instalados en /usr/bin. Pero <code>"make install"</code> instala binarios en /usr/local/bin (a no ser que --prefix= sea puesto en la configuración). Esto nos conduce al punto que escribiendo "amule" alguna de las dos versiones de aMule podría ser invocada para instalarse (cual es ejecutado dependerá de la variable de ambiente $PATH. Usted puede comprobarlo escribiendo <code>"type amule"</code>). El paso siguiente es muy fácil: quite el aMule instalado por el paquete de [[Debian]]. Puede hacer esto con el comando "apt-get remove amule" (no use <code>"apt-get remove --purge"</code> o podría perder sus ajustes de [[aMule]]) o con <code>"dpkg --remove amule"</code> (otra vez, nunca use <code>"dpkg --purge"</code> o usted podría perder sus ajustes de [[aMule]]). apt-get quitará aMule-utils si usted lo tiene instalado (sólo disponible como un paquete separado en Sid, en Sarge y en Woody aMule utils es incluido en el paquete base de aMule) mientras dpkg dejará aMule-utils instalado en el sistema (que en general, es una mala idea).

También, si instaló xmule o algún día piensa instalarlo, debe tener en mente esto: el [[ed2k command]] existe tanto en [[aMule]] como [[xMule]]. Usted podría querer ejecutar `type ed2k` para ver cuál [[ed2k command]] será ejecutado y renombrar el otro, entonces se asegura que nunca sea ejecutado por equivocación).

== Está terminando... ==

¡Esto es todo! Su propio [[aMule]] compilado está instalado en su sistema y listo para funcionar.

Para ejecutar [[aMule]], solamente escriba <code>"amule"</code>. Usted puede comprobar si todo está trabajado, escribiendo <code>"amule -v"</code> y comprueba si la versión mostrada está en correspondencia con la que usted compilo/instalo.

Si este Como no ayudara, usted tiene un problema raro en su sistema;-) Mire en http://www.amule.org ([http://www.amule.org/amule Foros de aMule] en http://forum.amule.org ) o nos visita en #amule en irc.freenode.net y (no lo dúde) trataremos de hacer todo lo posible para ayudarle.

== Notas finales ==

Si usted está en uno de aquellos casos raros cuando usted desea compilar [[aMule]] estáticamente, instalar también ''libtiff4-dev'' (por ''apt-get install libtiff4-dev''). De todos modos, esto '''NO''' es recomendado y de hecho, probablemente no hará ninguna mejora o hasta, no trabajan en nada.

HowTo Compile In Debian/Ubuntu

2006-01-10T08:53:54Z

Thedude0001: =aMule stable 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].

== 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-common
*amuled
*amule-remote-gui
*amuleweb
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

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...

== 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

2005-10-30T21:22:40Z

Thedude0001:

<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-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-common
*amuled
*amule-remote-gui
*amuleweb
*amulewebdlg
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

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...

== 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.

AMule devs

2005-10-24T17:11:06Z

Thedude0001: link added

== The [[aMule]] Project ==
The aMule project is led by a bunch of people (tho some rumours say they are monkeys) who toil away in front of their computers, so that you can enjoy a stable and featureful P2P client.
This page is about them.

== The Team ==
These are the people who work on aMule:

=== Developers ===
* [[User:deltaHF|deltaHF]]: Webmaster, Admin and from-time-to-time-coder ;)
* [[User:falso|falso]]: [[CAS]] coder.
* [[User:GonoszTopi|GonoszTopi]]: [[External Connections]] developer.
* [[User:Hetfield|Hetfield]]: Ex-Admin, pretty-no-free-time coder.
* [[User:Jacobo221|Jacobo221]]: Our man-for-all
* [[User:ken|Ken]]: The big [http://www.apple.com/macosx Mac] guy.
* [[User:Kry|Kry]]: Main developer and Admin
* [[User:lfroen|lfroen]]: Core/GUI dedicated guy.
* [[User:Phoenix|Phoenix]]: Code janitor junior.
* [[User:thepolish|thepolish]]: [[aMule]] [[FAQ_utils|tools]] coder.
* [[User:Unleashed|Unleashed]]: Sometimes around ;)
* [[User:Xaignar|Xaignar]]: Code janitor extraordinaire!

=== Testers ===
* [[User:Citroklar|Citroklar]]: Tester, slave-work-coder (sometimes)
* ender`: Tester
* [[User:lionel77|lionel77]]: Tester and provider of binaries for Mac OS
* nachbarnebenan: Tester, and life-complicator by using large&strange nicks ;-P
* nich: Tester
* skolnick: Solaris tester
* [[User:Stefanero|Stefanero]]: Supporter, Tester, and [[aMuleWeb]] Guru
* [[User:thedude0001|thedude0001]]: Tester

=== Special Gold Guest Members ===
* [[User:Bigbob|Bigbob]]: Also known as ''[[User:Bigbob|Creteil]]''; [[aMule]] project creator.
* [[User:Madcat|Madcat]]: The one and only kitty dev.
* [[User:Tiku|Tiku]]: And God said: Let there be [[lMule]]!

=== Others ===
* [[User:Bootstrap|bootstrap]]: [[IRC]] bot (''bootbox'') and [[aMule CVS]] hoster
* [[User:uberpenguin|uberpenguin]]: uberpenguin is extremely difficult to classify... Let us call him the 'official bystander to *mule'.
* niet: [http://www.dns.net/dnsrd DNS] stuff, [[XAS]], tester.

=== Former Team-members ===
These are people who have worked on [[aMule]] in the past.
Please note that this list doesn't include the people from before [[aMule]] forked off from [[xMule]], nor does it include people from the [[lMule]] days. If you wish to learn more about those, please visit the websites of those projects.

==== Developers ====
* shakraw: [[aMuleWeb]] mantainer.

==== Testers ====

== Helping ==
We can always use another helping hand, and if you are interested, then I'd encourage you to contact us and see if you can help us. Currently, what we need the most is developers and testers, though also translators and others.

=== Becoming a Developer ===
To become a [[aMule]] Developer (tm), you'll need, at the very least, a working knowledge of C++, since C++ is the language in which [[aMule]] is written. You'll also need to learn about the GUI toolkit used by [[aMule]]: [[wxWidgets]]. In addition, you are required to our [[Coding Style]] rules or we will beat you to death with a sockful of rocks. We do not require that you be an expert, only that you are willing to help and learn.

If you are interested, then simply drop by the [[IRC|IRC Channel]] and let us know. Currently, we use a private [http://www.gnu.org/software/cvs CVS] server, but after you've submitted a patch or two you can easily get r/w access to it. You can also post patches on the [http://www.amule-project.net/amule/board.php?boardid=47 Development] forum, however, virtually all discussions regarding development happens on [[IRC]].

We can especially use your skills if you are using one of the platforms: [http://www.unix.org Unix], *[http://www.bsd.org BSD], [http://www.sun.com/solaris Solaris], [http://www.apple.com Macs] and [http://www.microsoft.com/windows Windows]. If your operating system of choice isn't on that list, then perhaps you can contribute.

=== Becoming a Tester ===
We need people who are willing to create complete bug-reports, as the standard is pretty low regarding user reports. This is rather simple, but takes patience. Please contact us on [[IRC]] for more information and read [[Backtraces|this guide on creating useful backtraces]].

=== Becoming a Translator ===
[[aMule]] already includes translations for a number of languages, however, we'll always welcome more, and even if your language of choice has been done already, then perhaps you can help improve it. Please see the [http://forum.amule.org/board.php?boardid=40 Translations forum] for more information on current translations, or contact us on [[IRC]]. Also, take a look at the [[Translations|aMule translation howto]].

BTW, you can also help with [[Translating_Wiki|translating aMule wiki]] articles. There's always lots of work to do. =)

HowTo Compile In Debian/Ubuntu

2005-10-01T21:00:36Z

Thedude0001: =aMule CVS 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].

== 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 ===

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>

'''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 ===

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

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

'''NOTE:''' The second line is necessary for Sarge users and strongly recommended for Sid users.

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-common
*amuled
*amule-remote-gui
*amuleweb
*amulewebdlg
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

'''[[aMule]] stable'''
*amule-daemon
*amule-gui-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)
*amule-utils (metapackage for amule-gui-utils and amule-console-utils)

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...

== Notes before starting ==

'''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 unable to install the wxGTK, wxbase and Crypto++ libraries since they were not available in the current minimum compatible versions (2.4.2 and 2.5.1 respectively) when Woody was released.''

''The best for Woody users is to switch to the Sarge or Sid branch. That can be done with the following command (again, you must be root)''

perl -pi.$$ -e "s/(\bstable|woody)/testing/g" /etc/apt/sources.list

''or''

perl -pi.$$ -e "s/(\bstable|woody)/sarge/g" /etc/apt/sources.list

''to switch to the Sarge/testing branch, or with''

perl -pi.$$ -e "s/(\bstable|woody)/unstable/g" /etc/apt/sources.list
''or''

perl -pi.$$ -e "s/(\bstable|woody)/sid/g" /etc/apt/sources.list

''to switch to the Sid/unstable branch.''

''If Woody users are not be interested in switching to Sarge they will need to download Woody-backported debian packages by adding the following line to /etc/apt/sources.list (remember to <code>"apt-get update"</code> after adding this line):''

deb <nowiki>http://debian.thermoman.de/</nowiki> woody wxwindows2.4 libcrypto++

''What's more, [http://www.thermoman.de thermoman] stopped working on the [[aMule]] backports for [http://www.debian.org Woody] on the [[aMule]] 2.0.0-rc5 release, so newer [[aMule]] releases backports are unavailable. Sorry.''

'''''Note 3:''' Sarge users won't have any dependecy problems any longer, since both crypto++ and wxWidgets have both been in Sarge for some time now. So there's no longer any need to update ''sources.list'' on Debian Sarge distributions.''

'''''Note 4:''' 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 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.''

'''''Note 7:''' Woody users will most probably be unable to get libgd2-xpm-dev and libcurl3-dev since those packages aren't available for Woody. For libcurl3-dev you can just install libcurl2-dev and go on, everything will be ok For libgd2-xpm, at the moment there is no backport available but, since this library is only used by CAS (and suggested, not even required), it won't give any problems on compilation time. Just be aware that <code>cas -o</code> won't work.''

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 8:''' 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 9:''' 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>.''

== 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 10:''' 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 11:''' Please take a look at the [[configure|configure article]].''

'''''Note 12:''' 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 13:''' 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

2005-09-20T18:00:18Z

Thedude0001: =aMule stable 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].

== 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 ===

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>

'''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. 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 ===

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

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

'''NOTE:''' The second line is necessary for Sarge users and strongly recommended for Sid users.

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-common
*amuled
*amule-remote-gui
*amuleweb
*amulewebdlg
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

'''[[aMule]] stable'''
*amule-daemon
*amule-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)

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...

== Notes before starting ==

'''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 unable to install the wxGTK, wxbase and Crypto++ libraries since they were not available in the current minimum compatible versions (2.4.2 and 2.5.1 respectively) when Woody was released.''

''The best for Woody users is to switch to the Sarge or Sid branch. That can be done with the following command (again, you must be root)''

perl -pi.$$ -e "s/(\bstable|woody)/testing/g" /etc/apt/sources.list

''or''

perl -pi.$$ -e "s/(\bstable|woody)/sarge/g" /etc/apt/sources.list

''to switch to the Sarge/testing branch, or with''

perl -pi.$$ -e "s/(\bstable|woody)/unstable/g" /etc/apt/sources.list
''or''

perl -pi.$$ -e "s/(\bstable|woody)/sid/g" /etc/apt/sources.list

''to switch to the Sid/unstable branch.''

''If Woody users are not be interested in switching to Sarge they will need to download Woody-backported debian packages by adding the following line to /etc/apt/sources.list (remember to <code>"apt-get update"</code> after adding this line):''

deb <nowiki>http://debian.thermoman.de/</nowiki> woody wxwindows2.4 libcrypto++

''What's more, [http://www.thermoman.de thermoman] stopped working on the [[aMule]] backports for [http://www.debian.org Woody] on the [[aMule]] 2.0.0-rc5 release, so newer [[aMule]] releases backports are unavailable. Sorry.''

'''''Note 3:''' Sarge users won't have any dependecy problems any longer, since both crypto++ and wxWidgets have both been in Sarge for some time now. So there's no longer any need to update ''sources.list'' on Debian Sarge distributions.''

'''''Note 4:''' 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 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.''

'''''Note 7:''' Woody users will most probably be unable to get libgd2-xpm-dev and libcurl3-dev since those packages aren't available for Woody. For libcurl3-dev you can just install libcurl2-dev and go on, everything will be ok For libgd2-xpm, at the moment there is no backport available but, since this library is only used by CAS (and suggested, not even required), it won't give any problems on compilation time. Just be aware that <code>cas -o</code> won't work.''

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 8:''' 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 9:''' 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>.''

== 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 10:''' 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 11:''' Please take a look at the [[configure|configure article]].''

'''''Note 12:''' 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 13:''' 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

2005-08-31T09:43:20Z

Thedude0001: =aMule stable 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].

== 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 ===

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://dude.gemil.de/ debian/

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

'''NOTE:''' 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.

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

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

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

'''NOTE:''' The second line is necessary for Sarge users and strongly recommended for Sid users.

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-common
*amuled
*amule-remote-gui
*amuleweb
*amulewebdlg
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

'''[[aMule]] stable'''
*amule-daemon
*amule-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)

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...

== Notes before starting ==

'''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 unable to install the wxGTK, wxbase and Crypto++ libraries since they were not available in the current minimum compatible versions (2.4.2 and 2.5.1 respectively) when Woody was released.''

''The best for Woody users is to switch to the Sarge or Sid branch. That can be done with the following command (again, you must be root)''

perl -pi.$$ -e "s/(\bstable|woody)/testing/g" /etc/apt/sources.list

''or''

perl -pi.$$ -e "s/(\bstable|woody)/sarge/g" /etc/apt/sources.list

''to switch to the Sarge/testing branch, or with''

perl -pi.$$ -e "s/(\bstable|woody)/unstable/g" /etc/apt/sources.list
''or''

perl -pi.$$ -e "s/(\bstable|woody)/sid/g" /etc/apt/sources.list

''to switch to the Sid/unstable branch.''

''If Woody users are not be interested in switching to Sarge they will need to download Woody-backported debian packages by adding the following line to /etc/apt/sources.list (remember to <code>"apt-get update"</code> after adding this line):''

deb <nowiki>http://debian.thermoman.de/</nowiki> woody wxwindows2.4 libcrypto++

''What's more, [http://www.thermoman.de thermoman] stopped working on the [[aMule]] backports for [http://www.debian.org Woody] on the [[aMule]] 2.0.0-rc5 release, so newer [[aMule]] releases backports are unavailable. Sorry.''

'''''Note 3:''' Sarge users won't have any dependecy problems any longer, since both crypto++ and wxWidgets have both been in Sarge for some time now. So there's no longer any need to update ''sources.list'' on Debian Sarge distributions.''

'''''Note 4:''' 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 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.''

'''''Note 7:''' Woody users will most probably be unable to get libgd2-xpm-dev and libcurl3-dev since those packages aren't available for Woody. For libcurl3-dev you can just install libcurl2-dev and go on, everything will be ok For libgd2-xpm, at the moment there is no backport available but, since this library is only used by CAS (and suggested, not even required), it won't give any problems on compilation time. Just be aware that <code>cas -o</code> won't work.''

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 8:''' 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 9:''' 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>.''

== 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 10:''' 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 11:''' Please take a look at the [[configure|configure article]].''

'''''Note 12:''' 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 13:''' 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.

AMule is slow-de

2005-08-13T18:40:46Z

Thedude0001: =Schuld des Netzwerkes=

<center>'''Deutsche''' | [[AMule_is_slow|English]] | [[AMule_is_slow-it|Italiano]] | [[AMule_is_slow-nl|Nederlands]] | [[AMule_is_slow-es|Español]] | [[AMule_is_slow-hu|Magyar]]</center>
== [[aMule]] ist langsam ==

[[aMule]] ist langsam? Folgendes ist möglich:

*[[#Deine Schuld|Deine Schuld]]
*[[#Schuld des Netzwerkes|Schuld des Netzwerkes]]

== Deine Schuld ==

Dies ist eine Liste mit Möglichkeiten, die für Deine langsame Download-Geschwindigkeit verantwortlich sein könnten:

*Ein niedriger Wert unter "Einstellungen"->"Download-Limit"
*Ein niedriger Wert unter "Einstellungen"->"Upload-Limit". Wenn das Upload-Limit niedriger als 4 KB/s ist, wird die Download-Geschwindigkeit auf das dreifache des eingestellten Uploads begrenzt. Wenn die Upload-Begrenzung kleiner als zehn, aber größer als vier ist, wird die Download-Geschwindigkeit auf das vierfache des Uploads begrenzt. Upload-Begrenzungen die gleich oder größer zehn sind erlauben einen unbegrenzten Download, der nur durch das "Download-Limit" begrenzt wird. (Lese [[FAQ_eD2k-Kademlia-de##Gibt_es_Grenzen_im_ED2k-Netzwerk?|diese Seite]] um mehr darüber zu erfahren).
*Ein zu hohen Wert unter "Einstellungen"->"Upload-Limit". Deine Verbindung könnte verstopfen! (Es hängt von Deiner Verbindungs-Geschwindigkeit ab.)
*Ein zu niedriger Wert unter "Einstellungen"->"Max Verbindungen". Es sind nicht genügend Verbindungen verfügbar.
*Ein zu hoher Wert unter "Einstellungen"->"Max Verbindungen". Zu viele Verbindungen verstopfen Deinen Internetzugang.
*Ein zu niedriger Wert unter "Erweiterte Einstellungen"->"Neue Verbindungen". Es dauert sehr lange [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quellen]] zu erreichen.
*Ein zu hoher Wert unter "Erweiterte Einstellungen"->"Neue Verbindungen". Dein Internetzugang wird verstopft, viele neue Verbindungen erzeugen viel Overhead.
*Eine [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|Low-ID]] zu haben.
*Einige [http://de.wikipedia.org/wiki/Internetdienstanbieter ISPs] blockieren oder begrenzen Verbindungen zu den Standard-[[FAQ_eD2k-Kademlia#Was_ist_ED2K?|eD2k]]-[[FAQ_eD2k-Kademlia-de#Welche_Ports_m%C3%BCssen_in_einer_Firewall_oder_einem_Router_f%C3%BCr_aMule_konfiguriert_werden?|Ports]]. Versuche den Port unter "Einstellungen"->"Verbindung" zu verändern.
*Deine Firewall könnte einige Ports blockieren, die von [[aMule]] benutzt werden, oder Du hast die Ports in Deinem Router nicht weiterleiten lassen. (Wie bereits erwähnt, lese [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|Low-ID]])

== Schuld des Netzwerkes ==

Langsame Download-Geschwindigkeiten liegen nicht immer an einer falschen Konfiguration oder fehlerhaftem amule-Code. Einige Faktoren können unabhängig davon auch noch eine Rolle spielen:

*[[FAQ_eD2k-Kademlia#Was_ist_ED2K?|eD2k]] ist ein langsames Netzwerk; Das [[FAQ_eD2k-Kademlia#Was_ist_ED2K?|eD2k]]-Netzwerk ist eines der größten existierenden [http://de.wikipedia.org/wiki/Peer-to-Peer P2P]-Netzwerke, jedoch liegt das Hauptziel in der Verfügbarkeit von Daten. Während Du mit anderen verbreiteten Netzwerken schneller Deine Downloads fertig stellst, wirst Du schnell erkennen, dass das eD2k-Netzwerk die Heimat von Millionen von Dateien ist, die Du in keinem anderen Netzwerk findest.
*[[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Kredits]]; Wenn Du aMule das erste mal laufen lässt oder wenn Du die Dateien im ~/.aMule-Verzeichnis löscht, besitzt Du keine [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Kredits]]. [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Kredits]] garantieren schnellere Downloads. Wenn Du nicht weißt, worum es sich dabei handelt, klicke [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|hier]].
*Verbreitung von Dateien; Seltene, alte oder sehr neue Dateien haben sehr wenige [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quellen]], so das es länger dauert bis aMule von den wenigen verfügbaren Benutzern downloaden kann.
*Lange [[queue|Warteschlangen]]; eMule, genauso wie die meisten seiner Abkömmlinge, verwendet lange [[queue|Warteschlangen]]. aMule begrenzt die [[queue|Warteschlange]] standardmäßig auf 5000. Das garantiert, dass Benutzer nicht durch andere [[Client-de|Clients]] benachteiligt werden, die häufig wiederholt die [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quelle]] anfordern (Das war ein wirkliches Problem in der Zeit vor [http://de.wikipedia.org/wiki/EMule eMule]). Man muss bereit sein in der Schlange zu warten und dies kann für einen neuen Benutzer ohne [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Kredits]] sehr lange dauern. Manchmal muß man auch mal zwei Wochen auf die Fertigstellung eines Downloads warten, zum Beispiel für eine, für die nur eine Quelle existiert.
*Lies die [[FAQ network|Netzwerk FAQ]].

AMule is slow-de

2005-08-13T18:39:30Z

Thedude0001: =Schuld des Netzwerkes=

<center>'''Deutsche''' | [[AMule_is_slow|English]] | [[AMule_is_slow-it|Italiano]] | [[AMule_is_slow-nl|Nederlands]] | [[AMule_is_slow-es|Español]] | [[AMule_is_slow-hu|Magyar]]</center>
== [[aMule]] ist langsam ==

[[aMule]] ist langsam? Folgendes ist möglich:

*[[#Deine Schuld|Deine Schuld]]
*[[#Schuld des Netzwerkes|Schuld des Netzwerkes]]

== Deine Schuld ==

Dies ist eine Liste mit Möglichkeiten, die für Deine langsame Download-Geschwindigkeit verantwortlich sein könnten:

*Ein niedriger Wert unter "Einstellungen"->"Download-Limit"
*Ein niedriger Wert unter "Einstellungen"->"Upload-Limit". Wenn das Upload-Limit niedriger als 4 KB/s ist, wird die Download-Geschwindigkeit auf das dreifache des eingestellten Uploads begrenzt. Wenn die Upload-Begrenzung kleiner als zehn, aber größer als vier ist, wird die Download-Geschwindigkeit auf das vierfache des Uploads begrenzt. Upload-Begrenzungen die gleich oder größer zehn sind erlauben einen unbegrenzten Download, der nur durch das "Download-Limit" begrenzt wird. (Lese [[FAQ_eD2k-Kademlia-de##Gibt_es_Grenzen_im_ED2k-Netzwerk?|diese Seite]] um mehr darüber zu erfahren).
*Ein zu hohen Wert unter "Einstellungen"->"Upload-Limit". Deine Verbindung könnte verstopfen! (Es hängt von Deiner Verbindungs-Geschwindigkeit ab.)
*Ein zu niedriger Wert unter "Einstellungen"->"Max Verbindungen". Es sind nicht genügend Verbindungen verfügbar.
*Ein zu hoher Wert unter "Einstellungen"->"Max Verbindungen". Zu viele Verbindungen verstopfen Deinen Internetzugang.
*Ein zu niedriger Wert unter "Erweiterte Einstellungen"->"Neue Verbindungen". Es dauert sehr lange [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quellen]] zu erreichen.
*Ein zu hoher Wert unter "Erweiterte Einstellungen"->"Neue Verbindungen". Dein Internetzugang wird verstopft, viele neue Verbindungen erzeugen viel Overhead.
*Eine [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|Low-ID]] zu haben.
*Einige [http://de.wikipedia.org/wiki/Internetdienstanbieter ISPs] blockieren oder begrenzen Verbindungen zu den Standard-[[FAQ_eD2k-Kademlia#Was_ist_ED2K?|eD2k]]-[[FAQ_eD2k-Kademlia-de#Welche_Ports_m%C3%BCssen_in_einer_Firewall_oder_einem_Router_f%C3%BCr_aMule_konfiguriert_werden?|Ports]]. Versuche den Port unter "Einstellungen"->"Verbindung" zu verändern.
*Deine Firewall könnte einige Ports blockieren, die von [[aMule]] benutzt werden, oder Du hast die Ports in Deinem Router nicht weiterleiten lassen. (Wie bereits erwähnt, lese [[FAQ_eD2k-Kademlia-de#Was_sind_niedrige_und_hohe_IDs?|Low-ID]])

== Schuld des Netzwerkes ==

Wir mögen es nicht Dir mitteilen zu müssen, dass die langsame Download-Geschwindigkeit nicht immer etwas mit fehlerhaften [[aMule]]-Code oder einer falschen Konfiguration zu tun hat. Einige Faktoren könnten unabhängig von diesen auch noch eine Rolle spielen:

*[[FAQ_eD2k-Kademlia#Was_ist_ED2K?|eD2k]] ist ein langsames Netzwerk; Das [[FAQ_eD2k-Kademlia#Was_ist_ED2K?|eD2k]]-Netzwerk ist eines der größten existierenden [http://de.wikipedia.org/wiki/Peer-to-Peer P2P]-Netzwerke, jedoch liegt das Hauptziel in der Verfügbarkeit von Daten. Während Du mit anderen verbreiteten Netzwerken schneller Deine Downloads fertig stellst, wirst Du schnell erkennen, dass das eD2k-Netzwerk die Heimat von Millionen von Dateien ist, die Du in keinem anderen Netzwerk findest.
*[[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Kredits]]; Wenn Du aMule das erste mal laufen lässt oder wenn Du die Dateien im ~/.aMule-Verzeichnis löscht, besitzt Du keine [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Kredits]]. [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Kredits]] garantieren schnellere Downloads. Wenn Du nicht weißt, worum es sich dabei handelt, klicke [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|hier]].
*Verbreitung von Dateien; Seltene, alte oder sehr neue Dateien haben sehr wenige [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quellen]], so das es länger dauert bis aMule von den wenigen verfügbaren Benutzern downloaden kann.
*Lange [[queue|Warteschlangen]]; eMule, genauso wie die meisten seiner Abkömmlinge, verwendet lange [[queue|Warteschlangen]]. aMule begrenzt die [[queue|Warteschlange]] standardmäßig auf 5000. Das garantiert, dass Benutzer nicht durch andere [[Client-de|Clients]] benachteiligt werden, die häufig wiederholt die [[FAQ_eD2k-Kademlia-de#Was_ist_eine_Quelle?|Quelle]] anfordern (Das war ein wirkliches Problem in der Zeit vor [http://de.wikipedia.org/wiki/EMule eMule]). Man muss bereit sein in der Schlange zu warten und dies kann für einen neuen Benutzer ohne [[FAQ_eD2k-Kademlia-de#Was_hat_es_mit_diesem_ganzen_Krempel_(Credits,_Bewertungen,_Ratings,_Warteschlangen)_auf_sich?|Kredits]] sehr lange dauern. Manchmal muß man auch mal zwei Wochen auf die Fertigstellung eines Downloads warten, zum Beispiel für eine, für die nur eine Quelle existiert.
*Lies die [[FAQ network|Netzwerk FAQ]].

HowTo Compile In Debian/Ubuntu

2005-07-18T01:30:51Z

Thedude0001: =aMule CVS release=

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 ===

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://dude.gemil.de/ debian/

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

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

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

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

'''NOTE:''' The second line is necessary for Sarge users and strongly recommended for Sid users.

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-common
*amuled
*amule-remote-gui
*amuleweb
*amulewebdlg
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

'''[[aMule]] stable'''
*amule-daemon
*amule-utils (alc, wxcas)
*amule-console-utils (amuleweb, alcc, cas)

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...

== Notes before starting ==

'''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 unable to install the wxGTK, wxbase and Crypto++ libraries since they were not available in the current minimum compatible versions (2.4.2 and 2.5.1 respectively) when Woody was released.''

''The best for Woody users is to switch to the Sarge or Sid branch. That can be done with the following command (again, you must be root)''

perl -pi.$$ -e "s/(\bstable|woody)/testing/g" /etc/apt/sources.list

''or''

perl -pi.$$ -e "s/(\bstable|woody)/sarge/g" /etc/apt/sources.list

''to switch to the Sarge/testing branch, or with''

perl -pi.$$ -e "s/(\bstable|woody)/unstable/g" /etc/apt/sources.list
''or''

perl -pi.$$ -e "s/(\bstable|woody)/sid/g" /etc/apt/sources.list

''to switch to the Sid/unstable branch.''

''If Woody users are not be interested in switching to Sarge they will need to download Woody-backported debian packages by adding the following line to /etc/apt/sources.list (remember to <code>"apt-get update"</code> after adding this line):''

deb <nowiki>http://debian.thermoman.de/</nowiki> woody wxwindows2.4 libcrypto++

''What's more, [http://www.thermoman.de thermoman] stopped working on the [[aMule]] backports for [http://www.debian.org Woody] on the [[aMule]] 2.0.0-rc5 release, so newer [[aMule]] releases backports are unavailable. Sorry.''

'''''Note 3:''' Sarge users won't have any dependecy problems any longer, since both crypto++ and wxWidgets have both been in Sarge for some time now. So there's no longer any need to update ''sources.list'' on Debian Sarge distributions.''

'''''Note 4:''' 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 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.''

'''''Note 7:''' Woody users will most probably be unable to get libgd2-xpm-dev and libcurl3-dev since those packages aren't available for Woody. For libcurl3-dev you can just install libcurl2-dev and go on, everything will be ok For libgd2-xpm, at the moment there is no backport available but, since this library is only used by CAS (and suggested, not even required), it won't give any problems on compilation time. Just be aware that <code>cas -o</code> won't work.''

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 8:''' 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 1.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 9:''' 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>.''

== 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 10:''' 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 11:''' Please take a look at the [[configure|configure article]].''

'''''Note 12:''' 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 13:''' 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

2005-07-17T18:44:45Z

Thedude0001: =aMule CVS release=

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 ===

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://dude.gemil.de/ debian/

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

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

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

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

'''NOTE:''' The second line is necessary for Sarge users and strongly recommended for Sid users.

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-common
*amuled
*amule-remote-gui
*amuleweb
*amulewebdlg
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

'''[[aMule]] stable'''
*amule-daemon
*amule-utils
*amule-console-utils

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...

== Notes before starting ==

'''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 unable to install the wxGTK, wxbase and Crypto++ libraries since they were not available in the current minimum compatible versions (2.4.2 and 2.5.1 respectively) when Woody was released.''

''The best for Woody users is to switch to the Sarge or Sid branch. That can be done with the following command (again, you must be root)''

perl -pi.$$ -e "s/(\bstable|woody)/testing/g" /etc/apt/sources.list

''or''

perl -pi.$$ -e "s/(\bstable|woody)/sarge/g" /etc/apt/sources.list

''to switch to the Sarge/testing branch, or with''

perl -pi.$$ -e "s/(\bstable|woody)/unstable/g" /etc/apt/sources.list
''or''

perl -pi.$$ -e "s/(\bstable|woody)/sid/g" /etc/apt/sources.list

''to switch to the Sid/unstable branch.''

''If Woody users are not be interested in switching to Sarge they will need to download Woody-backported debian packages by adding the following line to /etc/apt/sources.list (remember to <code>"apt-get update"</code> after adding this line):''

deb <nowiki>http://debian.thermoman.de/</nowiki> woody wxwindows2.4 libcrypto++

''What's more, [http://www.thermoman.de thermoman] stopped working on the [[aMule]] backports for [http://www.debian.org Woody] on the [[aMule]] 2.0.0-rc5 release, so newer [[aMule]] releases backports are unavailable. Sorry.''

'''''Note 3:''' Sarge users won't have any dependecy problems any longer, since both crypto++ and wxWidgets have both been in Sarge for some time now. So there's no longer any need to update ''sources.list'' on Debian Sarge distributions.''

'''''Note 4:''' 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 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.''

'''''Note 7:''' Woody users will most probably be unable to get libgd2-xpm-dev and libcurl3-dev since those packages aren't available for Woody. For libcurl3-dev you can just install libcurl2-dev and go on, everything will be ok For libgd2-xpm, at the moment there is no backport available but, since this library is only used by CAS (and suggested, not even required), it won't give any problems on compilation time. Just be aware that <code>cas -o</code> won't work.''

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 8:''' 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 1.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 9:''' 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>.''

== 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 10:''' 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 11:''' Please take a look at the [[configure|configure article]].''

'''''Note 12:''' 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 13:''' 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 on Win32 with MinGW

2005-05-25T13:04:53Z

Thedude0001: typo

<center><h2>Originally by '''Madcat'''</h2></center>

This wiki page only supports the latest [[aMule_CVS|CVS]] version of [[aMule]].

== List of things you need to compile [[aMule]] ==

'''Note:''' Some of these require manually moving includes/libs into the right directories.

[http://www.microsoft.com/windows Windows] port of [http://gcc.gnu.org GNU C compiler] -> [http://prdownloads.sf.net/mingw/MinGW-3.1.0-1.exe?download Download]

Minimal [http://www.gnu.org GNU] shell for [http://www.microsoft.com/windows Windows] -> [http://prdownloads.sf.net/mingw/MSYS-1.0.10.exe?download Download]

Developer toolkit for [http://www.mingw.org/msys.shtml MSys] (for [http://www.gnu.org/software/cvs CVS] & co) -> [http://prdownloads.sf.net/mingw/msysDTK-1.0.1.exe?download Download]

[http://www.gnu.org/software/libiconv LibIConv] (required by [http://www.gnu.org/software/gettext gettext]) ->
[http://prdownloads.sf.net/mingw/libiconv-1.8.0-2003.02.01-1.exe?download Download]

[http://www.gnu.org/software/gettext GetText] (for [http://www.gnu.org/software/gettext po files], [http://www.gnu.org/software/automake/automake.html autogen.sh], etc) ->
[http://prdownloads.sf.net/mingw/gettext-0.11.5-2003.02.01-1.exe?download Download]

[http://www.zlib.org zlib] compression library ->
[http://www.zlib.net/zlib-1.2.2.tar.gz Download]

[http://www.microsoft.com/windows Windows] port of [[wxWidgets]] library ->
[http://prdownloads.sourceforge.net/wxwindows/wxMSW-2.6.0.zip Download]

== Common guidelines, issues, solutions ==

When compiling [[wxWidgets]], you should make use of the following configure flags:
''--disable-shared --without-checklistbox''

Link statically against ''[http://www.zlib.org zlib]'' to avoid distributing extranous DLLs (and generally make life simpler).

== Compilation ==

The compilation itself is actually just a matter of following the usual method: ''./configure && make''

However, [http://www.zlib.org zlib] detection might fail. If that's the case, you need to add ''--with-zlib=/local/'' to your configure flags.

== Compiling with [http://www.parinya.ca/mingwstudio.html MinGW Studio] ==

'''NOTE:''' The compilation with [http://www.parinya.ca/mingwstudio.html MinGW Studio] is deprecated right now and currently does not function. It might function again in the future.

As of 2004/07/17, you can find, in [http://www.gnu.org/software/cvs CVS], the file ''amule.msp'' which is the project file relative to the [http://www.parinya.ca/mingwstudio.html MinGW Studio] IDE ([http://www.gnu.org/philosophy/free-sw.html Free] and under [http://www.gnu.org/copyleft/gpl.html GPL] at http://www.parinya.ca/ and shipped with precompiled [[wxWidgets|wxMSW]]).

Install [http://www.parinya.ca/mingwstudio.html MinGW Studio], add [http://www.zlib.org Zlib] and [http://curl.haxx.se Curl] compiled libs in The [http://www.parinya.ca/mingwstudio.html MinGW Studio] tree.

Then, open ''amule.msp'' with [http://www.parinya.ca/mingwstudio.html MinGW Studio], press '''F7''', and [[aMule]] "should" be compiled :)

Yes, I know, "compile" is not the same as "work" ... But it is a great begining

HowTo compile on Solaris

2005-03-20T15:35:53Z

Thedude0001: Initial copy from forum post

I just wrote this little guide to help you all solaris fans. Hope this helps!

COMPILING AMULE/AMULEWEB ON SOLARIS 10 x86

*Install the pkg-get script from http://www.blastwave.org/pkg-get.php

*Use the pkg-get script to install some required libraries, which do not come with solaris:
autoconf
automake
gd
gettext
gtk/gtk2
libpng
These packages will install to /opt/csw tree

*Set your path like this:
PATH=/usr/local/bin:/opt/csw/bin:/usr/sfw/bin:/usr/bin

*Simlink the GNU utilities in /usr/sfw/bin to their "right" names (gar=ar, gas=as, gld=ld, gmake=make, ggrep=grep,
gtar=tar, etc...) somewhere in your path. I simlinked them to their same directory (/usr/sfw/bin)

*Now, get the latest wxGTK package from www.wxwidgets.org and compile it. Install it to /usr/local. I have not
tried compiling it with unicode support, nor against GTK2, so basically this is untested. But should work.

*Get the latest amule CVS from http://amule.hirnriss.net and uncompress it somewhere.

*Set these two environment wariables:
CPPFLAGS='-I /opt/csw/include'
LD_LIBRARY_PATH=/usr/local/lib:/opt/csw/lib:/usr/sfw/lib:/usr/lib

*Configure amule like this:
./configure --enable-webserver

*Type "make" (without the quotation marks), press <ENTER> and hope for the best.

*If compilation went OK, you can now run amule!
./src/amule
*ENJOY!

This guide was used for compiling amule and amuleweb on Solaris 10 FCS, I have no idea if it will work or not on
previous/later solaris releases, but it should. Also, if you got amule compiled on other solaris than 10, please tell me how you did, or if this guide worked for you or any extra things you had to do, etc.

WRITTEN BY Skolnick on March 6/2005

Thanks goes to all the amule dev team, specially Kry, who helped me a lot, and ken for the CPPFLAGS tip.

Little endian

2005-03-15T12:28:57Z

Thedude0001: =Example= typo

== Introduction to [[endian]]ness ==

Having read the [[endian]]ness article, you might already have an idea of what this is for.

The [[endian]]ess defines the bytes' order in physical memory.

== Definition ==

When you must store a two-bytes (or larger) value in memory, you can either store the first byte(s) in the first place or the second byte(s) in the first place.

Little [[endian]] defines that the first bytes will go first.

== Example ==

An example of a two-bytes number is 65534. This number requires two bytes to be stored in memory. The decimal number 65534 is represented, in hexadecimal, as FFFE (or 0xFFFE). Here we can see the two bytes: FF and FE.

We can decide wether we want to place the FF byte first in memory or the FE byte first.

Little [[endian]] tells us to place first the which whose numbers have less weight in the total number. That is FF, since FE here represents 254, while FF represents 65280.

So, physically in memory we would have:

_________________________
Memory Graph: |_____FE_____|_____FF_____|
Memory Possitions: 000001 000002

== Uses ==

This [[endian]]ness is used (amongst others) in [http://www.intel.com x86], in [http://www.x86-64.org AMD64] and in [http://h18002.www1.hp.com/alphaserver/vax VAX] machines.

== Notes ==

To understand better the little [[endian]] concept it is helpful to compare it to the [[big endian]] concept.

Bug tracker

2005-03-15T12:22:45Z

Thedude0001: typo

The [http://bugs.amule.org aMule Bug Tracker] is where you should post your ''complains'' about [[aMule]].

For suggestions, tips or any other stuff, please refer to [[aMule]]'s [[forum]]s or to [[aMule]]'s [[IRC]] channel.

Webserver

2005-03-02T14:20:30Z

Thedude0001: =Webserver with aMule 2.0.0-rc1 or later=

== Setting up [[aMuleWeb|Webserver]] with [[aMule]] ==

=== [[Webserver-1.2.x|Webserver with aMule 1.2.8 or earlier]] ===

=== Webserver with [[aMule]] 2.0.0-rc1 or later ===

*[http://www.gnu.org/software/tar/tar.html Untar] the sources and copy '''''src/aMule.tmpl''''' and '''''src/webserver/''''' into your '''''~/.aMule/''''' directory. The following (run from the sources directory), should do so:
:''$ cp -r src/aMule.tmpl src/webserver/ ~/.aMule/''

* If you installed [[aMule]] from rpm, then you can do:
:''$ cp /usr/share/amuleweb/aMule.tmpl ~/.aMule/''
:''$ cp -r /usr/share/amuleweb/webserver/ ~/.aMule/''

*Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
**Enable "Accept External Connections".
**Enable "Use TCP ports instead of unix local sockets".
**Enter a password for external connections. If you don't do this, amuleweb will not communicate with amule.

:'''NOTE:''' On some early [[aMule]] 2.0.0-rcX versions the above options weren't available (or didn't work). Use this if you want to run amuled, too. If you are using such [[aMule]] version and you don't wish to upgrade, then do the following:

:Shutdown [[aMule]] if it is still running.
:Edit your ''~/.eMule'' file, locate the ''[ExternalConnect]'' section and change:
::''AcceptExternalConnections=1'' <-- To enable [[aMule]] listening for [[External Connections]].
::''ECUseTCPPort=1'' <-- To use the [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] port. Very important since [http://www.unix.org Unix] sockets are disabled.
::''ECPassword=ca3c365274907c6fd527068788e14639'' <-- To find the MD5 string for your password, do:
:::''$ echo -n yourpasswordhere | md5sum | cut -d ' ' -f 1''
:::''ca3c365274907c6fd527068788e14639''

*Restart [[aMule]]

*Go to your "Preferences"->"Remote Controls" (in [[aMule]]) and setup your passwords here for [[External Connections]] and [[aMuleWeb|webserver]] login.
::'''NOTE:''' When you change your [[aMuleWeb|webserver]] and [[External Connections]] ports here, make sure to restart [[aMule]].
::'''NOTE:''' that ''"Enable [[aMuleWeb|Webserver]]"'' has no effect and will be renamed in 2.0.0rc8. [[aMuleWeb|Webserver]] is always enabled as long as you have [[External Connections]] enabled.
::'''NOTE:''' For users running [[aMuled|aMule Daemon]] you have to edit the ''.eMule'' file like shown above. For a way to setup a password check the [[Webserver-1.2.x|1.2.8 aMule HowTo]]. You can still do it in the same way.

*Now you're done! You are ready to run [[aMuleWeb|amuleweb]] and connect to it.

'''[[User:Stefanero|Stefanero]]'''

=== Webserver with [[aMule]] 2.0.0 or later (starting from CVS 2005.02.27) ===

*For users running the monotlithic [[aMule]] application:
**Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
***Enable "Accept External Connections".
***Enable "Use TCP ports instead of unix local sockets".
***Enter a password for external connections. If you don't do this, amuleweb will not communicate with amule.
::'''NOTE:''' When you change your [[aMuleWeb|webserver]] and [[External Connections]] ports here, make sure to restart [[aMule]].

*For users running the [[aMule|aMule daemon]]:
**Shutdown [[aMule|aMuled]] if it is still running.
**Edit your ''~/.eMule'' file, locate the ''[ExternalConnect]'' section and change:
***''AcceptExternalConnections=1'' <-- To enable [[aMule]] listening for [[External Connections]].
***''ECUseTCPPort=1'' <-- To use the [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] port. Very important since [http://www.unix.org Unix] sockets are disabled.
***''ECPassword=ca3c365274907c6fd527068788e14639'' <-- To find the MD5 string for your password, do:
:::''$ echo -n yourpasswordhere | md5sum | cut -d ' ' -f 1''
:::''ca3c365274907c6fd527068788e14639''
*Restart [[aMule|aMuled]]

'''NOTE:''' In [[aMule]] version 2.0.0 and later you don't need to do any copy/link of [[aMuleWeb|webserver]] files.

Thanks to [[User:Stefanero|Stefanero]], from who I shamelessly stole a lot from his tutorial.

==== Skin support ====

[[aMuleWeb|Webserver]] now looks for its files in a number of places:
*In your home directory: ''$HOME/.aMule/webserver/''[skin name]''/''
*And at it's install location, in this order.

Default skin (template) name is 'default'.

If, '''after installing''' [[aMule]], [[aMuleWeb|webserver]] refuses to run because of not being able to load template:
*please report this situation to us, and then
*create the directories ''webserver/default'' in the ''.aMule'' subdirectory of your home directory, and copy the contents of the ''src/webserver'' directory there from the [[aMule]] tarball (I mean to ''$HOME/.aMule/webserver/default''). [New record, four 'directory' word in one sentence :)]

'''[[User:GonoszTopi|GonoszTopi]]'''

== Connecting to [[aMuleWeb|amuleweb]] ==

To run [[aMuleWeb]] run '''''amuleweb''''' on a terminal. For more information about running [[aMuleWeb]] check the [[aMuleWeb|aMuleWeb document]].

Once [[aMuleWeb]] is running, open a web browser and connect to:

''http://host:port''

where ''host'' stands for your host's name (try with ''localhost'') and port stands for the [[aMuleWeb]] port ('''NOT''' the [[External Connections]] port).

For example: ''http://localhost:4711''

== Standard ports ==

The ports can be set to anything, but this are the most used (the standard ones):

*[[External Connections]]: 4712
*[[aMuleWeb|amuleweb]]: 4711

Make sure you do not confuse with what each of them is.

== Where to report problems and questions? ==

For Problems or Questions just report on http://forum.amule.org forum or join [[IRC]] channel [irc://irc.freenode.net/amule #amule] at [irc://irc.freenode.net irc.freenode.net]

FAQ network

2005-02-27T16:46:38Z

Thedude0001: mail adress

=Network speed: what you should know before asking questions=
by Froenchenko Leonid, lfroen@gmail.com

==Preface==
The purpose of this document is to clarify different issues regarding network
speed that pops up from time to time in amule forum. Generally speaking, there're several reasons for questions about "amule & network":
<ul>
<li>Speed reported by amule doesn't match provider given rate</li>
<li>Poor performance of amule itself or another network application on the same computer</li>
<li>What are key factors influencing network performance while amule is running
</li>
</ul>
Intended audience for this document are users who want to get better understanding of network functionality in general and in practical implication to amule functionality. 
This page, however, is not to be seen as comprehensive general purpose "Network
FAQ". 

==Network speed - how much is it ?==
While talking about network speed, people are using "bps" units, which mean
"bit per second". The reason for bit rather that byte is pretty
match historical, but also have engineering motivation behind. This motivation
comes from the fact, that not all networks in the world are transferring bytes. 
There's also convention to use capital "B" in "Bps" when speed is marked
in "bytes per second". However, this convention is not widely accepted. Particularly, organizations like IETF and IEEE are stick to original "bps". 

==Prefixes==
Since their invention, networks made quite a progress, and now we have networks
that transfers thousands and millions bits and more bits per second. For marking
those speeds, prefixes "kilo", "mega", "giga", "tera"
etc. are used. It is a common mistake to think that values with those prefixes are the same as in computer science, i.e. powers of 2. The truth is that, for historical reasons, prefixes in networking have a decimal base, and not a binary one.

<table cellpadding="2" cellspacing="2" border="1" width="100%"
title="Table 1">
<tr>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">Prefix 
</th>
<th valign="middle" align="center" bgcolor="#33ff33">meaning in computers 
</th>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">meaning in networks 
</th>
<th valign="middle" align="center" bgcolor="#33ff33">difference, %% 
</th>
</tr>
<tr>
<td valign="top">K (kilo) 
</td>
<td valign="top">2^10 = 1024 
</td>
<td valign="top">10^3 = 1000 
</td>
<td valign="top">2% 
</td>
</tr>
<tr>
<td valign="top">M (mega) 
</td>
<td valign="top">2^20 = 1,048,576 
</td>
<td valign="top">10^6 = 1,000,000 
</td>
<td valign="top">5% 
</td>
</tr>
<tr>
<td valign="top">G (giga) 
</td>
<td valign="top">2^30 = 1,073,741,624 
</td>
<td valign="top">10^9 = 1,000,000,000 
</td>
<td valign="top">7% 
</td>
</tr>
<tr>
<td valign="top">T (tera) 
</td>
<td valign="top">2^40 = 1,099,511,627,776 
</td>
<td valign="top">10^12 = 1,000,000,000,000 
</td>
<td valign="top">9% 
</td>
</tr>
<tr>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
</tr>

</table>
 
As you can see from the table above the error in calculation is about 5% when the prefix
is incorrectly interpreted. Please note that the speed your provider tells
you is "speed in network", i.e. calculated on decimal base. 
For example when your provider tells you that your link is "ADSL 256/128" you
should understand that he means 256000/128000 bps. Which means, that you have
64000/16000 bytes per second speed in your link. 

==Protocol overhead - what is it about==
When amule is running, it constantly "talks" with other "mules" and servers.
This data exchange is needed to identify itself, request information about
available sources and files, perform searches and so on. Since this information
has no use for the user itself, it's called "overhead" i.e. inevitable addition
to the data you actually want to upload or download. Amule calls this "connection
overhead". However, the number amule presents, includes only the size of the actual
data that amule itself is sending to the network stack. Later, this data is
sent down to the net with more overhead - now of network protocols. How much
is it - lets see that in the next section. 

==Network overhead==
First of all - we're talking about IPv4 network. Once upon a time, there
was only one type of IP network. Now there's 2 - IP version  4, the old
we all know; and IP version 6 - the new one. ED2K protocol by design, is
unable to talk over IPv6 network, so users who have it (in Japan and China
for example) will not be able to connect "as is". Using IPv4 means, that each
packet (TCP, UDP, ICMP) will have IPv4 header. The minimum size of this header
is 20 bytes. Header can have optional parts (each 4 bytes) and it's up to
your provider  - for example my add 1 option dword. 
When talking to other thing on ed2k network, amule uses the widely known TCP protocol.
UDP is also used, but in much smaller scale. As the reader might know, TCP is a reliable protocol, i.e. it's guaranteed that data which sent from one side will arrive on the other or an error will be reported. In order to achieve this, TCP send its own data in addition to the actual transfer. This data includes TCP client initial negotiation, checksums, sequence numbers and acknowledgments. All this is in the TCP header which is added to each packet sent. The size of this header
is 20 bytes minimum. While being small overhead for large bulk transfer, it
can take significant part of bandwidth when small amounts of data are being
exchanged. This is exactly what happens on source discovery part of amule.
Our client is trying to establish a connection and negotiate with a large number
of other clients. Doing this, amule opens new TCP connections all the
time. The amount of those connections is controlled by the "Maximum
number of connections in 5 seconds" setting in the preferences. A typical number
is about 100. Each TCP connection results in at least 3 packets traveling
the net - one is a SYN packet, i.e. connection request, and one an ACK or a RST
when the connection is accepted or refused, and SYN+ACK to establish the session.
There's more overhead of DNS queries when an address is resolved, retries when a
host doesn't reply and so on. 

===On low level:===
After passing TCP and IP layers packets go down to the network interface
driver. The kind of this driver depends on the way your computer is connected to the internet. For simplicity sake we will assume that this computer is connected to the ISP directly, i.e. you have no LAN (or switch or router) between.
Common setups that I'm aware of: 

<ol>
<li>Analog modem, connected to telephone line (ISDN modem falls in this category too)</li>
<li>Cable modem, connected through ethernet, ISP gives you an IP address through DHCP</li>
<li>Cable modem, connected through ethernet, ISP requires you to configure PPPoE or PPTP tunnel</li>
<li>ADSL modem, connected through ethernet. You must have a PPPoE or PPTP tunnel</li>
<li>Variation of above - modem connected to PC by USB. </li>

</ol>
In each of above setups there are different protocols in use, and different headers added to transmitted packets. But there's one important thing to note: ethernet frames traveling between cable/ADSL modem and PC don't reach the ISP. And consequently they are not counted in rate calculations. PPPoE and
PPTP headers, on the contrary do reach the ISP. Whether or not
your particular provider includes them in rate calculations I obviously have
no idea about. For this reason I will exclude those headers from my calculations.
If you think that your ISP includes it, add 4 bytes to the size of each packet. 

===Example:===
Let's see how much network overhead we have on a typical network. Our connection
is a cable modem connected via an ethernet link to a PC directly (no router between them).
In this setup we have IPv4 packets sent over ethernet. 
Lets say we have 10 new connections opened each second, and all are being accepted
(successfully established TCP session). This alone sums up to (I'm counting data
going up - from my computer to the net): 
 
10 connection * 2 packets * (20 bytes of TCP + 20 bytes of IPv4) = 800 bytes of overhead. 
 
This means that we are starting with  1.16*8 Kbps of "invisible"
overhead caused by the very way the network works. Now, let's assume that
after each connection is established our amule sends something to the other side
and waits to receive an answer. 
 
10 connections * (1 packet of data + 1 ACK)*(20 bytes of TCP + 20 bytes of IPv4) = 800 bytes of overhead. 
 
Total of 800 bytes + 800 bytes = 1600 bytes per second = 6400 bps = 6.4 Kbps 
 
What we have here is 6.4 Kbps of network overhead alone. Taking into account
that amule has other data to send (uploads) and it is not the only network
application running we will have the following picture: Most chances that your
link to provider is not that fast.  Amule will try to open
10 connections per second and will try to upload on the specified
speed. Your operating system will share all available bandwidth between those and between amule and other network applications (browser for example). Actual results will vary depending on specific OS settings. 

==ACK bottleneck==
In all calculations above there was one assumption - zero download. But downloading is what amule was built for. So let's examine how the overhead
above affects your downloading speed. The answer is in TCP protocol. When TCP is sending
data, it requires from the other side to acknowledge the reception. So if client
A is sending data to client B by TCP, B has to send a special ACK packets to A which tells B "ok, I got it". If, however, A doesn't receive the ACK packets
in time, he will assume that either packet is lost. So, without going deeply
into TCP specification: if B fails to send ACK to A, as a result A will
transmit slower. 
Now let's see the situation in amule. We saw in the previous chapter, that the uplink
stream is congested by connection requests and uploads. As a result, there's a
good chance that ACK packets for a file we are downloading will not be sent
on time. The remote party will notice this and slow down. This is one
more reason why the upstream should better not be too congested. 

==Is there something I can do ?==
OK, now that you understood why your network is so slow while amule is
running you will maybe look for a way to fix this. The answer in 2 words: "rate limit".
The first thing you should do is to assign realistic rate limits in amule
itself. If you have a uplink rate of 128 Kbps don't set amules upload limit to
16 (kilobytes per second) just because 128/8=16. 
A better, but far more complicated solution is to use the QoS and packet scheduling
services of your OS. For example, you can give a higher priority to ACK packets
to solve the above mentioned "ACK bottleneck" problem. The QoS topic, however, is beyond
scope of this article. 
 

==Router (switch, home network):  is there any difference ?==
When the cable coming from your ISP is connected to some switching or routing
device, which in turn is connected to several PC's, bandwidth is shared between
them. So, having N computers connected, an ideal device would simply provide
each one of them with 1/N of the total bandwidth. The situation may vary in real
life, and your particular device may have different idea about fairness. Since
you're not going to have the hardware specs of your router chipset the only
advice here is "try and see yourself".

FAQ network

2005-02-27T16:45:27Z

Thedude0001: wicification, typos and grammar

=Network speed: what you should know before asking questions=
by Froenchenko Leonid, <a href="lfroen@gmail.com">lfroen@gmail.com</a> 

==Preface==
The purpose of this document is to clarify different issues regarding network
speed that pops up from time to time in amule forum. Generally speaking, there're several reasons for questions about "amule & network":
<ul>
<li>Speed reported by amule doesn't match provider given rate</li>
<li>Poor performance of amule itself or another network application on the same computer</li>
<li>What are key factors influencing network performance while amule is running
</li>
</ul>
Intended audience for this document are users who want to get better understanding of network functionality in general and in practical implication to amule functionality. 
This page, however, is not to be seen as comprehensive general purpose "Network
FAQ". 

==Network speed - how much is it ?==
While talking about network speed, people are using "bps" units, which mean
"bit per second". The reason for bit rather that byte is pretty
match historical, but also have engineering motivation behind. This motivation
comes from the fact, that not all networks in the world are transferring bytes. 
There's also convention to use capital "B" in "Bps" when speed is marked
in "bytes per second". However, this convention is not widely accepted. Particularly, organizations like IETF and IEEE are stick to original "bps". 

==Prefixes==
Since their invention, networks made quite a progress, and now we have networks
that transfers thousands and millions bits and more bits per second. For marking
those speeds, prefixes "kilo", "mega", "giga", "tera"
etc. are used. It is a common mistake to think that values with those prefixes are the same as in computer science, i.e. powers of 2. The truth is that, for historical reasons, prefixes in networking have a decimal base, and not a binary one.

<table cellpadding="2" cellspacing="2" border="1" width="100%"
title="Table 1">
<tr>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">Prefix 
</th>
<th valign="middle" align="center" bgcolor="#33ff33">meaning in computers 
</th>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">meaning in networks 
</th>
<th valign="middle" align="center" bgcolor="#33ff33">difference, %% 
</th>
</tr>
<tr>
<td valign="top">K (kilo) 
</td>
<td valign="top">2^10 = 1024 
</td>
<td valign="top">10^3 = 1000 
</td>
<td valign="top">2% 
</td>
</tr>
<tr>
<td valign="top">M (mega) 
</td>
<td valign="top">2^20 = 1,048,576 
</td>
<td valign="top">10^6 = 1,000,000 
</td>
<td valign="top">5% 
</td>
</tr>
<tr>
<td valign="top">G (giga) 
</td>
<td valign="top">2^30 = 1,073,741,624 
</td>
<td valign="top">10^9 = 1,000,000,000 
</td>
<td valign="top">7% 
</td>
</tr>
<tr>
<td valign="top">T (tera) 
</td>
<td valign="top">2^40 = 1,099,511,627,776 
</td>
<td valign="top">10^12 = 1,000,000,000,000 
</td>
<td valign="top">9% 
</td>
</tr>
<tr>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
</tr>

</table>
 
As you can see from the table above the error in calculation is about 5% when the prefix
is incorrectly interpreted. Please note that the speed your provider tells
you is "speed in network", i.e. calculated on decimal base. 
For example when your provider tells you that your link is "ADSL 256/128" you
should understand that he means 256000/128000 bps. Which means, that you have
64000/16000 bytes per second speed in your link. 

==Protocol overhead - what is it about==
When amule is running, it constantly "talks" with other "mules" and servers.
This data exchange is needed to identify itself, request information about
available sources and files, perform searches and so on. Since this information
has no use for the user itself, it's called "overhead" i.e. inevitable addition
to the data you actually want to upload or download. Amule calls this "connection
overhead". However, the number amule presents, includes only the size of the actual
data that amule itself is sending to the network stack. Later, this data is
sent down to the net with more overhead - now of network protocols. How much
is it - lets see that in the next section. 

==Network overhead==
First of all - we're talking about IPv4 network. Once upon a time, there
was only one type of IP network. Now there's 2 - IP version  4, the old
we all know; and IP version 6 - the new one. ED2K protocol by design, is
unable to talk over IPv6 network, so users who have it (in Japan and China
for example) will not be able to connect "as is". Using IPv4 means, that each
packet (TCP, UDP, ICMP) will have IPv4 header. The minimum size of this header
is 20 bytes. Header can have optional parts (each 4 bytes) and it's up to
your provider  - for example my add 1 option dword. 
When talking to other thing on ed2k network, amule uses the widely known TCP protocol.
UDP is also used, but in much smaller scale. As the reader might know, TCP is a reliable protocol, i.e. it's guaranteed that data which sent from one side will arrive on the other or an error will be reported. In order to achieve this, TCP send its own data in addition to the actual transfer. This data includes TCP client initial negotiation, checksums, sequence numbers and acknowledgments. All this is in the TCP header which is added to each packet sent. The size of this header
is 20 bytes minimum. While being small overhead for large bulk transfer, it
can take significant part of bandwidth when small amounts of data are being
exchanged. This is exactly what happens on source discovery part of amule.
Our client is trying to establish a connection and negotiate with a large number
of other clients. Doing this, amule opens new TCP connections all the
time. The amount of those connections is controlled by the "Maximum
number of connections in 5 seconds" setting in the preferences. A typical number
is about 100. Each TCP connection results in at least 3 packets traveling
the net - one is a SYN packet, i.e. connection request, and one an ACK or a RST
when the connection is accepted or refused, and SYN+ACK to establish the session.
There's more overhead of DNS queries when an address is resolved, retries when a
host doesn't reply and so on. 

===On low level:===
After passing TCP and IP layers packets go down to the network interface
driver. The kind of this driver depends on the way your computer is connected to the internet. For simplicity sake we will assume that this computer is connected to the ISP directly, i.e. you have no LAN (or switch or router) between.
Common setups that I'm aware of: 

<ol>
<li>Analog modem, connected to telephone line (ISDN modem falls in this category too)</li>
<li>Cable modem, connected through ethernet, ISP gives you an IP address through DHCP</li>
<li>Cable modem, connected through ethernet, ISP requires you to configure PPPoE or PPTP tunnel</li>
<li>ADSL modem, connected through ethernet. You must have a PPPoE or PPTP tunnel</li>
<li>Variation of above - modem connected to PC by USB. </li>

</ol>
In each of above setups there are different protocols in use, and different headers added to transmitted packets. But there's one important thing to note: ethernet frames traveling between cable/ADSL modem and PC don't reach the ISP. And consequently they are not counted in rate calculations. PPPoE and
PPTP headers, on the contrary do reach the ISP. Whether or not
your particular provider includes them in rate calculations I obviously have
no idea about. For this reason I will exclude those headers from my calculations.
If you think that your ISP includes it, add 4 bytes to the size of each packet. 

===Example:===
Let's see how much network overhead we have on a typical network. Our connection
is a cable modem connected via an ethernet link to a PC directly (no router between them).
In this setup we have IPv4 packets sent over ethernet. 
Lets say we have 10 new connections opened each second, and all are being accepted
(successfully established TCP session). This alone sums up to (I'm counting data
going up - from my computer to the net): 
 
10 connection * 2 packets * (20 bytes of TCP + 20 bytes of IPv4) = 800 bytes of overhead. 
 
This means that we are starting with  1.16*8 Kbps of "invisible"
overhead caused by the very way the network works. Now, let's assume that
after each connection is established our amule sends something to the other side
and waits to receive an answer. 
 
10 connections * (1 packet of data + 1 ACK)*(20 bytes of TCP + 20 bytes of IPv4) = 800 bytes of overhead. 
 
Total of 800 bytes + 800 bytes = 1600 bytes per second = 6400 bps = 6.4 Kbps 
 
What we have here is 6.4 Kbps of network overhead alone. Taking into account
that amule has other data to send (uploads) and it is not the only network
application running we will have the following picture: Most chances that your
link to provider is not that fast.  Amule will try to open
10 connections per second and will try to upload on the specified
speed. Your operating system will share all available bandwidth between those and between amule and other network applications (browser for example). Actual results will vary depending on specific OS settings. 

==ACK bottleneck==
In all calculations above there was one assumption - zero download. But downloading is what amule was built for. So let's examine how the overhead
above affects your downloading speed. The answer is in TCP protocol. When TCP is sending
data, it requires from the other side to acknowledge the reception. So if client
A is sending data to client B by TCP, B has to send a special ACK packets to A which tells B "ok, I got it". If, however, A doesn't receive the ACK packets
in time, he will assume that either packet is lost. So, without going deeply
into TCP specification: if B fails to send ACK to A, as a result A will
transmit slower. 
Now let's see the situation in amule. We saw in the previous chapter, that the uplink
stream is congested by connection requests and uploads. As a result, there's a
good chance that ACK packets for a file we are downloading will not be sent
on time. The remote party will notice this and slow down. This is one
more reason why the upstream should better not be too congested. 

==Is there something I can do ?==
OK, now that you understood why your network is so slow while amule is
running you will maybe look for a way to fix this. The answer in 2 words: "rate limit".
The first thing you should do is to assign realistic rate limits in amule
itself. If you have a uplink rate of 128 Kbps don't set amules upload limit to
16 (kilobytes per second) just because 128/8=16. 
A better, but far more complicated solution is to use the QoS and packet scheduling
services of your OS. For example, you can give a higher priority to ACK packets
to solve the above mentioned "ACK bottleneck" problem. The QoS topic, however, is beyond
scope of this article. 
 

==Router (switch, home network):  is there any difference ?==
When the cable coming from your ISP is connected to some switching or routing
device, which in turn is connected to several PC's, bandwidth is shared between
them. So, having N computers connected, an ideal device would simply provide
each one of them with 1/N of the total bandwidth. The situation may vary in real
life, and your particular device may have different idea about fairness. Since
you're not going to have the hardware specs of your router chipset the only
advice here is "try and see yourself".

HowTo Compile aMuled

2005-02-26T14:28:28Z

Thedude0001: fixed configure, some formatting

1st

download wxBase 2.5.4 from www.wxWidgets.org
unpack it, and do as user
*./configure --prefix=/usr/
*make
as root
*make install
*ldconfig

2nd

*download amule-cvs !!! from http://amule.hirnriss.net
Don't use rc8, there was a severe bug concerning amuled in it!

unpack it, and do as user
*./configure --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon --prefix=/usr/local
*make
as root
*make install

That's it. You now have a working aMule-daemon in /usr/local/bin. 
Now you need to configure it, to create the .eMule file, which is the preferences file, run aMuled once. 
The .eMule file and the .aMule directory will be creted in the home directory of the user that ran aMule. 
You probably want amuleweb to controll your daemon. To be able to use that you need to enable external connections. Check this [http://www.amule.org/wiki/index.php/Webserver-1.2.x HowTo] 
I know it's for 1.2.x but since you dont have a GUI to setup everything this is what you want. 
 

== Where to report problems and questions? ==

For Problems or Questions just report on http://forum.amule.org forum or join [[IRC]] channel [irc://irc.freenode.net/amule #amule] at [irc://irc.freenode.net irc.freenode.net]

Stefanero

Using another wxinstall

2005-02-24T21:54:20Z

Thedude0001:

<center>
'''English''' | [[Using another wxinstall-de|Deutsch]]
</center>

If there's already a version of [[wxWidgets]] installed, but you want [[aMule]] to use another (probably newer) one, here are the steps to follow:

First, create the target directory (in this article, as an example, ''~/aMule/'' will be used), where [[wxWidgets]] and [[aMule]] will reside (they don't need to be in the same dir, but it makes life easier). Then configure [[wxWidgets]] and [[aMule]] accordingly (assuming [[wxWidgets]] 2.4.2 and current (=>rc8) aMule).

It is recommended that you read the article about [[Compilation_Installation#Step_1:_wxGTK|how to compile wxGTK]] and (optionally, only if installing a [[wxWidgets]] version prior to 2.5) [[Compilation_Installation#Step_2:_wxBase|how to compile wxBase]]

In [[aMule]] source dir: 
''./configure --prefix=~/aMule/ --enable-debug --disable-optimize --with-wx-config=/home/'''user'''/aMule/bin/wx-config --with-wxbase-config=/home/'''user'''/aMule/bin/wxbase-2.4-config'' 
''make && make install''

'''NOTE:''' On some distros, instead of ''--with-wx-config=/home/'''user'''/aMule/bin/wx-config'' you might need to use ''--with-wx-config=/home/'''user'''/aMule/bin/wxgtk-2.4-config''

'''NOTE 2:''' Sometimes [[wxBase]] will overwrite ''wx-config''. You can know if it has done so by running ''wx-config --basename''. It should show ''wx_gtk''. If it doesn't, please reinstall [[wxGTK]] so it will overwritte ''wx-config'' to link it to the [[wxGTK]] file.

On the above example, [[aMule]] binary will be installed in ''~/aMule/bin/'' directory.

Also note that ''--with-wxbase-config=...'' should only be used with [[wxWidgets]] versions prior to 2.5.

To start [[aMule]], you need to explicitely specifiy the LD path each time you run it:

''export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH'' 
''export LC_ALL=en_EN.UTF-8''

'''NOTE 3:''' On some systems the above export command does not work, you have instead to run 
''export LD_LIBRARY_PATH=~/aMule/lib/:$LD_LIBRARY_PATH'' 
This has been observed on Debian and Gentoo Linux.

Please remember to create [[Backtraces]] and provide them to the [[AMule_devs|aMule development team]].

HowTo Compile In Gentoo

2005-02-23T22:19:00Z

Thedude0001:

Compiling a recent version of amule on Gentoo should be a breeze by just typing
'emerge -av amule'
but due to several facts it isn't quite that easy right now. So here's a little Step by Step explanation. Please read the whole document before doing anything as there are several ways you can use and each of them will have a different outcome.

=Stable amule from portage=

If you just ''emerge amule'' you will most likely get the latest package that is marked as stable in portage. This is amule-1.2.8 which is more than 12 months old, lacks several bugfixes and features which could seriously lower your download or make it impossible to connect to some servers. So that is not really an option.

=Unstable amule from portage=
Gentoo classifies amule2.0.0rc ebuilds as unstable because they are ReleaseCandidates. The latest one available is amule2.0.0rc7. There is an (inofficial) ebuild for rc8, but as rc8 depends on wxGTK2.5.3 to build the amule daemon and wxGTK2.5.3 is hardmasked in portage it isn't available through portage.

However, if rc7 is "new enough" for you enter the following things as root into a console:

<code>mkdir /etc/portage</code> (this could give an error message if the directory already exists, just ignore that) 
<code>echo 'net-p2p/amule ~x86' >> /etc/portage/package.keywords 
emerge -av amule</code>

However rc7 is getting quite old now, so it is the best thing to use either rc8 or even a recent cvs tarball and compile amule manually.

=Recent amule manual installation=
Per default Gentoo uses gtk2 in all recent profiles. When it comes to wxGTK (which is needed by amule) this can be some trouble. The recent stable wxGTK in portage is wxGTK2.4.2 which should never be linked against GTK2. It causes random crashes, freezes, inpredictable behaviour and may even harm your pet dog!

So there are two possible ways to go: choose wxGTK2.4.2 linked against GTK1.2 (which should be fine for everybody who doesn't want to use amuled, the amule daemon) or choose wxGTK2.5.3 linked either against GTK1.2 or GTK2 (for those who want to try amuled as amuled doesn't work with wxGTK prior to 2.5.3).

Another thing is unicode support: You can't enable unicode support when using GTK1.2 and enabling unicode with GTK2 causes huge memleaks (100MB and more in 24h). So I will just disable it in these examples.

==wxGTK2.4.2==
If you don't want to use amuled then wxGTK2.4.2 is just fine for. You only need to tell it that it should link against GTK1.2. To do this grab a console and enter (as root):

<code>mkdir /etc/portage</code> (this may give you an error if the directory already exists, just ignore that) 
<code> echo 'x11-libs/wxGTK -gtk2 -unicode' >> /etc/portage/package-use 
emerge -av wxGTK</code>

This should (re-)emerge wxGTK2.4.2 linked against GTK1.2. Now you can go on to [[HowTo_Compile_In_Gentoo#compiling_amule|compiling amule]].

==wxGTK2.5.3==
If you want to use amuled then you need at least wxGTK2.5.3. This is currently hardmasked in portage due to problems when compiling with opengl support. But as amule is no 3D egoshooter we can safely disable opengl support and use it anyway. To do so enter the following into a console as root:

<code>mkdir /etc/portage</code> (this may give you an error if the directory already exists, just ignore that) 
<code>echo '=x11-libs/wxGTK-2.5*' >> /etc/portage/package.unmask 
echo 'x11-libs/wxGTK ~x86' >> /etc/portage/package.keywords </code>

If you want to use GTK1.2 (recommended): 
<code>echo 'x11-libs/wxGTK -gtk2 -unicode -opengl' >> /etc/portage/package.use </code>

If you want to use GTK2 (not thoroughly tested yet): 
<code>echo 'x11-libs/wxGTK -unicode -opengl' >> /etc/portage/package.use </code>

<code>emerge -av wxGTK</code>

==Compiling amule==
Grab either amule2.0.0rc8 from [http://www.amule.org http://www.amule.org] or (especially if you want to use amuled) a recent cvs tarball from [http://amule.hirnriss.net http://amule.hirnriss.net]. Untar it by entering <code>tar -xvjf aMule-foo.tar.bz2</code> and cd to the new directory.

check <code>./configure --help</code> for a summary of all configure options. Pick the ones you want and run (as an example building the monolithic client and amulecmd) 
<code>./configure --enable-amulecmd</code>

Check the configure output for errors and if everything seems fine type <code>make</code>. Once amule is done compiling change to a root account and type <code>make install</code> to install amule. Now you're done and can start enjoying your amule experience.

HowTo Compile In Gentoo

2005-02-23T21:25:04Z

Thedude0001:

Compiling a recent version of amule on Gentoo should be a breeze by just typing
'emerge -av amule'
but due to several facts it isn't quite that easy right now. So here's a little Step by Step explanation. Please read the whole document before doing anything as there are several ways you can use and each of them will have a different outcome.

=Stable amule from portage=

If you just ''emerge amule'' you will most likely get the latest package that is marked as stable in portage. This is amule-1.2.8 which is more than 12 months old, lacks several bugfixes and features which could seriously lower your download or make it impossible to connect to some servers. So that is not really an option.

=Unstable amule from portage=
Gentoo classifies amule2.0.0rc ebuilds as unstable because they are ReleaseCandidates. The latest one available is amule2.0.0rc7. There is an (inofficial) ebuild for rc8, but as rc8 depends on wxGTK2.5.3 to build the amule daemon and wxGTK2.5.3 is hardmasked in portage it isn't available through portage.

However, if rc7 is "new enough" for you enter the following things as root into a console:

<code>mkdir /etc/portage</code> (this could give an error message if the directory already exists, just ignore that) 
<code>echo 'net-p2p/amule ~x86' >> /etc/portage/package.keywords 
emerge -av amule</code>

However rc7 is getting quite old now, so it is the best thing to use either rc8 or even a recent cvs tarball and compile amule manually.

=Recent amule manual installation=
Per default Gentoo uses gtk2 in all recent profiles. When it comes to wxGTK (which is needed by amule) this can be some trouble. The recent stable wxGTK in portage is wxGTK2.4.2 which should never be linked against GTK2. It causes random crashes, freezes, inpredictable behaviour and may even harm your pet dog!

So there are two possible ways to go: choose wxGTK2.4.2 linked against GTK1.2 (which should be fine for everybody who doesn't want to use amuled, the amule daemon) or choose wxGTK2.5.3 linked either against GTK1.2 or GTK2 (for those who want to try amuled as amuled doesn't work with wxGTK prior to 2.5.3).

Another thing is unicode support: You can't enable unicode support when using GTK1.2 and enabling unicode with GTK2 causes huge memleaks (100MB and more in 24h). So I will just disable it in these examples.

==wxGTK2.4.2==
If you don't want to use amuled then wxGTK2.4.2 is just fine for. You only need to tell it that it should link against GTK1.2. To do this grab a console and enter (as root):

<code>mkdir /etc/portage</code> (this may give you an error if the directory already exists, just ignore that) 
<code> echo 'x11-libs/wxGTK -gtk2 -unicode' >> /etc/portage/package-use 
emerge -av wxGTK</code>

This should (re-)emerge wxGTK2.4.2 linked against GTK1.2. Now you can go on to [[HowTo_Compile_In_Gentoo#compiling_amule|compiling amule]].

==wxGTK2.5.3==
If you want to use amuled then you need at least wxGTK2.5.3. This is currently hardmasked in portage due to problems when compiling with opengl support. But as amule is no 3D egoshooter we can safely disable opengl support and use it anyway. To do so enter the following into a console as root:

<code>mkdir /etc/portage</code> (this may give you an error if the directory already exists, just ignore that) 
<code>echo '=x11-libs/wxGTK-2.5*' >> /etc/portage/package.unmask 
echo 'x11-libs/wxGTK ~x86' >> /etc/portage/package.keywords </code>

If you want to use GTK1.2 (recommended): 
<code>echo 'x11-libs/wxGTK -gtk2 -unicode -opengl' >> /etc/portage/package.use </code>

If you want to use GTK2 (not thoroughly tested yet): 
<code>echo 'x11-libs/wxGTK -unicode -opengl' >> /etc/portage/package.use 

<code>emerge -av wxGTK</code>

==Compiling amule==
Grab either amule2.0.0rc8 from [http://www.amule.org http://www.amule.org] or (especially if you want to use amuled) a recent cvs tarball from [http://amule.hirnriss.net http://amule.hirnriss.net]. Untar it by entering <code>tar -xvjf aMule-foo.tar.bz2</code> and cd to the new directory.

check <code>./configure --help</code> for a summary of all configure options. Pick the ones you want and run (as an example building the monolithic client and amulecmd) 
<code>./configure --enable-amulecmd</code>

Check the configure output for errors and if everything seems fine type <code>make</code>. Once amule is done compiling change to a root account and type <code>make install</code> to install amule and you're done.

HowTo Compile In Gentoo

2005-02-23T21:15:51Z

Thedude0001: initial article

Compiling a recent version of amule on Gentoo should be a breeze by just typing
'emerge -av amule'
but due to several facts it isn't quite that easy right now. So here's a little Step by Step explanation. PLease read the whole document before doing anything as there are several ways you can use and which will each have a different outcome.

=Stable amule from portage=

If you just ''emerge amule'' you will most likely get the latest package that is marked as stable in portage. This is amule-1.2.8 which is more than 12 months old, lacks several bugfixes and features which could seriously lower your download or make it impossible to connect to some servers. So that is not really an option.

=Unstable amule from portage=
Gentoo classifies amule2.0.0rc ebuilds as unstable because they are ReleaseCandidates. The latest one available is amule2.0.0rc7. There is an (inofficial) ebuild for rc8, but as rc8 depends on wxGTK2.5.3 to build the amule daemon and wxGTK2.5.3 is hardmasked in portage it isn't available through portage.

However, if rc7 is "new enough" for you enter the following things as root into a console:

<code>mkdir /etc/portage</code> (this could give an error message if the directory already exists, just ignore that) 
<code>echo 'net-p2p/amule ~x86' >> /etc/portage/package.keywords 
emerge -av amule</code>

However rc7 is getting quite old now, so it is the best thing to use either rc8 or even a recent cvs tarball and compile amule manually.

=Recent amule manual installation=
Per default Gentoo uses gtk2 in all recent profiles. When it comes to wxGTK (which is needed by amule) this can be some trouble. The recent stable wxGTK in portage is wxGTK2.4.2 which should never be linked against GTK2. It causes random crashes, freezes, inpredictable behaviour and may even harm your pet dog!

So there are two possible ways to go: choose wxGTK2.4.2 linked against GTK1.2 (which should be fine for everybody who doesn't want to use amuled, the amule daemon) or choose wxGTK2.5.3 linked either against GTK1.2 or GTK2 (for those who want to try amuled as amuled doesn't work with wxGTK prior to 2.5.3).

Another thing is unicode support: You can't enable unicode support when using GTK1.2 and enabling unicode with GTK2 causes huge memleaks (100MB and more in 24h). So I will just disable it in these examples.

==wxGTK2.4.2==
If you don't want to use amuled then wxGTK2.4.2 is just fine for. You only need to tell it that it should link against GTK1.2. To do this grab a console and enter (as root):

<code>mkdir /etc/portage</code> (this may give you an error if the directory already exists, just ignore that) 
<code> echo 'x11-libs/wxGTK -gtk2 -unicode' >> /etc/portage/package-use 
emerge -av wxGTK</code>

This should (re-)emerge wxGTK2.4.2 linked against GTK1.2. Now you can go on to [[HowTo_Compile_In_Gentoo#compiling_amule|compiling amule]].

==wxGTK2.5.3==
If you want to use amuled then you need at least wxGTK2.5.3. This is currently hardmasked in portage due to problems when compiling with opengl support. But as amule is no 3D egoshooter we can safely disable opengl support and use it anyway. To do so enter the following into a console as root:

<code>mkdir /etc/portage</code> (this may give you an error if the directory already exists, just ignore that) 
<code>echo '=x11-libs/wxGTK-2.5*' >> /etc/portage/package.unmask 
echo 'x11-libs/wxGTK ~x86' >> /etc/portage/package.keywords </code>

If you want to use GTK1.2 (recommended): 
<code>echo 'x11-libs/wxGTK -gtk2 -unicode -opengl' >> /etc/portage/package.use </code>

If you want to use GTK2 (not thoroughly tested yet): 
<code>echo 'x11-libs/wxGTK -unicode -opengl' >> /etc/portage/package.use 

<code>emerge -av wxGTK</code>

==Compiling amule==
Grab either amule2.0.0rc8 from [http://www.amule.org http://www.amule.org] or (especially if you want to use amuled) a recent cvs tarball from [http://amule.hirnriss.net http://amule.hirnriss.net]. Untar it by entering <code>tar -xvjf aMule-foo.tar.bz2</code> and cd to the new directory.

check <code>./configure --help</code> for a summary of all configure options. Pick the ones you want and run (as an example building the monolithic client and amulecmd) 
<code>./configure --enable-amulecmd</code>

Check the configure output for errors and if everything seems fine type <code>make</code>. Once amule is done compiling change to a root account and type <code>make install</code> to install amule and you're done.

Format specifiers

2005-02-09T01:04:25Z

Thedude0001: typos

== Introduction ==

[[aMule]] is being developed in the [http://www.icce.rug.nl/documents/cplusplus C++] programming language. This language alows to handle strings very easily but sometimes it needs a little tweaking in those strings.

When [[translations|translating aMule]], you might encounter with strange things. Sometimes this will be just typos, but sometimes they are there on purpose.

This document is a '''must read''' for anyone willing or actually [[translations|translating aMule]]. It describes all the cases of groups of characters which '''should not''' ever be modified.

So, the following is a description of all the groups of characters which are '''not''' supposed to be modified and what they actually mean.

== Escape codes ==

=== Non-representable [http://www.ecma-international.org/publications/standards/Ecma-006.htm ASCII] codes ===

This are codes which represent characters of the [http://www.ecma-international.org/publications/standards/Ecma-006.htm ASCII] codeset which aren't representable with the keyboard.
*''\a'' -> This will normally cause an audible alert (sometimes visual) like a beep
*''\b'' -> Will go back one character
*''\f'' -> On most systems this will clean the screen
*''\n'' -> Ends the current line and starts a new one, palcing the cursor at the begining
*''\r'' -> Goes to the beggining of the current line
*''\t'' -> Torizontal tabulation
*''\v'' -> Vertical tabulation
*''\<octal digits>'' -> Will display the value ''octal digits'' in octal
*''\x<hex digits>'' -> Will display the value ''hex digits'' in hexadecimal

=== Disambiguation escape codes ===

The following are not characters non-representable on the keyboard, but due to limitations in the [http://www.icce.rug.nl/documents/cplusplus C++] programming language, are needed to be used this way:
*''\?'' -> Displays a question mark ( ''?'' ) to avoid trigraph translations (not all compilers support trigraph translating, so it's not allways necessary)
*''\\'' -> Displays a backslash ( ''\'' )
*''\'' -> Displays a single quote ('' ' '')
*''\"'' -> Displays a double quote ('' " '')

=== Examples ===

The following are some examples for the above escape codes. They are listed as couples of code-line + output. So, the first line represents the line in the way it is written into the [http://www.icce.rug.nl/documents/cplusplus C++] code and the second line (or group of lines if it needs more than one line) represents how that [http://www.icce.rug.nl/documents/cplusplus C++] code line is displayed on execution:

**Code line: ''"[[User:Jacobo221|Jacobo221]] is an angel\aOh, true, I am not."''
**Output: ''[[User:Jacobo221|Jacobo221]] is an angelOh, true, I am not'' (A beep will be heard right after displaying the word ''angel'' and the next word (''Oh'') will not be displayed untill the beep finishes)

**Code line: ''"I have 6\b5 fingers in my right hand"''
**Output: ''I have 5 fingers in my right hand''

**Code line: ''"Where is the <RETURN> key???\nAh, here it is!"''
**Output: ''Where is the <RETURN> key???'' ''Ah, here it is!''

**Code line: ''"I am a BIG lier\rI'm married with Marilyn Monroe"''
**Output: ''I'm married with Marilyn Monroe''

**Code line: ''"\141\115\165\x6C\x65"''
**Output: ''aMule'' (Notice that the octal value of ''a'' in the [http://www.ecma-international.org/publications/standards/Ecma-006.htm ASCII] codeset is 141, the octal value of ''M'' is 115, the octal value of ''u'' is 165, the hexadecimal value of ''l'' is 6C and the hexadecimal value of ''e'' is 65)

**Code line: ''"Isn\'t it complicated to use the \" and \\ characters\?"''
**Output: ''Isn't it complicated to use the " and \ characters?''

== Format specifiers ==

=== Basic format specifiers ===

Format specifiers are groups of characters which will be substituted with something else. The format specifier itself specified which type of data it will be substituted with:
*''%d'' -> Decimal value (signed integer type). Equivalen to %i
*''%i'' -> Decimal value (signed integer type). Equivalen to %d
*''%u'' -> Natural number (unsigned integer type).
*''%x'' -> Hexadecimal value represented with lowercase characters (unsigned integer type)
*''%X'' -> Hexadecimal value represented with uppercase characters (unsigned integer type)
*''%o'' -> Octal value (unsigned integer type)
*''%f'' -> Rational number (number with a floating point) with the normal (showing all numbers) notation (both float and double types)
*''%e'' -> Rational number (number with a floating point) with exponential notation using lowercase ''e'' (both float and double types)
*''%E'' -> Rational number (number with a floating point) with exponential notation using uppercase ''E'' (both float and double types)
*''%g'' -> Rational number (number with a floating point) with normal or exponential notation depending on the value. If exponential, a lowercase ''e'' will be used (both float and double types)
*''%G'' -> Rational number (number with a floating point) with normal or exponential notation depending on the value. If exponential, an uppercase ''E'' will be used (both float and double types)
*''%c'' -> A single character text representation (integer type)
*''%s'' -> A string (array, pointer of integers type)
*''%p'' -> Displays a memory addess (pointer type)
*''%n'' -> The variable that is assigned to this format specifier will be given the value of the number of characters displayed up to know (integer type)

=== Type extensions ===

Sometimes, some characters can be inserted between ''%'' and the character representing the type of data. This insterted characters are meant to extend the information about the type of data the format specifier is going to be substituted with:
*''h'' -> Will turn into short integer type. Valid for ''d'', ''i'', ''o'', ''u'', ''x'', ''X'' and ''n''.
*''l'' -> Will turn into long integer type. Valid for for ''d'', ''i'', ''o'', ''u'', ''x'', ''X'' and ''n''.
*''L'' -> Will turn into long double type. Valid for 'e'', ''E'', ''f'', ''F'', ''g'', ''G''

=== Output tweaks ===

Also, some of the format specifiers allow to tweak a bt how they should be outputted. This tweaking codes must be inserted between ''%'' and the type character:
*''-'' -> Aligns to the left
*''+'' -> Prints plus ( ''+'' ) sign even when the number is positive. Valid for *''d'', ''i'', ''e'', ''E'', ''f'', ''g'' and ''G''.
*''0'' -> Fill the blank spaces with zeros ( ''0'' ) instead of spaces. Valid for *''d'', ''i'', ''u'', ''x'', ''X'', ''o'', ''e'', ''E'', ''f'', ''g'' and ''G''.
*''#'' -> It will act in different ways depending on the type of data:
**''o': A zero ( ''0'' ) will be prepended when the data is non-zero.
**''x'' and ''X'': Prepends a zero ( ''0'' ) to the data.
**''f'', ''e'', ''E'', ''g'' and ''G'': Displays the decimal point even when the data is an integer (no decimals).
**''g'' and ''G'': The trailing zeros are not removed.
*''<non-zero decimal value>'' -> Specifies the minimum width the data must occupy (if not all is occupied, it will be padded). Can be used together with ''0''.
*''.<decimal value>'' -> It will act in different ways depending on the type of data:
**''f'', ''e'' and ''E'': Specify the amount of decimals it is allowed to display (if ''.0'', no decimals will be displayed).
**''s'': Maximum amount of characters to display (if ''.0'', no characters will be displayed).
*''%%'' -> This is not a format specifier, instead, it is only meant to be used to avoid ambiguousity. It will display a single ''%'' character.

=== Examples ===

The following are some examples for the above format specifiers. They are listed as couples of code-line + output. So, the first line represents the line in the way it is written into the [http://www.icce.rug.nl/documents/cplusplus C++] code and the second line (or group of lines if it needs more than one line) represents. The data for which the format specifiers are being substituted is random (well, not really random, I've just set something meaning-full in each example):

**Code line: ''"I am %s and I am %d years old."''
**Output: ''I am [[User:Jacobo221|Jacobo221]] and I am 19 years old.''

**Code line: ''"The first letter in the english alphabet is %c"''
**Output: ''The first letter in the english alphabet is A''

**Code line: ''"There exists a format specifier which is %%%c"''
**Output: ''There exists a format specifier which is %E''

**Code line: ''"There exists a format specifier which is %%c"''
**Output: ''There exists a format specifier which is %c''

**Code line: ''"%E and %e are the same number"''
**Output: ''9.186329E+00 and 9.186329e+00 are the same number''

**Code line: ''"%g is in normal notation while %g is in exponential notation"''
**Output: ''0.25 is in normal notation while 3.234234E+34 is in exponential notation''

**Code line: ''"%+d is a positive number"''
**Output: ''+5 is a positive number''

**Code line: ''"%05f says: Am I not 0-plenty?"''
**Output: ''000.250000 says: Am I not 0-plenty?''

**Code line: ''"Both %#o and %#X start with a zero"''
**Output: ''Both 0345 and 065FC start with a zero''

**Codeline: ''"%010x must be plenty of zeros"''
**Output: ''00000065fc must be plenty of zeros''

**Codeline: ''"Pi number is %.2f"''
**Output: ''Pi number is 3.14''

**Codeline: ''"Look what happens when you read the four letters in [http://www.mozilla.org/products/firefox Firefox]: %.4s"''
**Output: ''Look what happens when you read the four letters in [http://www.mozilla.org/products/firefox Firefox]: Fire''

== Other stuff ==

There are other things you must have in mind when translating. So keep on reading.

=== Character cases ===

The [http://www.icce.rug.nl/documents/cplusplus C++] programming language doesn't consider uppercase and lowercase letters as the same lettes. So, 'a' is a different letter from 'A' for [http://www.icce.rug.nl/documents/cplusplus C++] programs. In most cases, this will be insignificant for you, but when dealing with [[#Escape codes|escape codes]] and [[#Format specifiers|format specifiers]] it does, so please remain them the same.

=== Leading and ending blank spaces ===

You will sometimes find strings with either begin or end with a space. This is '''not''' a typo. That space is there for a reason. Most usually this reason is one of the following:
#Appearance. Maybe it separates the string from somewhere that, without this separation, would look ugly.
#Future additions. In 99% of the cases, it will be because some data is going to be appended to it. Imagine you find a string like ''I am ''. Although no ''%s'' format specifier is found there, some data is going to be added later anyway. So, if the blank space wasn't kept, once translated, in the app it would look like ''I amme'' instead of ''I am me''.

=== Examples ===

The following are examples of the above cases explained. They are unified into groups of four lines. The first line shows an original string, the second one how it should be translated (the examples are translated into spanish),the third one a possible output and the fourth line translates the translated possible output back into english so that you can understand it in case you don't speak spanish:

**Code line: ''"[[aMule]] version "''
**Translation: ''"[[aMule]] versión "''
**Output: ''[[aMule]] versión 2.0.0''
**Output (in english): ''[[aMule]] version 2.0.0''

**Code line: ''" can become a %s [[aMule]] user"''
**Translation: ''" puede llegar a ser un %s usuario de [[aMule]]"''
**Output: ''Cualquiera puede llegar a ser un feliz usuario de [[aMule]]''
**Output (in english): ''Anyone can become a happy [[aMule]] user''

**Code line: ''" this line looks complete and the leading and ending spaces can be deleted because they seem typos "''
**Translation: ''" esta frase parece completa y los espacios del principio y del final se pueden eliminar porque deben ser un error "''
**Output: ''Aunque esta frase parece completa y los espacios del principio y del final se pueden eliminar porque deben ser un error no lo es porque, como se puede ver, quedaban cosas por añadir, lo cual demuestra que '''nunca''' se deben eliminar esos espacios''
**Output (in english): ''Allthough this line looks complete and the leading and ending spaces can be deleted because they seem typos it is not because, as you can see, there were still words to be added, so this shows you why you should '''never''' delete those spaces''

== Overall example ==

'''Example:'''
:Untranslated:
:''msgid="I am %s and I a %d-year old\nand I\'m a happy \"aMule\" user "''
:''msgstr=""

:Would become (translation to spanish):
:''msgid="I am %s, %d years old\nand &I\'m a happy \"rabitty-aMule\" user "''
:''msgstr="Soy %s y tengo %d años\ny soy un fel&iz usuario del \"conejillo-aMule\" "''

:Explanation:
:#''%s'' and ''%d'' '''must''' be copied literally since they will be substituted in the program with some string or number. General rule: anything between a character ''%'' and the next letter-character (that is, ''a'', ''b'', 'c'', etc...) or percentage character (''%'') must be copied literally.
:#''\n'' must be copied literally too since it brakes the line into a new line. The general rule is: ''\'' and it's very next character (can be ''\'', ''a'', ''n'', ''t'', '',f'', ''"'', ''<nowiki>'</nowiki>'', etc) must be copied literally.
:#''&'' must be placed '''before'' the very same letter in the translation since it indicates the combination ALT+letter that will select that option.
:#The ending space is left since in the original message it was there. '''Never''' remove startng or ending spaces, even if they look ugly. They are there for some reason. Nomally this will be because either before or after that string comes another string. For example: ''"Opening file "'' has a blank space at the end, so you can expect that right after it the name of a file will be displayed. Something like ''Opening file server.met''