AMule Project FAQ - User contributions [en]

Install-amule-freebsd

2004-05-31T14:17:08Z

80.224.220.9:

This page is likely to be updated soon, but it might help you even right now.

== Install amule 2.0.0rc3 on freebsd 5.x ==

Why would u ask... we have /usr/ports/net/amule

Well, this is the stable version 1.2.6

We wanna stay current or help testing / debugging, why else would u read this?

== Install ports we need if u dont allready have (see ''pkg_info'') ==

''security/cryptopp''

and

''x11-toolkits/wxgtk''

and (but you will have this already ;-)

''devel/gettext''

and (but you will also have this already ;-)

''devel/gmake''

You know how to install ports as a BSD user, so I don't have to tell you, I hope. It's just too easy you know. In case you're very new to FreeBSD, consult the great handbook at [http://www.freebsd.org].

'''NOTE:''' If you think you have wxGTK installed because you see wxGTK2, you should know, wxGTK is linked against GTK1 and wxGTK2 is linked against GTK2. Using wxGTK2 with aMule will become aMule unstable! You have to use wxGTK, not wxGTK2.

== Configure ==

The ./configure does not work 100% automagically, we must help it out a bit.

I used the following line of configure, wich may differ for you a bit due to different OS or library versions you have installed

Right now this line works for FreeBSD 5.2-CURRENT 03-May-2004 for example but version numbers may be different for FreeBSD 5.2.1 or the upcomming 5.3.

Edit the <your home> tag, of course, or install it elsewhere.

''./configure --prefix=/home/<your home>/amule --with-wx-config=/usr/X11R6/bin/wxgtk-2.4-config --with-wxbase-config=/usr/X11R6/bin/wxgtk-2.4-config''

NOTE: This is one single line, not 3 lines or whatever wiki/html/your browser wraps this line into.

You will see configure doesn't find gdlib-config, even if you installed gdlib. dont care, its just not there and its no "must have". Just skip it.

'''NOTE:''' If you get the following warning

''WARNING!! Your wxWidgets copy has been linked against GTK2 and this will make aMule be unstable, use so much cpu and ram. You have been advised, don't report bugs so.''

at the end of configure you are probably linking against wxGTK2 instead of wxGTK. aMule will memleak and eat your CPU. It will probably crash as well. Use wxGTK as mentioned above!

== Patch 1 ==

The problem would be:

'''<pre>[...]
/usr/bin/ld: cannot find -lcryptopp
gmake[2]: *** [cas] Error 1
gmake[2]: Leaving directory `/home/eugene/aMule-2.0.0rc3/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/eugene/aMule-2.0.0rc3'
gmake: *** [all] Error 2</pre>'''

So we patch it now:

''edit src/Makefile''

Search for the line containing

''cryptopp''

This line will read as:

''LIBS = -lcryptopp''

Add ''-L/usr/local/lib'' to that line

Now the line will read as:

''LIBS = -L/usr/local/lib -lcryptopp''

== Patch 2 ==

The problem would be:

'''<pre>[...]
amule.cpp:39:30: execinfo.h: No such file or directory
amule.cpp:40:28: mntent.h: No such file or directory
In file included from /usr/local/include/cryptopp/pkcspad.h:4,
from /usr/local/include/cryptopp/rsa.h:9,
from ClientCredits.h:32,
from amule.cpp:86:
/usr/local/include/cryptopp/cryptlib.h:1358:9: warning: "/*" within comment
amule.cpp: In member function `virtual bool CamuleApp: nInit()':
amule.cpp:423: error: `setmntent' undeclared (first use this function)
amule.cpp:423: error: (Each undeclared identifier is reported only once for
each function it appears in.)
amule.cpp:429: error: `getmntent' undeclared (first use this function)
amule.cpp:431: error: invalid use of undefined type `struct mntent'
amule.cpp:427: error: forward declaration of `struct mntent'
amule.cpp:432: error: invalid use of undefined type `struct mntent'
amule.cpp:427: error: forward declaration of `struct mntent'
amule.cpp:437: error: invalid use of undefined type `struct mntent'
amule.cpp:427: error: forward declaration of `struct mntent'
amule.cpp: In member function `virtual void CamuleApp: nFatalException()':
amule.cpp:982: error: `backtrace' undeclared (first use this function)
amule.cpp:987: error: `backtrace_symbols' undeclared (first use this function)
gmake[2]: *** [amule-amule.o] Error 1
gmake[2]: Leaving directory `/home/eugene/aMule-2.0.0rc3/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/home/eugene/aMule-2.0.0rc3'
gmake: *** [all] Error 2</pre>'''

So we patch it now:

As there is no official FreeBSD support in aMule yet we will patch it to work... Well there is OpenBSD support and this support will work for us too :-)

Edit ''src/amule.cpp''

and insert

''#define __OPENBSD__''

at the top of this file. I placed it right before the first ''#include'' line...

"What a workaround!" you may scream. Hey, we don't fiddle too much around with the code, just hack it to work and get ready to share ;-)

== Make ==

''make'' will fail, use ''gmake''

''make'' is BSD make, ''gmake'' is gnu make. They are '''not''' compatible.

Now do:

''gmake''

Get yourself a hot green tea (I prefer some sort of sencha) while it is compiling.

Then do:

''gmake install''

== Use it ==

Just start it with ''/home/<your home>/amule/bin/amule''
or wherever you installed it to...

Have phun

Eugene

== Update - Using the port ==

I've just released the 2.0.0rc3 port.
See [http://www.amule.org/amule/download.php] (and [http://contribs.martymac.com]) to download it.

Since the port is not (yet) officially available, you'll have to uncompress it (''tar xvzf file.tgz'') into the ''/usr/ports/net'' directory and then do a standard ''make install''.

Any feedback welcome, many thanks to Eugene for this great wiki :)

Ganael Laplanche.

Main Page

2004-05-31T13:59:22Z

80.224.220.9:

== Welcome to the Wikipedia of aMule Project ;-) ==

http://www.amule.org/images/logo.gif

We hope you will find some answers for your questions and problems!

aMule Team

 
== FAQs: ==

FAQ [[FAQ_aMule|on aMule]] ([[FAQ-es|Spanish]]) 
FAQ [[FAQ_eD2k/Kademlia|on ED2K/Kademlia]] 

 

== Help: ==

Howto [[Compilation Installation|compile/install aMule from scratch]] 
Howto [[Install-amule-freebsd|compile aMule on FreeBSD]] 
Howto [[HowTo compile on Win32|compile aMule on Windows]] 
Howto [[HowTo_Compile_In_Debian| compile aMule in Debian]] 
Howto [[CryptoppDebian|make Crypto++ work on Debian]] 
Howto [[MDK10_install|install aMule in Mandrake 10]] 
Howto [[Backtraces|create backtraces]] to help the [[aMule_devs|aMule devs]] 
Howto [[Firewall|setup iptables for aMule]] 
Howto [[Ed2k links handling|handle ed2k:// links]] 
Howto [[Webserver|Webserver configuration]] for aMule >= 2.0.0rc1 
Howto [[Debian_fonts|Font problems on Debian]] 
Howto [[Mule_Project_Wikipedia:Help|edit a page]]

AMule Project FAQ:Help

2004-05-12T19:25:52Z

80.224.220.9:

HowTo Compile In MDK

2004-05-12T19:25:32Z

80.224.220.9:

This how-to explains the way to install and compile aMule on Mandrake 10 by using urpmi. I guess it would work in any other Mandrake version but I haven't tried it.

The problem when installing aMule on Mandrake 10, is that wxBase official Mandrake package is linked against GTK2 and aMule needs it to be linked against GTK1. However it's needed to use the wx rpm packages from the aMule website.

This can be done following the how-to in the page of aMule, but when doing it with urpmi, you have the advantage of controlling the version conflict between Mandrake's wxBase package and aMule's website package every time you update your system.

There are others packages needed to install aMulle on Mandrake. However, in this case, Mandrake official packages are fine. These packages are:

curl 
libcrypto 
libgd <----- this is needed only to use the -o option of cas. If you're not going to use that option, you don't have to install it.

If you also want to compile aMule, you must install the devel packages corresponding to those:

curl-devel 
libcrypto-devel 
libgd-devel 

To install all this packages, you must have well-configured urpmi sources (look easyurpmi or urpmidor to verify). If you have them well-configured, you only must do:

'''urpmi curl''' 
'''urpmi libcrypto''' 
'''urpmi libgd'''

'''urpmi curl-devel''' 
'''urpmi libcrypto-devel''' 
'''urpmi libgd-devel'''

Let's start

1. Create a dir to put in wxGTK and wxBase rpm packages from the aMule website.

'''mkdir /home/user/RPMS'''

copy there:

wxGTK-2.4.2.rpm 
wxBase-2.4.2.rpm 
aMule-2.0.0rc3-MDK_9.2-10.rpm o aMule-1.2.6-MDK_9.2-10.rpm

if you also want to compile aMule you must also copy:

wxGTK-devel-2.4.2.rpm

2. Get in the new dir,

'''cd /home/user/RPMS'''

and run genhdlist to create hdlist.cz

'''genhdlist'''

3. Add that dir as a new source to urpmi

'''urpmi.addmedia dirRPMS file://home/user/RPMS with hdlist.cz'''

4. Go to RPMDRAKE, Remove Software, and search wx. Select wxBase, wxGTK and wxGTK-devel, and remove all of them from your computer. If your computer doesn't find any of them, it just wasn't installed, so there's no need to remove it ;)

5. Install wxGTX packages from dirRPMS source by doing:

'''urpmi wxGTK-2.4.2'''

if you also want to compile aMule you must also install

'''urpmi wxGTK-devel-2.4.2'''

6. Install wxBase package

'''urpmi wxBase-2.4.2'''

Make sure you install the right packages from dirRPMS copying their exact name after urpmi.

then you must create the following symbolic links:

'''ln -sf /usr/bin/wxgtk-2.4-config /usr/bin/wx-config'''

'''ln -sf /usr/bin/wxbase-2.4-config /usr/bin/wxbase-config'''

7. Now you can do

'''urpmi aMule-2.0.0rc3-MDK_9.2-10.rpm'''

or

'''urpmi aMule-1.2.6-MDK_9.2-10.rpm'''

or compile aMule from the sources .tar.gz

Following this how-to, you get an easy way to install back all of the packages that urpmi will remove each time yo update your system with urpmi --auto-select.

After updating the system with urpmi you must remove back wxBase (and wxGTK if it also changes it), and then install the packages from dirRPMS as we have done before.

Main Page

2004-05-12T19:25:00Z

80.224.220.9:

== Welcome to the Wikipedia of aMule Project ;-) ==

http://www.amule.org/images/logo.gif

We hope you will find some answers for your questions and problems!

aMule Team

 
== FAQs: ==

FAQ [[FAQ_aMule|on aMule]] 

 
== Help: ==

Howto [[Compilation Installation|compile/install aMule from scratch]] 
Howto [[HowTo_Compile_In_Debian| compile aMule in Debian]] 
Howto [[CryptoppDebian|make Crypto++ work on Debian]] 
Howto [[Firewall|setup iptables for aMule]] 
Howto [[Backtraces|create backtraces]] to help the aMule devs. 
Howto [[Install-amule-freebsd|aMule 2.0.0rc3]] compilation under FreeBSD 
Howto [[Webserver|Webserver configuration]] for aMule => 2.0.0rc1 
Howto [[MDK10_install|install aMule in Mandrake 10]] 
Howto [[Mule_Project_Wikipedia:Help|edit a page]]

Backtraces

2004-04-30T23:49:22Z

80.224.220.9:

Well, not hard to guess, this is about backtraces.

Usually, it should not be necessary for the normal user to do this. However, we might have a bad day and release a somewhat buggy version or you are running CVS which can also be unstable sometimes.
This is where the backtraces come in: if aMule crashes, and you get an "OOPS - aMule crashed" and so on, we'd like to know. The backtrace aMule provides is not always very usefull as it contains little information, but, as usual, there's a better way: A *real* backtrace.

First of all, you need the GNU Debugger installed. It's called gdb and you could check for that by typing 'which gdb' in a console window. You should see something like this:

$ which gdb
/usr/bin/gdb

If you dont have gdb installed, you will get a message like this:
$ which gdb
which: no gdb in (/bin:/usr/bin:[sic])

If that is the case, the GNU Debugger is most likely not installed on your system and you should install it before you proceed.

Then, compile aMule with debugging information:
$ ./configure --enable-debug --disable-optimise --prefix=/where/to/install/aMule
$ make
$ make install

If you do not want to overwrite you old copy of aMule, simply do this instead:
$ ./configure --enable-debug --disable-optimise
$ make

aMule can then be run by cd'ing to the dir 'src' and typing ./amule

If you are unable or unwilling to recompile, or are running a *.rpm version, proceed anyway, but be aware that backtraces from debugging enabled builds are much more useful to us.

To create a backtrace, do the following:
<ol>
<li>Run "gdb /where/to/install/aMule/bin/amule".
<li>Enter "ha SIGPIPE nostop noprint pass" after (gdb) prompt (to avoid gdb stopping at broken pipes).
<li>Enter "ha SIG32 nostop noprint pass" (to avoid gdb stopping at new thread).
<li>Enter "run".
<li>Use aMule normally until it crashes.
<li>Enter "bt".
<li>Enter "bt full".
<li>Post the output of the last two steps in the [http://www.amule.org/amule/board.php?boardid=33&sid= backtraces forum] with some additional comment about the circumstances the segfault happened and what aMule version you used (or checkout time for CVS).
</ol>

So, that's it, have fun with aMule

greetings, Citroklar

(most of the above shamelessly stolen from pure_ascii's post in backtraces forum, thanks, pure!)