View source for HowTo Compile In RedHat-Fedora

<h1><font color=red>This article is being rewritten. Work in progress!</font></h1>

<h1>aMule in Fedora</h1> 
rev 0.1 by [[User:bootstrap|bootstrap]] <br>
rev 0.9 by iz0bbz - <font color=red>WORK in PROGRESS</font>

== Contents  ==

This page explains how to get a working [[aMule]] installation on [http://www.fedoraproject.org Fedora] distributions.<br>

It covers installing by pre-compiled [http://www.rpm.org RPM] packages available as well as building from sources.<br>


== Installing pre-compiled packages ==

First of all, be aware that pre-compiled packages may or may not include all amule features. It depends on configuration choices done by the packager.<br>
You can be sure that the amule 'monolithic' version is always included, but cannot say about other features (amule daemon, link creator or so).<br>


=== Installing via [http://fedoraproject.org/wiki/Tools/yum yum] ===

Amule is not included by default in official fedora repositories.
But it can be installed and automatically updated adding additional, external repositories to your Fedora system.<br>

[http://rpm.livna.org Livna] or [http://freshrpms.net freshrpms] are known to include the amule package in their repository.<br>
<font color=red>'''IMPORTANT NOTE: currently (June 2008) the 'old' amule 2.1.x versions only are available.'''<br></font>

You must first configure your Fedora system to use the external repositories. This is usually done manually installing a rpm, there are instructions available at repositories home page. For example, for [http://rpm.livna.org livna] you have to download:<br>

:http://rpm.livna.org/livna-release-9.rpm (for Fedora 9) <br>
:or <br>
:http://rpm.livna.org/livna-release-8.rpm (for Fedora 8) <br>

and then perform a ''rpm -i livna-release-x.rpm<br>

Then, you can install amule simply doing a :<br>

''yum install amule<br>

All dependencies will be automagically resolved by yum , and it will download and install the amule rpm package as well as all other rpm packages needed to run amule (wxGTK etc.)<br>

That's it ! Now you can just run 'amule' !<br>

=== Installing user-contributed RPM packages ===
You can find in the [http://forum.amule.org amule forum] user-contributed RPM packages for amule, both for the [http://forum.amule.org/index.php?board=69.0 stable version] and for [http://forum.amule.org/index.php?board=70.0 development versions]<br>

You need to install (if not already done)some libraries in order for amule to run.
Having a working internet connection, do a :<br>

''yum install wxGTK gettext GeoIP<br>

and then you can install the RPM package via a:<br>

''rpm -i <your-amule-RPM-package><br>

If there are other libraries still missing, rpm will warn you about the dependencies needed and stops the installation process. In that case you need to find out and install the missing libraries and repeat the command.<br>

(to be continued)<br>

<font color=red>To be rewritten. Work in progress!</font>
<br>
I said it's easy and it really is. The one and only rule to get an [http://www.rpm.org RPM] based [[aMule]] installation up and running is:

: Get the right [http://www.rpm.org RPM]s. That means:

: 1. Get [[wxWidgets|wxGTK]] and [[wxWidgets|wxBase]] from http://www.wxwidgets.org (you don't need the -devel packages to get [[aMule]] running) and install <!-- this should be a link --> them. Whatever someone else may say or you might think, don't use any other [[WxWidgets|wx]] [http://www.rpm.org RPM].

: 2. Install some additional [http://www.rpm.org RPM]s. On a common [http://www.redhat.com RedHat]-ish system you will have most of them, but I've read some questions regarding libcrypto (not [[libcrypto]]++, that's next...), so it's better to say that you will need to have openssl installed. If you're installing aMule <= 2.0rc6 you will also need to install [[libcrypto]]++ (we're talking about [[libcrypto]]++ from [http://www.eskimo.com/~weidai/cryptlib.html http://www.eskimo.com/~weidai/cryptlib.html]). You can find [http://www.rpm.org RPM]s for [http://www.redhat.com RedHat]/[http://fedora.redhat.org Fedora] on http://www.hirnriss.net or links on the [http://www.amule.org/amule/download.php aMule download page]. That should probably be all you [http://www.rpm.org RPM]s you will need to install by hand (actually [http://www.openssl.org openssl] will be installed on most systems, but as I mentioned before, there have been questions about that, so here you are...). If you're still getting a dependency problem and can't figure it out on your own, contact us through [[IRC]] (come to irc.freenode.net and visit #amule). Somebody will surely help you. Some [http://www.rpm.org RPM]s you should probably check are [http://www.openssl.org OpenSSL] and [http://www.gnu.org/software/make/manual/make.html automake] >= 1.7.

: 3. Get [[aMule]] from http://www.amule.org/dl/index.php?category=22 and install <!-- "install" should be a link to part 5 --> it.

That's it. If nothing went wrong you can drop your root privileges <!-- "root privileges" should be a link to part 3 --> and start [[aMule]]. That's as easy as typing ''amule &'' in your favourite shell. Have fun!

=== Compiling & installing amule from sources ===
<font color=red>To berewritten. Work in progress!</font>
==== First notes ====

So you're one of that guys that don't like [http://www.rpm.org RPM]s? Well - you asked for it...

Preparation:

You will need to get some [[wxWidgets|wx]] stuff. If you'd like to build [[wxBase]] and [[wxWidgets|wxGTK]] yourself, you will have to look into another howto. Building [[wxWidgets|wx]] can be complex and takes some time, so I really recommend to use the http://www.wxwidgets.org [http://www.rpm.org RPM]s.

As you want to build [[aMule]] yourself, you will need some more [http://www.rpm.org RPM]s than other people. Install [[wxWidgets|wxGTK]], [[wxBase]], [[wxWidgets|wxGTK]]-devel and [[wxBase]]-devel.

If you're building [[aMule]] <= 2.0rc6 you will also need [[libcrypto]]pp and [[libcrypto]]pp-devel ([http://www.redhat.com RedHat]/[http://fedora.redhat.com Fedora] downloads at [http://www.hirnriss.net http://www.hirnriss.net]) to get [[aMule]] compiled. Skip this if you're building [[aMule]] => 2.0rc7.

Get the sources you want (probably a cvs tarball from http://amule.hirnriss.net ?) from http://www.amule.org and un[http://www.gnu.org/software/tar/tar.html tar] it (if you don't know about tarballs, use [http://www.rpm.org RPM]s. Please!) into a directory you'd like to work in.

Drop your root privileges <!-- "root privileges" should be a link to part 3 --> and proceed to the fun part...

==== Configuring your [[aMule]] build ====

The following is an example, but it will work on [http://www.redhat.com RedHat]/[http://fedora.redhat.com Fedora] systems and it's been used for quite some time when building the "official" [[aMule]] [http://www.rpm.org RPM]s. Anyway, your system or your opinion may be different, so feel free to change the options if you feel like changing them.

''Note: If you're building [[aMule]] => 2.0rc7 you will have an embedded [http://www.openssl.org/docs/crypto/crypto.html crypto] lib that makes [[libcrypto]]++ installation obsolete. It's enabled by default, so you don't need to change your configure options.''

Go to the directory you created, change into the [[aMule]] sources and type (check the [[configure|configure article]]): ''./configure --prefix=/usr --enable-optimize --enable-amulecmd --enable-webserver --enable-utf8-systray --with-wx-config=/usr/bin/wxgtk-2.4-config --with-wxbase-config=/usr/bin/wxbase-2.4-config''

Now you should see a bunch of output, while your system tries to configure [[aMule]] for building. If you're '''NOT''' building a [http://www.gnu.org/software/cvs CVS] Version and you encounter problems, join the [[IRC|aMule IRC channel] at #amule on irc.freenode.net and prepare to paste some info. If your building a [http://www.gnu.org/software/cvs CVS] version you should probably wait a day and try again - it may just be some of those days where [http://www.gnu.org/software/cvs CVS] sources are not really working out for unexperienced users ;). If you're suspecting an interesting bug or just want to build that tarball whatever it takes, you're welcome to [[IRC]] in #amule as well, but bring some time because solving problems may not be as easy as installing [http://www.rpm.org RPM]s.

Once configure is done (should not take that long... 30 - 60 seconds on a modern system, a little more on older systems) type ''make'', sit down and relax. Depending on your systems speed this can take some time. Prepare for at least 5 minutes of strange output. If make stops check the last few lines of output for something that looks like an error message. If you can find something that looks like an error message, again, join [[IRC]], come to #amule and prepare for pasting or do a ''make clean'', try to change some of your configure options and restart ''make''. If it's still not working, ask someone at [[IRC]] in #amule on irc.freenode.net for help.

If your build completed without error you're nearly done.

Get root privileges and type ''make install'' to install your newly built [[aMule]]. Now drop your root privileges <!-- "root privileges" should be a link to part 3 --> and try to start [[aMule]] with ''amule &''. If your build was ok and you had a good day on [http://www.gnu.org/software/cvs CVS] versions you may have a great piece of software running by now. If your [[aMule]] instantly dies and produces a bunch of output containing words like "backtrace" - don't worry, Join [[IRC]] at #amule on irc.freenode.net and somebody might help you.

After building you can remove the directory you just built [[aMule]] in, as well as you can remove the installed -devel [http://www.rpm.org RPM]s. I suggest you leave the [http://www.rpm.org RPM]s in place in case you want to rebuild or build a new version some other day.

If nothing works and your home built [[aMule]] won't run, don't worry, try one of our [http://www.rpm.org RPM]s ;)

== Suggestions ==

This section is quite small (at the time of this writing) and contains some tips regarding [[aMule]] usage.

: * Drop your root privileges. Don't work/play/watch movies/drive a car/{you're favourite way to waste some time here} as root. Working as root can be dangerous. One mistake can lead to some interesting hours, restoring your system's health. If you know what you're doing: fine, but it's probably still better if you don't work as root.

: * Keep an eye on the [http://forum.amule.org aMule forum] and the [[Main_Page|aMule Project FAQ]] and probably use the search function: most questions have been answered before.

: * Don't drink and drive.

... to be continued ...

== Additional fun ==

This section covers additional ways to have fun with or around [[aMule]].

[http://www.uk.research.att.com/vnc VNC] Server. Did you ever think about using [[aMule]] on your server? If you don't like webservers and want to have more access to your system but a limited web GUI, this info is for you.

Using [[aMule]] in [http://www.uk.research.att.com/vnc VNC] is quite easy in [http://www.redhat.com RedHat]/[http://fedora.redhat.com Fedora], because you don't need more than a simple [http://www.rpm.com RPM] install <!-- "install" should be a link to part 5 --> of vnc-server and a minor modification to a startup script.

Just install vnc-server ([http://www.rpm.org RPM] comes with your installation CDs) and drop your root privileges<!-- "root privileges" should be a link to part 3 -->.
This howto assumes that your default user is named ''bob''.
As 'bob' do: ''vncserver -depth 16 :1''. If you never used [http://www.uk.research.att.com/vnc VNC] as 'bob' before, the [http://www.uk.research.att.com/vnc VNC] server should ask you for a password. This password is used to connect to your [http://www.uk.research.att.com/vnc VNC] session. It is ''not'' the password your user 'bob' has and it should not be set to the same password. Furthermore your [http://www.uk.research.att.com/vnc VNC] password can be only 8 letters/digits long, so you really should not set your users pw here.
The next step would be to test if your server is running as expected. Use you desktop or any other remote system to connect to your [http://www.uk.research.att.com/vnc VNC] session. To make sure you get the right port, use the following syntax: ''pizza:1'' or ''192.168.100.1'' assuming your server is named pizza and your [http://www.dns.net/dnsrd DNS] is running, or your server is running on the [http://www.faqs.org/rfcs/rfc791.html IP] 192.168.100.1 - if not, change the values to your needs.
Once your connection is up, you should be watching a very simple and nearly ugly desktop by now (i'm pretty sure the [http://www.plig.org/xwinman/vtwm.html twm] folks will kill me if they read this... sorry guys). This is because the default setting is to start only a little set of applications and a small window manager inside [http://www.uk.research.att.com/vnc VNC]. Go back to your shell and stop [http://www.uk.research.att.com/vnc VNC] using ''vncserver -kill :1'' as 'bob'. Now your [http://www.uk.research.att.com/vnc VNC] server should immediatly go offline. As next step edit ''/home/bob/.vnc/xstartup'' - uncomment the two lines below ''"Uncomment the following two lines for a normal desktop"'' and comment the rest. If you now start your [http://www.uk.research.att.com/vnc VNC] server again, you will have a fully functional [http://www.redhat.com RedHat]/[http://fedora.redhat.com Fedora] desktop. Now open a shell or use your window manager to start [[aMule]] and enjoy. One last hint: [http://www.uk.research.att.com/vnc VNC] uses encryption and timeouts to protect your password, but it's not perfectly secure. To get an even more secure system, I'd recommend using a screensaver on your newly created desktop. If you're using [http://www.kde.org KDE] you should have a nice button on your taskbar already. That should protect your system, even if your [http://www.uk.research.att.com/vnc VNC] password has been compromised.

To get the VNC server to launch when the machine boots, you can add the following to the end of <code>/etc/rc.d/rc.local</code>

<code>su username -c vncserver</code>

(replace username with the name of the user who'll be running all this.)

== How to use [http://www.rpm.org RPM] ==

There are several how to's on [http://www.rpm.org RPM] available so I won't try to write a new one. Here are some short hints to help you out in case you're completely new to your system and just want to follow the [[aMule]] installation from part 2.

Install: ''rpm -i rpmname'' (use the complete filename of your [http://www.rpm.org RPM], like: ''openssl-0.9.7a-35.i386.rpm'')

Remove: ''rpm -e rpmname'' (don't use the complete filename here, just the package name. Like ''openssl'', but not ''openssl-0.9.7a-35'')

Update: ''rpm -U rpmname'' (use the complete filename of your rpm, like: ''openssl-0.9.7a-35.i386.rpm'')

If you need any further info on [http://www.rpm.org RPM], please consult the rpm howto or use ''[http://www.rpm.org/max-rpm/rpm.8.html man rpm]''.