Difference between revisions of "HowTo Compile In Gentoo"

From AMule Project FAQ
Jump to: navigation, search
(=Compiling aMule=)
(→‎The SVN ebuild - updated the ChangeLog)
 
(93 intermediate revisions by 17 users not shown)
Line 1: Line 1:
−
<center>'''English''' | [[HowTo_Compile_In_Gentoo-es|Español]]</center>
+
<center>
 +
'''English''' |  
 +
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
 +
[[HowTo_Compile_In_Gentoo-es|Español]]
 +
</center>
  
−
Compiling a recent version of [[aMule]] on [http://www.gentoo.org Gentoo] should be a breeze by just typing ''emerge amule''. Unfortunately, it isn't quite that easy right now. So here's a little step by step explanation. Please read the entire document before attempting installation.
+
English version updated: 01.08.2009 - Newest Gentoo Version are now 2.2.5.
  
−
'''Note:''' currently Diego "Flameeyes" Pettenò (non-official devel) is trying to make the [[aMule]] emerge easier. Please take a look at [http://bugs.gentoo.org/show_bug.cgi?id=71108 Gentoo Bug #71108] for further information. The new ebuild requires, at minimum, [[wxGTK]] 2.5, but there is another ebuild for [[wxGTK]] 2.5 (also from Diego) which should allow to safely unmask that version.
+
== Introduction ==
 +
Gentoo is known for choices. As such, [[aMule]] comes in a variety of versions. This article will cover the installation of the last PORTAGE version, and of [[aMule SVN]] through a personal overlay.
  
−
== Available eBuilds ==
+
== Methods of Installation ==
 +
=== amule-2.2.5.ebuild ===
 +
This ebuild matches the 2.2.5 stable [[aMule]] release, it is available 28.08.2009 in portage.
  
−
The eBuild for [[aMule]]-2.0.1 can be found here:
+
Dependencies: >=x11-libs/wxGTK-2.8*; >=dev-libs/crypto++-5.5.2; >=sys-libs/zlib-1.2.1
−
http://bugs.gentoo.org/show_bug.cgi?id=71108
+
  
−
The eBuild for [[aMule CVS]] can be found here:
+
Conditional dependencies: >=dev-libs/geoip for geoip support; >=net-libs/libupnp for Intel UPnP stack support; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support and or statistic reporting.
−
http://forum.amule.org/thread.php?sid=&postid=30548
+
  
−
== Stable [[aMule]] from portage ==
+
== Installation instructions ==
  
−
If you just ''emerge amule'' you will install the version of [[aMule]] that [http://www.gentoo.org Gentoo] considers stable. This version is amule-1.2.8 which is over 12 months old, lacks several bugfixes and features which could seriously lower your downloads or make it impossible to connect to some servers. So this option is not really a good option.
+
=== amule-2.2.5.ebuild ===
 +
1. Show what will be done:
 +
  emerge -pv amule
 +
2. Adjust your USE flags for amule into ''/etc/portage/package.use
  
−
== Unstable [[aMule]] from portage ==
+
3. Emerge amule:
 +
  emerge -a amule
  
−
[http://www.gentoo.org Gentoo] classifies amule-2.0.0-rc releases as unstable because they are Release Candidates. The most current ebuild in Portage is ''net-p2p/amule-2.0.0-rc7.ebuild'' (masked by keyword).
+
=== amule SVN ===
 +
It is no ebuild for the current [[aMule SVN]] so we need to add one in portage. For that, we will make use of a personal portage overlay. If you don't already have one, just follow this HOWTO article: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay Overlay: Creating_a_local_overlay]
  
−
The most current, unofficial ebuild for [http://www.gentoo.org Gentoo] is amule-2.0.1.ebuild. Version 2.0.1 depends on ''>=wxGTK2.5.3'' (masked by keyword) to build the [[aMuled|aMule daemon]]. wxGTK 2.6.0 is suggested.
+
We will also follow the naming scheme of portage. SVN ebuild from a SVN tarball are not named as '''package_name-SVN''' but as '''package_name-version_date_of_the_tarball'''. That is to distinguish them from real SVN ebuilds (the so called live ebuilds) named as '''package_name-9999''' and using keywords="". As aMule is using the revision to name the tarball, we will use it for the '''version_date_of_the_tarball'''.
  
−
However, if rc7 is "good enough", fire up a console window and enter an su environment.
+
1. Define ''PORTDIR_OVERLAY''. Open up ''/etc/make.conf'' with your favourite text editor and define the ''PORTDIR_OVERLAY'' variable. We will use:
 +
  PORTDIR_OVERLAY="/usr/local/portage"
  
−
<code>mkdir /etc/portage<br>
+
2. Create overlay for amule-svn:
−
echo 'net-p2p/amule ~x86' >> /etc/portage/package.keywords<br>
+
  mkdir -p /usr/local/net-p2p/amule
−
emerge -av amule</code>
+
  
−
Keep in mind that rc7 is getting quite old now, so the best ebuilds to use would be for version 2.0.1 ([http://bugs.gentoo.org/show_bug.cgi?id=71108 Gentoo Bug #71108]) or even the recent CVS ([http://bugs.gentoo.org/show_bug.cgi?id=88243 Gentoo Bug #88243]).
+
3. Add to ''package.keywords'':
 +
  echo "net-p2p/amule ~x86" >> /etc/portage/package.keywords
  
−
== Recent [[aMule]] manual installation ==
+
4. Copy the following ebuild into ''{PORTDIR_OVERLAY}/net-p2p/amule/amule-9732.ebuild''
  
−
By default, [http://www.gentoo.org 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, unpredictable behaviour and may even harm your pet dog!
+
I use here the tarball from 31 July 2009 revision 9732 that was working fine for me, but you can change the revision like you want.  Be careful to choose a version number available on the [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.
  
−
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 [[aMuled|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).
+
==== The SVN ebuild ====
 +
ChangeLog:
 +
* 01-08-2009 Initial SVN ebuild
 +
* 04-08-2009 Updated DEPEND + RDEPEND
 +
* 27-08-2009 Updated for the 2_2_X trunk
 +
* 12-04-2011 USE flag change
 +
* 16-04-2011 Updated to EAPI="3
 +
* 14-10-2011 Workaround debian specific test with USE=plasma
 +
* 04-05-2012 Plasma need kde4-base that need EAPI="3" (Change in portage?). Fix it.  
 +
For more details, see the [http://forum.amule.org/index.php?topic=17143.0 forum thread].
  
−
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.
+
# Copyright 1999-2011 Gentoo Foundation
 +
# Distributed under the terms of the GNU General Public License v2
 +
# $Header: $
 +
 +
EAPI="3"
 +
 +
inherit eutils flag-o-matic kde4-base wxwidgets
 +
 +
MY_P="aMule-SVN-r${PV}"
 +
S="${WORKDIR}"/${MY_P}
 +
 +
DESCRIPTION="aMule, the all-platform eMule p2p client"
 +
HOMEPAGE="http://www.amule.org/"
 +
SRC_URI="http://amule.sourceforge.net/tarballs/${MY_P}.tar.bz2"
 +
 +
LICENSE="GPL-2"
 +
SLOT="0"
 +
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
 +
IUSE="daemon debug ed2k fileview geoip gtk mmap nls plasma remote static stats unicode upnp xchat"
 +
 +
RESTRICT="nomirror"
 +
 +
DEPEND="=x11-libs/wxGTK-2.8.12*
 +
>=dev-libs/crypto++-5.5.2
 +
>=sys-libs/zlib-1.2.1
 +
stats? ( >=media-libs/gd-2.0.26[jpeg] )
 +
geoip? ( dev-libs/geoip )
 +
plasma? ( kde-base/kdelibs )
 +
upnp? ( >=net-libs/libupnp-1.6.6 )
 +
remote? ( >=media-libs/libpng-1.2.0
 +
unicode? ( >=media-libs/gd-2.0.26 ) )"
 +
 +
RDEPEND="$DEPEND
 +
xchat? ( net-irc/xchat[perl] )"
 +
 +
 +
pkg_setup() {
 +
if ! use gtk && ! use remote && ! use daemon; then
 +
eerror ""
 +
eerror "You have to specify at least one of gtk, remote or daemon"
 +
eerror "USE flag to build amule."
 +
eerror ""
 +
die "Invalid USE flag set"
 +
fi
 +
 +
if use stats && ! use gtk; then
 +
einfo "Note: You would need both the gtk and stats USE flags"
 +
einfo "to compile aMule Statistics GUI."
 +
einfo "I will now compile console versions only."
 +
fi
 +
}
 +
 +
pkg_preinst() {
 +
if use daemon || use remote; then
 +
enewgroup p2p
 +
enewuser p2p -1 -1 /home/p2p p2p
 +
fi
 +
}
 +
 +
src_configure() {
 +
local myconf
 +
 +
WX_GTK_VER="2.8"
 +
 +
if use gtk; then
 +
einfo "wxGTK with gtk support will be used"
 +
need-wxwidgets unicode
 +
else
 +
einfo "wxGTK without X support will be used"
 +
need-wxwidgets base
 +
fi
 +
 +
if use gtk ; then
 +
use stats && myconf="${myconf}
 +
--enable-wxcas
 +
--enable-alc"
 +
use remote && myconf="${myconf}
 +
--enable-amule-gui"
 +
else
 +
myconf="
 +
--disable-monolithic
 +
--disable-amule-gui
 +
--disable-wxcas
 +
--disable-alc"
 +
fi
 +
 +
econf \
 +
--with-wx-config=${WX_CONFIG} \
 +
--enable-amulecmd \
 +
$(use_enable debug) \
 +
$(use_enable !debug optimize) \
 +
$(use_enable daemon amule-daemon) \
 +
$(use_enable ed2k) \
 +
$(use_enable fileview) \
 +
$(use_enable geoip) \
 +
$(use_enable mmap) \
 +
$(use_enable nls) \
 +
$(use_enable plasma plasmamule ) \
 +
$(use_enable remote webserver) \
 +
$(use_enable static) \
 +
$(use_enable stats cas) \
 +
$(use_enable stats alcc) \
 +
$(use_enable upnp) \
 +
$(use_enable xchat xas) \
 +
${myconf} || die
 +
}
 +
 +
src_compile() {
 +
cd ${S}
 +
emake
 +
}
 +
 +
src_install() {
 +
emake DESTDIR="${D}" install || die
 +
 +
if use daemon; then
 +
newconfd "${FILESDIR}"/amuled.confd amuled
 +
newinitd "${FILESDIR}"/amuled.initd amuled
 +
fi
 +
if use remote; then
 +
newconfd "${FILESDIR}"/amuleweb.confd amuleweb
 +
newinitd "${FILESDIR}"/amuleweb.initd amuleweb
 +
fi
 +
}
 +
  
−
== [[wxGTK]] 2.5.3 - 2.6.0 ==
 
  
−
If you want to use amuled then you need, at least, ''wxGTK2.5.3''. Currently, the only version not hard masked in Portage is [[wxGTK]] 2.4.2 due to problems when compiling with [http://www.opengl.org OpenGL] support in [[wxGTK]] 2.5.3. But as [[aMule]] is no 3D egoshooter, we can safely disable [http://www.opengl.org OpenGL] support and use it anyway. To do so enter the following into a console as root:
+
5. Change directory:
 +
  cd /usr/local/portage/net-p2p/amule/
  
−
<code>mkdir /etc/portage (this may give you an error if the directory already exists, just ignore that)<br>
+
6. Copy the files directory from PORTAGE:
−
echo 'x11-libs/wxGTK ~x86' >> /etc/portage/package.keywords<br></code>
+
  cp -r /usr/portage/net-p2p/amule/files files
  
−
If you want to use ''GTK1.2'' (recommended):<br>
+
7. Remove the unneeded files:
−
<code>echo 'x11-libs/wxGTK -gtk2 -unicode -opengl' >> /etc/portage/package.use<br></code>
+
  rm files/*.patch
  
−
If you want to use ''GTK2'' (not thoroughly tested yet):<br>
+
8. Digest the ebuild:
−
<code>echo 'x11-libs/wxGTK -unicode -opengl' >> /etc/portage/package.use<br></code>
+
  ebuild amule-9732.ebuild digest
  
−
<code>emerge -av wxGTK</code>
+
9. As you can see, this ebuild depend on x11-libs/wxGTK-2.8.12 which is not yet in portage. You can find it at [http://bugs.gentoo.org/show_bug.cgi?id=363319 Gentoo's Bugzilla – Bug 363319]. What you have to do is to dpwnload the ebuild from bugzilla and put it into the x11-libs/wxGTK directory of your overlay. You must also copy the files directory from PORTAGE and digest the ebuild:
 +
  cd /usr/local/portage/x11-libs/wxGTK
 +
  cp -r /usr/portage/x11-libs/wxGTK/files files
 +
  ebuild wxGTK-2.8.12.ebuild digest
  
−
'''Note:''' There are 2 ebuilds available for amule-cvs. A version with [http://bugs.gentoo.org/attachment.cgi?id=58059&action=view >=wxGTK 2.6.0] support and a version with [http://bugs.gentoo.org/attachment.cgi?id=55546&action=view <=wxGTK 2.5.3] support. Please use the correct version depending on what version of wxGTK you choose to use. Of course, wxGTK 2.6.0 is recommended.
+
10. Review installation flags:
 +
  emerge amule -pv
  
−
== [[wxGTK]] 2.4.2 ==
+
11. Modify ''/etc/portage/package.use'' to suit your needs (please note that ''debug'' is enabled regardless of ''USE'' flag):
 +
  net-p2p/amule -amuled -debug geoip gtk nls -remote -stats unicode
  
−
If you don't want to use the [[aMuled|aMule daemon]], ''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):
+
This would install amule without deamon and remote support.
 +
To activate deamons and remote options, leave out the '-' like this:
  
−
<code>mkdir /etc/portage (this may give you an error if the directory already exists, just ignore that)<br>
+
  net-p2p/amule amuled -debug geoip gtk nls remote -stats unicode
−
echo 'x11-libs/wxGTK -gtk2 -unicode' >> /etc/portage/package.use<br>
+
−
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]].
+
As aMule needs unicode support or it won't compile, you might also want to add a line to enable unicode in x11-libs/wxGTK
 +
  x11-libs/wxGTK unicode
  
−
== Compiling [[aMule]] ==
+
12. Install [[aMule SVN]]:
 +
  emerge amule
  
−
Grab either ''amule-2.0.1'' from http://www.aMule.org or (specially if you want to use [[aMuled]]) a recent [[aMule CVS|CVS tarball]] from http://amule.hirnriss.net. Untar it by entering <code>tar -xvjf aMule-foo.tar.bz2</code> and go into the newly created directory.
+
'''PLEASE''' do ''emerge amule -pv'' before installing to determine how you want to compile [[aMule]].
  
−
Review <code>./configure --help</code> (or [[configure|this article]]) for a summary of all configure options. Pick the ones you want and run (as an example building, the monolithic client and [[aMuleCMD]])<br>
+
13. As other programs can depend on wxGTK, it can be a good opportunity to update your system as usual. emerge --sync, and so on as explained into the handbook.
−
<code>./configure --enable-amulecmd</code>
+
  
−
Review 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.
+
==== Possible crash ====
 +
On my ~amd64 system, I get a crash at amule startup with recent libcrypto++ versions.
 +
To avoid it, mask it into /etc/portage/package.mask:
 +
echo =dev-libs/crypto++-5.6.0 >> /etc/portage/package.mask
 +
echo =dev-libs/crypto++-5.6.0-r1 >> /etc/portage/package.mask
 +
echo dev-libs/crypto++-5.6.1 >> /etc/portage/package.mask
 +
emerge -a crypto++ amule
 +
revdep-rebuild
 +
Revdep-rebuild didn't find anything into my system, but it is safer to run it anyway.
 +
 
 +
Another solution is to use the ebuild and the patch in [http://bugs.gentoo.org/show_bug.cgi?id=322713 bug 322713] for merging the last version of libcrypto++.
 +
 
 +
'''Update:''' It look like to be fixed. If it should append again with the same crypto++ version, please ask to reopen this bug.

Latest revision as of 16:58, 9 May 2012

English | Deutsch | Español

English version updated: 01.08.2009 - Newest Gentoo Version are now 2.2.5.

Introduction

Gentoo is known for choices. As such, aMule comes in a variety of versions. This article will cover the installation of the last PORTAGE version, and of aMule SVN through a personal overlay.

Methods of Installation

amule-2.2.5.ebuild

This ebuild matches the 2.2.5 stable aMule release, it is available 28.08.2009 in portage.

Dependencies: >=x11-libs/wxGTK-2.8*; >=dev-libs/crypto++-5.5.2; >=sys-libs/zlib-1.2.1

Conditional dependencies: >=dev-libs/geoip for geoip support; >=net-libs/libupnp for Intel UPnP stack support; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support and or statistic reporting.

Installation instructions

amule-2.2.5.ebuild

1. Show what will be done: 

 emerge -pv amule

2. Adjust your USE flags for amule into /etc/portage/package.use

3. Emerge amule: 

 emerge -a amule

amule SVN

It is no ebuild for the current aMule SVN so we need to add one in portage. For that, we will make use of a personal portage overlay. If you don't already have one, just follow this HOWTO article: Overlay: Creating_a_local_overlay

We will also follow the naming scheme of portage. SVN ebuild from a SVN tarball are not named as package_name-SVN but as package_name-version_date_of_the_tarball. That is to distinguish them from real SVN ebuilds (the so called live ebuilds) named as package_name-9999 and using keywords="". As aMule is using the revision to name the tarball, we will use it for the version_date_of_the_tarball.

1. Define PORTDIR_OVERLAY. Open up /etc/make.conf with your favourite text editor and define the PORTDIR_OVERLAY variable. We will use: 

 PORTDIR_OVERLAY="/usr/local/portage"

2. Create overlay for amule-svn: 

 mkdir -p /usr/local/net-p2p/amule

3. Add to package.keywords: 

 echo "net-p2p/amule ~x86" >> /etc/portage/package.keywords

4. Copy the following ebuild into {PORTDIR_OVERLAY}/net-p2p/amule/amule-9732.ebuild

I use here the tarball from 31 July 2009 revision 9732 that was working fine for me, but you can change the revision like you want. Be careful to choose a version number available on the tarballs page, otherwise your ebuild will fail.

The SVN ebuild

ChangeLog:

  • 01-08-2009 Initial SVN ebuild
  • 04-08-2009 Updated DEPEND + RDEPEND
  • 27-08-2009 Updated for the 2_2_X trunk
  • 12-04-2011 USE flag change
  • 16-04-2011 Updated to EAPI="3
  • 14-10-2011 Workaround debian specific test with USE=plasma
  • 04-05-2012 Plasma need kde4-base that need EAPI="3" (Change in portage?). Fix it.

For more details, see the forum thread. 

# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $

EAPI="3"

inherit eutils flag-o-matic kde4-base wxwidgets

MY_P="aMule-SVN-r${PV}"
S="${WORKDIR}"/${MY_P}

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://amule.sourceforge.net/tarballs/${MY_P}.tar.bz2"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="daemon debug ed2k fileview geoip gtk mmap nls plasma remote static stats unicode upnp xchat"

RESTRICT="nomirror"

DEPEND="=x11-libs/wxGTK-2.8.12*
	>=dev-libs/crypto++-5.5.2
	>=sys-libs/zlib-1.2.1
	stats? ( >=media-libs/gd-2.0.26[jpeg] )
	geoip? ( dev-libs/geoip )
	plasma? ( kde-base/kdelibs )
	upnp? ( >=net-libs/libupnp-1.6.6 )
	remote? ( >=media-libs/libpng-1.2.0
	unicode? ( >=media-libs/gd-2.0.26 ) )"

RDEPEND="$DEPEND
	xchat? ( net-irc/xchat[perl] )"


pkg_setup() {
	if ! use gtk && ! use remote && ! use daemon; then
		eerror ""
		eerror "You have to specify at least one of gtk, remote or daemon"
		eerror "USE flag to build amule."
		eerror ""
		die "Invalid USE flag set"
	fi

	if use stats && ! use gtk; then
		einfo "Note: You would need both the gtk and stats USE flags"
		einfo "to compile aMule Statistics GUI."
		einfo "I will now compile console versions only."
	fi
}

pkg_preinst() {
	if use daemon || use remote; then
		enewgroup p2p
		enewuser p2p -1 -1 /home/p2p p2p
	fi
}

src_configure() {
	local myconf

	WX_GTK_VER="2.8"

	if use gtk; then
		einfo "wxGTK with gtk support will be used"
		need-wxwidgets unicode
	else
		einfo "wxGTK without X support will be used"
		need-wxwidgets base
	fi

	if use gtk ; then
		use stats && myconf="${myconf}
			--enable-wxcas
			--enable-alc"
		use remote && myconf="${myconf}
			--enable-amule-gui"
	else
		myconf="
			--disable-monolithic
			--disable-amule-gui
			--disable-wxcas
			--disable-alc"
	fi

	econf \
		--with-wx-config=${WX_CONFIG} \
		--enable-amulecmd \
		$(use_enable debug) \
		$(use_enable !debug optimize) \
		$(use_enable daemon amule-daemon) \
		$(use_enable ed2k) \
		$(use_enable fileview) \
		$(use_enable geoip) \
		$(use_enable mmap) \
		$(use_enable nls) \
		$(use_enable plasma plasmamule ) \
		$(use_enable remote webserver) \
		$(use_enable static) \
		$(use_enable stats cas) \
		$(use_enable stats alcc) \
		$(use_enable upnp) \
		$(use_enable xchat xas) \
		${myconf} || die
}

src_compile() {
	cd ${S}
	emake
}

src_install() {
	emake DESTDIR="${D}" install || die

	if use daemon; then
		newconfd "${FILESDIR}"/amuled.confd amuled
		newinitd "${FILESDIR}"/amuled.initd amuled
	fi
	if use remote; then
		newconfd "${FILESDIR}"/amuleweb.confd amuleweb
		newinitd "${FILESDIR}"/amuleweb.initd amuleweb
	fi
}


5. Change directory: 

 cd /usr/local/portage/net-p2p/amule/

6. Copy the files directory from PORTAGE: 

 cp -r /usr/portage/net-p2p/amule/files files

7. Remove the unneeded files: 

 rm files/*.patch

8. Digest the ebuild: 

 ebuild amule-9732.ebuild digest

9. As you can see, this ebuild depend on x11-libs/wxGTK-2.8.12 which is not yet in portage. You can find it at Gentoo's Bugzilla – Bug 363319. What you have to do is to dpwnload the ebuild from bugzilla and put it into the x11-libs/wxGTK directory of your overlay. You must also copy the files directory from PORTAGE and digest the ebuild: 

 cd /usr/local/portage/x11-libs/wxGTK
 cp -r /usr/portage/x11-libs/wxGTK/files files
 ebuild wxGTK-2.8.12.ebuild digest

10. Review installation flags: 

 emerge amule -pv

11. Modify /etc/portage/package.use to suit your needs (please note that debug is enabled regardless of USE flag): 

 net-p2p/amule -amuled -debug geoip gtk nls -remote -stats unicode

This would install amule without deamon and remote support. To activate deamons and remote options, leave out the '-' like this: 

 net-p2p/amule amuled -debug geoip gtk nls remote -stats unicode

As aMule needs unicode support or it won't compile, you might also want to add a line to enable unicode in x11-libs/wxGTK 

 x11-libs/wxGTK unicode

12. Install aMule SVN: 

 emerge amule

PLEASE do emerge amule -pv before installing to determine how you want to compile aMule.

13. As other programs can depend on wxGTK, it can be a good opportunity to update your system as usual. emerge --sync, and so on as explained into the handbook.

Possible crash

On my ~amd64 system, I get a crash at amule startup with recent libcrypto++ versions. To avoid it, mask it into /etc/portage/package.mask: 

echo =dev-libs/crypto++-5.6.0 >> /etc/portage/package.mask
echo =dev-libs/crypto++-5.6.0-r1 >> /etc/portage/package.mask
echo dev-libs/crypto++-5.6.1 >> /etc/portage/package.mask
emerge -a crypto++ amule
revdep-rebuild

Revdep-rebuild didn't find anything into my system, but it is safer to run it anyway.

Another solution is to use the ebuild and the patch in bug 322713 for merging the last version of libcrypto++.

Update: It look like to be fixed. If it should append again with the same crypto++ version, please ask to reopen this bug.

Retrieved from "http://wiki.amule.org/t/index.php?title=HowTo_Compile_In_Gentoo&oldid=28425"