AMule Project FAQ - User contributions [en]

AMule problems

2012-05-22T16:35:16Z

Libre: /*aMule's Preview hang MPlayer? */

<center>
'''English''' |
[[AMule_problems-de|Deutsch]] |
[[AMule_problems-es|Español]] |
[[AMule_problems-hu|Magyar]] |
[[AMule_problems-it|Italiano ]] |
[[AMule_problems-nl|Nederlands]]
</center>

== Where are my downloaded files? ==
By default, aMule stores completed files in ''~/.aMule/Incoming'' but, since ''~/.aMule'' directory is a hidden directory, your file manager might not show it. Make sure you have enabled your file manager to show hidden files.

By default, files being downloaded are placed in ''~/.aMule/Temp'', so again, this is a hidden directory and the file managed must be configured to show hidden files.

On a Macintosh downloads are in ''~/Library/Application Support/aMule/Incoming'' and Windows users can find downloads in the folder ''aMule downloads'' in their user folder.

== Why is aMule taking so much CPU resources at start-up? ==
This happens because aMule is hashing new files found on the Shared Directories.

If aMule is always taking a lot of CPU at startup and no new files have been added or modified in any way in the Shared Directories, then something is wrong.

In aMule versions earlier than 2.0.0-rc3 this used to happen when having the Temp, Incoming or any Shared Directory in a FAT32 partition. Since aMule 2.0.0-rc3 this is not happening any more.

Also, in aMule versions earlier than 2.0.0-rc4 filesystems with UTF-8 encoding (known to happen with SuSE 9.1) could present problems when some file or directory in the Shared Directories path contained a special character. If this is your problem, there's a workaround (thanks '''nachbarnebenan'''): after aMule has hashed all shared files (that is, when it stops taking a lot of your CPU's resources), close aMule and enconde ~/.aMule/known.met into UTF-8 encoding (you can do this with the application ''[http://www.gnu.org/directory/recode.html recode]'' by running the following command: ''recode u8 ~/.aMule/known.met''). This should be done whenever a files is added or modified in any Shared Directory. So, best option is to upgrade to latest aMule version.

If non of the above helps you, then something went really wrong on ''known.met'' file, probably some external program or user broke it. Best option is to delete it, start aMule and let aMule rehash all files again.

== So now aMule starts, but why is it displaying this message: "No valid servers to connect in serverlist found"? ==
That's because you enabled the option "Auto connect to servers the static list only". So, disable it or add some server to the static list.

To disable that option, go to Preferences -> Servers -> "Auto connect to servers the static list only"

To add a server to the static list, go to the Servers window and right-click on the server you want to add to the static list. Then select "Add to static" and do this exact process wit all the servers you want to add to the static list.

== Why does it happen that sometimes aMule suddenly has no/few servers in is server list? ==
You probably have enabled the options Preferences -> Servers -> "Remove dead server after X retries" and Preferences -> Connection -> "Reconnect on loss".

If so, most probably you lost internet (or lan, etc) connection for a period of time so aMule noticed it was not connected to the ed2k server anymore and went trying to connect to other servers until all servers were removed (after trying X times each).

To solve this problem, disable the "Remove dead server after X retries" option. Disabling the option "Remove dead server after X retries" is safe in most cases. You most probably don't want to disable the "Reconnect on loss" option, so keep it enabled.

== aMule connects to server, but it is always given Low-ID. Why? and, can I do something about it? ==
This can bue due to three reasons:
*Some necessary port is not opened in your firewall. Read [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|this]] to get to know what to do and check [http://www.amule.org/testport.php here] if the ports are open.
*The server is very busy or maybe badly configured, so it's giving you a [[Low ID|Low-ID]]. There's nothing that can be done in this case other than reconnect or connect to some other server.
*Some ISP forbid the use of p2p applications, such as aMule, by not allowing traffic through popular p2p ports. In these cases, configure aMule to use some other port. It would be even better if it was some popular port used for some other issue. It's been known that on some ISPs it worked with port TCP 25600.

== [[aMule]] was interrupted while completing a file and it is now never completing it (although it's 100% downloaded). How can I complete it? ==
This one is easy: Close [[aMule]]. Now go into the Temp directory (by default, ''~/.aMule/Temp'') and run the following command:

''touch ./*''

Finally, run [[aMule]] and let it complete the files.

== I just lost a download. Is there any way I can recover it? ==
This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault). 
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted.

If *.part files have disappeared, the only solution is to restart the downloads from the beginning (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them.

If *.part.met files have disappeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running:

''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''

Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this:

Either, use [http://www.bigwillystyle42.com/mfr/ MetFileRegenerator] (Java needed) to reconstruct the *.part.met files.

Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you were downloading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have mysteriously disappeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddenly become unresponsive to the mouse although it's not hanged? ==
It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive until you click OK, Cancel, or whatever you have to click.

So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==
This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time).

However, on some releases it has happened that after restarting aMule, some files dissapear from the Shared Folders window although they are in the shared folders. In such cases, the only way to have them back is to delete ''~/.aMule/known.met'' but, of course, on next aMule start, all shared files will have to be rehashed, and that will take some time most probably.

== I always get a message about addresses.met when I start aMule. What's wrong? ==
This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it.

== I sometimes get a message on the log about credits being lost. Should I be worried? ==
No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you shouldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==
Losing this files means you lose all of your credits. Sorry. Since you'll need to start building credits up again, you'll need to delete ''~/.aMule/preferences.dat'' or you'll not be able to collect credits on [[client|clients]] who have previously identified you (prior to losing cryptkey.dat).

== Why is Upload/Download limit always back to 0 after every restart? ==
This happened on aMule versions previous to 2.0.0-rc4 when you trying to set a Upload or Download limit value higher than the Upload or Download Capacity value. However, since version 2.0.0-rc4 this is fixed (read [[FAQ_aMule#What_is_the_real_point_on_setting_up_Line_Capacities_in_Preferences?_Shouldn't_aMule_only_care_for_the_Bandwidth_Limits?|What is the real point on setting up Line Capacities
in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] to understand why) and shouldn't happen anymore.

== Why is aMule ignoring the bandwidth I set per slot? ==
The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time.

So, the maximum speed allowed per slot is '''BandwidthLimit/3'''.

Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwidth Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive.

Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth.

Example:
*Bandwidth Limit: 7 KBps
*Slot allocation: 2 KBps

When [[aMule]] sets the slots to some clients to upload to them, after giving out three slots, it will notice that there are no more 2KBps left, since the limit is 7 KBps, but there is still 1 KBps left in the bandwidth before reaching the Bandwidth Limit. So, it will allow another slot to upload to a client and, instead of giving that last slot a 1 KBps bandwidth connection (and leave the rest with a 2 KBps bandwidth connection), it will give all four slots a 1.8 KBps bandwidth connection.

== Why can't I set aMule's download limit to more than X? ==
To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:
*From 0KBps to 3KBps:
*DownloadLimit can't be more than UploadLimit*3
*From 4KBps to 9KBps:
*DownloadLimit can't be more than UploadLimit*4
*UploadLimit values over 9KBps:
*There's no DownloadLimit limitation.

Be careful when setting 0KBps as Upload Limit. It might not mean what you think it is. Read [[AMule_problems#I_set_Upload_Limit_to_0KBps,_but_aMule_is_still_transferring._What_did_I_do_wrong?|I set Upload Limit to 0KBps, but aMule is still transferring. What did I do wrong?]] to make sure you understand it's meaning.

== I set Upload Limit to 0KBps, but aMule is still transferring. What did I do wrong? ==
Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opposite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to its end.

Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==
This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established).

On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editing the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist):

''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==
In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would give the progress bar a flat look while setting it to the most left will give it a dark look.

== All my downloads suddenly paused and I can't resume them. What's going on? ==
Check if there's any free space in the filesystem where the Temp directory is placed. If there is any at all, check if there's more free space than the minimum free space set at Preferences -> Files -> "Min disk space".

The minimum free space required for [[aMule]] is 9.28MB, since that's what [[aMule]] needs to be able to download a [[FAQ_eD2k-Kademlia#What_is_a_chunk?|part]] of a file.

== Why can't I preview a file? ==
First of all you must know that [[aMule]] only allows to preview video files.

To be able to preview a file [[aMule]] requires two things:
*The file must have a known video extension in its filename
*You must have downloaded the first 256KBs of the file

Anyway, sometimes it happens that the file is previewable though [[aMule]] doesn't allow you. In that case, go to the Temp directory and preview them manually, if you can and wish.

== Why isn't [[aMule]]'s Preview working at all with MPlayer? ==
Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.:

''xterm -T "aMule preview" -iconic -e mplayer -idx''

Sometime, mplayer will hang with incomplete avi files. The best way I know to avoid it is with ''[http://wiki.multimedia.cx/index.php?title=MPlayer_FAQ -demuxer lavf]'' i.e.:

''xterm -T "aMule preview" -iconic -e mplayer -demuxer lavf "%PARTFILE"''

== After exitting MPlayer on Preview, my aMule keeps locked? ==
Preview used to lock aMule on purpose until aMule reached version 2.0.0-rc4. As a result of this, people using MPlayer suffered from a bug on MPlayer which remains the main process in background when closing the main MPlayer window. The way to walk around this MPlayer bug on aMule versions previous to 2.0.0-rc4 is to exit MPlayer by pressing the '''Q''' key. Any way, it'd be better if you could possibly upgrade aMule to the latest versions.

== Why is ''Transfered'' a smaller number than ''Completed''? ==
It's a common mistake to think it should be bigger or, at least, equal.

Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Transfers_window?|What is the difference between Transfered and Completed in the Transfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==
Yes it is. When aMule completes a download it checks it has not been corrupted. although this is already checked while downloading (by checking the chunk's hash values), once the file is completely downloaded aMule hashes all the chunks to check that the chunks which were previously downloaded weren't somehow corrupted by the user or an external application while the rest of the file was being downloaded.

== Is there any way to recursively select a whole directory and its contents? ==
Yes, there is. And it's simple:
*On [[aMule]] 2.0.0-rc4 or later, right-click on the icon of the directory you want to recursively select.
*On [[aMule]] 1.x and up to 2.0.0-rc3 (included), while clicking on the directory, hold the CTRL key.

And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==
If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]].

[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

== What should I be aware of when using NFS mounts with [[aMule]]? ==
When using NFS mounts with [[aMule]], make sure you unmount those NFS mounts (the ones from the computer being shut down) from the computer running [[aMule]] because, otherwise, [[aMule]] will simply hang until those mounts are back up again. How to notice this? If you leave [[aMule]] running at night, and on the next day you go to the stats and see straight lines for [[Download]]/[[Upload]]/[[Connect]]ions stats (non-zero) and after mounting those NFS mounts, those straight lines drop to zero resuming normal behaviour, that is a sign. Plus, after unmouting the NFS mounts from any computer being shut down, '''reload''' [[aMule]]'s shared files.

''I noticed all this from my frustrating experience of countless days with no downloads at night ;) ... --[[User:PedroAlgarvio|PedroAlgarvio]] 00:25, 15 Jun 2005 (CEST)''

== Downloaded files don't get the permissions I set in Preferences. Why? ==
aMule must follow the permissions it is allowed to set by ''umask''. ''umask'' sets the permissions which applications should '''not''' be allowed to assign files.

Therefore, if you set, for example, file permissions to ''664'' in aMule's Preferences, and umask's value (check it by running ''umask'') is ''022'', aMule will create files with permissions ''644'' (that is, ''664'' - ''022'' = ''644'').

== aMule fails to create files/shows file descriptor errors. What's going on? ==
This should never happen. If it happens chances are you have the resources limits very low, so aMule is denied to create/open new files. Run ''ulimit -a'' to check your resources limits. Read ''man ulimit'' to learn how to set the limits as you want them, and remember that this has to be set on every system restart (probably your distribution provides a configuration file which sets this automatically).

HowTo Compile In Gentoo

2012-05-09T15:58:09Z

Libre: /* The SVN ebuild - updated the ChangeLog */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ 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 [http://forum.amule.org/index.php?topic=17143.0 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 [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

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

HowTo Compile In Gentoo

2012-05-04T17:32:41Z

Libre: /* The SVN ebuild */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ 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
For more details, see the [http://forum.amule.org/index.php?topic=17143.0 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 [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

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

HowTo Compile In Gentoo

2011-11-13T11:00:20Z

Libre: /* The SVN ebuild - reversed DEB_HOST change*/

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ 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
For more details, see the [http://forum.amule.org/index.php?topic=17143.0 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_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 [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

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

User:Libre

2011-10-21T18:34:08Z

Libre: /* More about me */

Hi all,

== Me and linux ==

I have a technical background in electronic, all the electronic from the vacuum tubes to DSP processors. I prefer the analog electronic and I buy my first PC, a x86, when I see what could be archived with an analog electronic simulation software.

I learned English with books on electronics, so, it is not terrific -:)

I am an old linux user, my first working linux installation was a real pain, one week of work to get it running on my x386 box. A few weeks later, I try on my Amiga 2000, and surprise, in one hour the same work was done. But the 1.3 Amiga OS was so better, than i just installed it back... Now, the heart of my box is a phenom, and it just work like hell with gentoo-linux. This is the fastest and more stable box I never had. The stability of this AMD box is truly amazing, and its speed is amazing too.

For the distributions, Suse, Suse again, Suse always. But I get sick of a few things like its inability to deal reliably on the long run with multiple repositories. I shifted to gentoo. I learned a lot more on linux but eventually not enough, and I get back to Suse after an unrepairable system crash. Same problem than before with it, so I shifted to debian. Debian is not better with its management of multiple repositories, so I shifted back to gentoo. This time, I took my time to experiment with the most critical part of the gentoo install: the cflags.

My conclusion is that, if you use sane cflags, a gentoo system is more stable than even debian. But with insane cflags, it is possible to crash it to death in a few months, days, or even hours, and the only way to get it back will be trough, like with window$, a format and a full reinstall.

What are sane cflags: the ones used in the gentoo handbook.
What are insane cflags: any other combination.

Conclusion bis: if you are not 100% sure, use the same cflags than in the handbook.

The problem posed by the cflags is multiple. They are optimization flags used by gcc when compiling a program. On one hand, you can get a speed boost with them. On the other hand, more optimizations can introduce very strange bugs that can be very difficult to trace: as example, a software can compile just fine, but you can get troubles during its execution, and that even if it doesn't crash.

It is 2 solutions to that problem:
1) Use sane cflags as explained before. (easy, read and paste -:)
2) Do flags optimization for each single program in the box with a profiler like valgrind.

The problem with 2) is than I know nobody that have the time to do that with each and every single installed package, and to redone this work at each upgrade.

And it is more. Flag optimization can give you a speed boost. But this boost will be very marginal with most software, and for the other, the software developers of the program, or the package maintainers of the distribution, will do the profiling for you.

It is much more, but I skip it... In short, the same unsafe cflag can behave differently with different gcc versions and different source codes... ... ... In consequence: don't trust the optimization made by software developers, they just don't have the same system than yours. -:) It is also for that than it is best to set sane cflags into /etc/make.conf

And last, it is a much better way to get a speed boost: compile your kernel with a processor type that is corresponding to the processor in your box. On gentoo, you already know that. With the other distributions, you have to install the kernel sources that correspond to your kernel in use, copy the .config file of this kernel into the kernel sources, run "make oldconfig" and "make menuconfig". In this menu, go to "Processor tape and features" -> "Processor family" and select the most appropriated family. Exit the menu, compile and install the kernel and its modules. For more information of the process of kernel compilation and installation, take a look at the forum of your distribution. It can be important distribution specific tricks that will make this easier and safer (in case of system upgrade and so on).

== More about me ==
Hopefully, it is a life outside the computadores, the real life.

For now, I have one foot in Switzerland and one in Cuba.

Switzerland is an amazing country, but behind its goodies, it is very boring, peoples here are like in all the rich countries I know, obsessed by the money and so selfish. But it is here than I get at work 5 days a week. And for that, it is yet a good country.

Cuba is another amazing country. It is not only a tropical island, but also a socialist country. And the people here is truly kind and free. OK, they are not free to travel because they are too poor, but they are free to go at school at any age, they have free housing, free healthcare, phone and electricity prices are very very low, and they have many other advantages that are just unthinkable in a capitalist country. They can watch the TV canals from both Cuba and the US, same thing with the radio canals, and if they choose the Cuban's ones most of the time, it is because they are better. It is even 2 educational TV canals with subjects of all kinds, from the ground level up to the university level.

One time, I was walking into the country side, and I come into a very little village. Peoples was very surprised to see a tourist here, but very kind. The houses was simple, but in very good condition, it was electricity and a clean water system in all the houses, it was a common house with a TV and other amenities (as well than TV sets in the other houses), it was a little healthcare center done by a family doctor, and even a house with a popular university. I have never seen a so little village with so many facilities into a so rich country such as Switzerland. I was not in Switzerland but in Cuba.

I discussed with a lot of peoples, from a Police Commissioner or the director of one the biggest society in Cuba (the one that rent cars to the tourists), to ordinary peoples of all kinds, even with some rogue guys. I noticed 2 things unthinkable in Switzerland: all have a good education, are very open-minded and very critical of the Cuban system, all know their system better than most of us know the capitalism, and all of them don't want another system than the Cuban one. They are all very proud of what they are accomplishing in Cuba, and they all never forget that the first conquest of the Cuban revolution is the real independence of the Island.

Also, their criticism of their system is always constructive. The don't say "It's all bullshit" or non-understandable political talks. Instead, they said things like "This is not going well because this and that. We are aware of the problem, we want to correct it, and we are discussing the possible solutions. One is that, the other is this, and a few other peoples think like this. We must deepen the discussion in order to find the better solution for all of us." Sometime they add "because of the US blockade, we don't have the means to do it now, this is a wishful thinking".

Also, the nature of the Island is one of the most beautiful I have never seen. If you like to walk, prefer the winter, it is less hot.

In short, I am in love with Cuba, its inhabitants, their way of life, their choices, and also and of course with my future Cuban wife. She will be my third wife, and I hope the good and last one.

User:Libre

2011-10-21T18:24:51Z

Libre: /* Me and linux */

Hi all,

== Me and linux ==

I have a technical background in electronic, all the electronic from the vacuum tubes to DSP processors. I prefer the analog electronic and I buy my first PC, a x86, when I see what could be archived with an analog electronic simulation software.

I learned English with books on electronics, so, it is not terrific -:)

I am an old linux user, my first working linux installation was a real pain, one week of work to get it running on my x386 box. A few weeks later, I try on my Amiga 2000, and surprise, in one hour the same work was done. But the 1.3 Amiga OS was so better, than i just installed it back... Now, the heart of my box is a phenom, and it just work like hell with gentoo-linux. This is the fastest and more stable box I never had. The stability of this AMD box is truly amazing, and its speed is amazing too.

For the distributions, Suse, Suse again, Suse always. But I get sick of a few things like its inability to deal reliably on the long run with multiple repositories. I shifted to gentoo. I learned a lot more on linux but eventually not enough, and I get back to Suse after an unrepairable system crash. Same problem than before with it, so I shifted to debian. Debian is not better with its management of multiple repositories, so I shifted back to gentoo. This time, I took my time to experiment with the most critical part of the gentoo install: the cflags.

My conclusion is that, if you use sane cflags, a gentoo system is more stable than even debian. But with insane cflags, it is possible to crash it to death in a few months, days, or even hours, and the only way to get it back will be trough, like with window$, a format and a full reinstall.

What are sane cflags: the ones used in the gentoo handbook.
What are insane cflags: any other combination.

Conclusion bis: if you are not 100% sure, use the same cflags than in the handbook.

The problem posed by the cflags is multiple. They are optimization flags used by gcc when compiling a program. On one hand, you can get a speed boost with them. On the other hand, more optimizations can introduce very strange bugs that can be very difficult to trace: as example, a software can compile just fine, but you can get troubles during its execution, and that even if it doesn't crash.

It is 2 solutions to that problem:
1) Use sane cflags as explained before. (easy, read and paste -:)
2) Do flags optimization for each single program in the box with a profiler like valgrind.

The problem with 2) is than I know nobody that have the time to do that with each and every single installed package, and to redone this work at each upgrade.

And it is more. Flag optimization can give you a speed boost. But this boost will be very marginal with most software, and for the other, the software developers of the program, or the package maintainers of the distribution, will do the profiling for you.

It is much more, but I skip it... In short, the same unsafe cflag can behave differently with different gcc versions and different source codes... ... ... In consequence: don't trust the optimization made by software developers, they just don't have the same system than yours. -:) It is also for that than it is best to set sane cflags into /etc/make.conf

And last, it is a much better way to get a speed boost: compile your kernel with a processor type that is corresponding to the processor in your box. On gentoo, you already know that. With the other distributions, you have to install the kernel sources that correspond to your kernel in use, copy the .config file of this kernel into the kernel sources, run "make oldconfig" and "make menuconfig". In this menu, go to "Processor tape and features" -> "Processor family" and select the most appropriated family. Exit the menu, compile and install the kernel and its modules. For more information of the process of kernel compilation and installation, take a look at the forum of your distribution. It can be important distribution specific tricks that will make this easier and safer (in case of system upgrade and so on).

== More about me ==
Hopefully, it is a life outside the computadores, the real life.

For now, I have one foot in Switzerland and one in Cuba.

Switzerland is an amazing country, but behind its goodies, it is very boring, peoples here are like in all the rich countries I know, obsessed by the money and so selfish. But it is here than I get at work 5 days a week. And for that, it is yet a good country.

Cuba is another amazing country. It is not only a tropical island, but also a socialist country. And the people here is truly kind and free. OK, they are not free to travel because they are too poor, but they are free to go at school at any age, they have free housing, free healthcare, phone and electricity prices are very very low, and they have many other advantages that are just unthinkable in a capitalist country. They can watch the TV canals from both Cuba and the US, same thing with the radio canals, and if they choose the Cuban's ones most of the time, it is because they are better. It is even 2 educational TV canals with subjects of all kinds, from the ground level up to the university level.

One time, I was walking into the country side, and I come into a very little village. Peoples was very surprised to see a tourist here, but very kind. The houses was simple, but in very good condition, it was electricity and a clean water system in all the houses, it was a common house with a TV and other amenities (as well than TV sets in the other houses), it was a little healthcare center done by a family doctor, and even a house with a popular university. I have never seen a so little village with so many facilities into a so rich country such as Switzerland. I was not in Switzerland but in Cuba.

I discussed with a lot of peoples, from a Police Commissioner or the director of one the biggest society in Cuba (the one that rent cars to the tourists), to ordinary peoples of all kinds, even with some rogue guys. I noticed 2 things unthinkable in Switzerland: all have a good education, are very open-minded and very critical of the Cuban system, all know their system better than most of us know the capitalism, and all of them don't want another system than the Cuban one. They are all very proud of what they are accomplishing in Cuba, and they all never forget that the first conquest of the Cuban revolution is the real independence of the Island.

Also, their criticism of their system is always constructive. The don't say "It's all bullshit" or non-understandable political talks. Instead, they said things like "This is not going well because this and that. We are aware of the problem, we want to correct it, and we are discussing the possible solutions. One is that, the other is this, and a few other peoples think like this. We must deepen the discussion in order to find the better solution." Sometime they add "because of the US blockade, we don't have the means to do it know and this is a wishful thinking".

Also, the nature of the Island is one of the most beautiful I have never seen. If you like to walk, prefer the winter, it is less hot.

In short, I am in love with Cuba, its inhabitants, their way of life, their choices, and also and of course with my future Cuban wife. She will be my third wife, and I hope the good and last one.

User:Libre

2011-10-21T18:18:21Z

Libre:

Hi all,

== Me and linux ==

I have a technical background in electronic, all the electronic from the vacuum tubes to DSP processors. I prefer the analog electronic and I buy my first PC, a x86, when I see what could be archived with an analog electronic simulation software.

I learned English with books on electronics, so, it is not terrific -:)

I am an old linux user, my first working linux installation was a real pain, one week of work to get it running on my x386 box. A few weeks later, I try on my Amiga 2000, and surprise, in one hour the same work was done. But the 1.3 Amiga OS was so better, than i just installed it back... Now, the heart of my box is a phenom, and it just work like hell with gentoo-linux. This is the fastest and more stable box I never had. The stability of this AMD box is truly amazing, and its speed is amazing too.

For the distributions, Suse, Suse again, Suse always. But I get sick of a few things like its inability to deal reliably on the long run with multiple repositories. I shifted to gentoo. I learned a lot more on linux but eventually not enough, and I get back to Suse after an unrepairable system crash. Same problem than before with it, so I shifted to debian. Debian is not better with its management of multiple repositories, so I shifted back to gentoo. This time, I took my time to experiment with the most critical part of the gentoo install: the cflags.

My conclusion is that, if you use sane cflags, a gentoo system is more stable than even debian. But with insane cflags, it is possible to crash it to death in a few months, days, or even hours, and the only way to get it back will be trough, like with window$, a format and a full reinstall.

What are sane cflags: the ones used in the gentoo handbook.
What are insane cflags: any other combination.

Conclusion bis: if you are not 100% sure, use the same cflags than in the handbook.

The problem posed by the cflags is multiple. They are optimization flags used by gcc when compiling a program. On one hand, you can get a speed boost with them. On the other hand, more optimizations can introduce very strange bugs that can be very difficult to trace: as example, a software can compile just fine, but you can get troubles during its execution, and that even if it doesn't crash.

It is 2 solutions to that problem:
1) Use sane cflags as explained before. (easy, read and paste -:)
2) Do flags optimization for each single program in the box with a profiler like valgrind.

The problem with 2) is than I know nobody that have the time to do that with each and every single installed package, and to redone this work at each upgrade.

And it is more. Flag optimization can give you a speed boost. But this boost will be very marginal with most software, and for the other, the software developers of the program, or the package maintainers of the distribution, will do the profiling for you.

It is much more, but I skip it... In short, the same unsafe cflag can behave differently with different gcc versions and different source codes... ... ... -:)

And last, it is a much better way to get a speed boost: compile your kernel with a processor type that is corresponding to the processor in your box. On gentoo, you already know that. With the other distributions, you have to install the kernel sources that correspond to your kernel in use, copy the .config file of this kernel into the kernel sources, run "make oldconfig" and "make menuconfig". In this menu, go to "Processor tape and features" -> "Processor family" and select the most appropriated family. Exit the menu, compile and install the kernel and its modules. For more information of the process of kernel compilation and installation, take a look at the forum of your distribution. It can be important distribution specific tricks that will make this easier and safer (in case of system upgrade and so on).

== More about me ==
Hopefully, it is a life outside the computadores, the real life.

For now, I have one foot in Switzerland and one in Cuba.

Switzerland is an amazing country, but behind its goodies, it is very boring, peoples here are like in all the rich countries I know, obsessed by the money and so selfish. But it is here than I get at work 5 days a week. And for that, it is yet a good country.

Cuba is another amazing country. It is not only a tropical island, but also a socialist country. And the people here is truly kind and free. OK, they are not free to travel because they are too poor, but they are free to go at school at any age, they have free housing, free healthcare, phone and electricity prices are very very low, and they have many other advantages that are just unthinkable in a capitalist country. They can watch the TV canals from both Cuba and the US, same thing with the radio canals, and if they choose the Cuban's ones most of the time, it is because they are better. It is even 2 educational TV canals with subjects of all kinds, from the ground level up to the university level.

One time, I was walking into the country side, and I come into a very little village. Peoples was very surprised to see a tourist here, but very kind. The houses was simple, but in very good condition, it was electricity and a clean water system in all the houses, it was a common house with a TV and other amenities (as well than TV sets in the other houses), it was a little healthcare center done by a family doctor, and even a house with a popular university. I have never seen a so little village with so many facilities into a so rich country such as Switzerland. I was not in Switzerland but in Cuba.

I discussed with a lot of peoples, from a Police Commissioner or the director of one the biggest society in Cuba (the one that rent cars to the tourists), to ordinary peoples of all kinds, even with some rogue guys. I noticed 2 things unthinkable in Switzerland: all have a good education, are very open-minded and very critical of the Cuban system, all know their system better than most of us know the capitalism, and all of them don't want another system than the Cuban one. They are all very proud of what they are accomplishing in Cuba, and they all never forget that the first conquest of the Cuban revolution is the real independence of the Island.

Also, their criticism of their system is always constructive. The don't say "It's all bullshit" or non-understandable political talks. Instead, they said things like "This is not going well because this and that. We are aware of the problem, we want to correct it, and we are discussing the possible solutions. One is that, the other is this, and a few other peoples think like this. We must deepen the discussion in order to find the better solution." Sometime they add "because of the US blockade, we don't have the means to do it know and this is a wishful thinking".

Also, the nature of the Island is one of the most beautiful I have never seen. If you like to walk, prefer the winter, it is less hot.

In short, I am in love with Cuba, its inhabitants, their way of life, their choices, and also and of course with my future Cuban wife. She will be my third wife, and I hope the good and last one.

User:Libre

2011-10-21T18:15:14Z

Libre: /* Me and linux */

Hi all,

== Me and linux ==

I have a technical background in electronic, all the electronic from the vacuum tubes to DSP processors. I prefer the analog electronic and I buy my first PC, a x86, when I see what could be archived with an analog electronic simulation software.

I learned English with books on electronics, so, it is not terrific -:)

I am an old linux user, my first working linux installation was a real pain, one week of work to get it running on my x386 box. A few weeks later, I try on my Amiga 2000, and surprise, in one hour the same work was done. But the 1.3 Amiga OS was so better, than i just installed it back... Now, the heart of my box is a phenom, and it just work like hell with gentoo-linux. This is the fastest and more stable box I never had. The stability of this AMD box is truly amazing, and its speed is amazing too.

For the distributions, Suse, Suse again, Suse always. But I get sick of a few things like its inability to deal reliably on the long run with multiple repositories. I shifted to gentoo. I learned a lot more on linux but eventually not enough, and I get back to Suse after a unrepairable system crash. Same problem than before with it, so I shifted to debian. Debian is not better with its management of multiple repositories, so I shifted back to gentoo. This time, I took my time to experiment with the most critical part of the gentoo install: the cflags.

My conclusion is that, if you use sane cflags, a gentoo system is more stable than even debian. But with insane cflags, it is possible to crash it to death in a few months, days, or even hours, and the only way to get it back will be trough, like with window$, a format and a full reinstall.

What are sane cflags: the ones used in the gentoo handbook.
What are insane cflags: any other combination.

Conclusion bis: if you are not 100% sure, use the same cflags than in the handbook.

The problem posed by the cflags is multiple. They are optimization flags used by gcc when compiling a program. On one hand, you can get a speed boost with them. On the other hand, more optimizations can introduce very strange bugs that can be very difficult to trace: as example, a software can compile just fine, but you can get troubles during its execution, and that even if it doesn't crash.

It is 2 solutions to that problem:
1) Use sane cflags as explained before. (easy, read and paste -:)
2) Do flags optimization for each single program in the box with a profiler like valgrind.

The problem with 2) is than I know nobody that have the time to do that with each and every single installed package, and to redone this work at each upgrade.

And it is more. Flag optimization can give you a speed boost. But this boost will be very marginal with most software, and for the other, the software developers of the program, or the package maintainers of the distribution, will do the profiling for you.

It is much more, but I skip it... In short, the same unsafe cflag can behave differently with different gcc versions and different source codes... ... ... -:)

And last, it is a much better way to get a speed boost: compile your kernel with a processor type that is corresponding to the processor in your box. On gentoo, you already know that. With the other distributions, you have to install the kernel sources that correspond to your kernel in use, copy the .config file of this kernel into the kernel sources, run "make oldconfig" and "make menuconfig". In this menu, go to "Processor tape and features" -> "Processor family" and select the most appropriated family. Exit the menu, compile and install the kernel and its modules. For more information of the process of kernel compilation and installation, take a look at the forum of your distribution. It can be important distribution specific tricks that will make this easier and safer (in case of system upgrade and so on).

== More about me ==
Hopefully, it is a life outside the computadores, the real life.

For now, I have one foot in Switzerland and one in Cuba.

Switzerland is an amazing country, but behind its goodies, it is very boring, peoples here are like in all the rich countries I know, obsessed by the money and so selfish. But it is here than I get at work 5 days a week. And for that, it is yet a good country.

Cuba is another amazing country. It is not only a tropical island, but also a socialist country. And the people here is truly kind and free. OK, they are not free to travel because they are too poor, but they are free to go at school at any age, they have free housing, free healthcare, phone and electricity prices are very very low, and they have many other advantages that are just unthinkable in a capitalist country. They can watch the TV canals from both Cuba and the US, same thing with the radio canals, and if they choose the Cuban's ones most of the time, it is because they are better. It is even 2 educational TV canals with subjects of all kinds, from the ground level up to the university level.

One time, I was walking into the country side, and I come into a very little village. Peoples was very surprised to see a tourist here, but very kind. The houses was simple, but in very good condition, it was electricity and a clean water system in all the houses, it was a common house with a TV and other amenities (as well than TV sets in the other houses), it was a little healthcare center done by a family doctor, and even a house with a popular university. I have never seen a so little village with so many facilities into a so rich country such as Switzerland. I was not in Switzerland but in Cuba.

I discussed with a lot of peoples, from a Police Commissioner or the director of one the biggest society in Cuba (the one that rent cars to the tourists), to ordinary peoples of all kinds, even with some rogue guys. I noticed 2 things unthinkable in Switzerland: all have a good education, are very open-minded and very critical of the Cuban system, all know their system better than most of us know the capitalism, and all of them don't want another system than the Cuban one. They are all very proud of what they are accomplishing in Cuba, and they all never forget that the first conquest of the Cuban revolution is the real independence of the Island.

Also, their criticism of their system is always constructive. The don't say "It's all bullshit" or non-understandable political talks. Instead, they said things like "This is not going well because this and that. We are aware of the problem, we want to correct it, and we are discussing the possible solutions. One is that, the other is this, and a few other peoples think like this. We must deepen the discussion in order to find the better solution." Sometime they add "because of the US blockade, we don't have the means to do it know and this is a wishful thinking".

Also, the nature of the Island is one of the most beautiful I have never seen. If you like to walk, prefer the winter, it is less hot.

In short, I am in love with Cuba, its inhabitants, their way of life, their choices, and also and of course with my future Cuban wife. She will be my third wife, and I hope the good and last one.

User:Libre

2011-10-21T18:13:44Z

Libre:

Hi all,

== Me and linux ==

I have a technical background in electronic, all the electronic from the vacuum tubes to DSP processors. I prefer the analog electronic and I buy my first PC, a x86, when I see what could be archived with an analog electronic simulation software.

I am an old linux user, my first working linux installation was a real pain, one week of work to get it running on my x386 box. A few weeks later, I try on my Amiga 2000, and surprise, in one hour the same work was done. But the 1.3 Amiga OS was so better, than i just installed it back... Now, the heart of my box is a phenom, and it just work like hell with gentoo-linux. This is the fastest and more stable box I never had. The stability of this AMD box is truly amazing, and its speed is amazing too.

For the distributions, Suse, Suse again, Suse always. But I get sick of a few things like its inability to deal reliably on the long run with multiple repositories. I shifted to gentoo. I learned a lot more on linux but eventually not enough, and I get back to Suse after a unrepairable system crash. Same problem than before with it, so I shifted to debian. Debian is not better with its management of multiple repositories, so I shifted back to gentoo. This time, I took my time to experiment with the most critical part of the gentoo install: the cflags.

My conclusion is that, if you use sane cflags, a gentoo system is more stable than even debian. But with insane cflags, it is possible to crash it to death in a few months, days, or even hours, and the only way to get it back will be trough, like with window$, a format and a full reinstall.

What are sane cflags: the ones used in the gentoo handbook.
What are insane cflags: any other combination.

Conclusion bis: if you are not 100% sure, use the same cflags than in the handbook.

The problem posed by the cflags is multiple. They are optimization flags used by gcc when compiling a program. On one hand, you can get a speed boost with them. On the other hand, more optimizations can introduce very strange bugs that can be very difficult to trace: as example, a software can compile just fine, but you can get troubles during its execution, and that even if it doesn't crash.

It is 2 solutions to that problem:
1) Use sane cflags as explained before. (easy, read and paste -:)
2) Do flags optimization for each single program in the box with a profiler like valgrind.

The problem with 2) is than I know nobody that have the time to do that with each and every single installed package, and to redone this work at each upgrade.

And it is more. Flag optimization can give you a speed boost. But this boost will be very marginal with most software, and for the other, the software developers of the program, or the package maintainers of the distribution, will do the profiling for you.

It is much more, but I skip it... In short, the same unsafe cflag can behave differently with different gcc versions and different source codes... ... ... -:)

And last, it is a much better way to get a speed boost: compile your kernel with a processor type that is corresponding to the processor in your box. On gentoo, you already know that. With the other distributions, you have to install the kernel sources that correspond to your kernel in use, copy the .config file of this kernel into the kernel sources, run "make oldconfig" and "make menuconfig". In this menu, go to "Processor tape and features" -> "Processor family" and select the most appropriated family. Exit the menu, compile and install the kernel and its modules. For more information of the process of kernel compilation and installation, take a look at the forum of your distribution. It can be important distribution specific tricks that will make this easier and safer (in case of system upgrade and so on).

== More about me ==
Hopefully, it is a life outside the computadores, the real life.

For now, I have one foot in Switzerland and one in Cuba.

Switzerland is an amazing country, but behind its goodies, it is very boring, peoples here are like in all the rich countries I know, obsessed by the money and so selfish. But it is here than I get at work 5 days a week. And for that, it is yet a good country.

Cuba is another amazing country. It is not only a tropical island, but also a socialist country. And the people here is truly kind and free. OK, they are not free to travel because they are too poor, but they are free to go at school at any age, they have free housing, free healthcare, phone and electricity prices are very very low, and they have many other advantages that are just unthinkable in a capitalist country. They can watch the TV canals from both Cuba and the US, same thing with the radio canals, and if they choose the Cuban's ones most of the time, it is because they are better. It is even 2 educational TV canals with subjects of all kinds, from the ground level up to the university level.

One time, I was walking into the country side, and I come into a very little village. Peoples was very surprised to see a tourist here, but very kind. The houses was simple, but in very good condition, it was electricity and a clean water system in all the houses, it was a common house with a TV and other amenities (as well than TV sets in the other houses), it was a little healthcare center done by a family doctor, and even a house with a popular university. I have never seen a so little village with so many facilities into a so rich country such as Switzerland. I was not in Switzerland but in Cuba.

I discussed with a lot of peoples, from a Police Commissioner or the director of one the biggest society in Cuba (the one that rent cars to the tourists), to ordinary peoples of all kinds, even with some rogue guys. I noticed 2 things unthinkable in Switzerland: all have a good education, are very open-minded and very critical of the Cuban system, all know their system better than most of us know the capitalism, and all of them don't want another system than the Cuban one. They are all very proud of what they are accomplishing in Cuba, and they all never forget that the first conquest of the Cuban revolution is the real independence of the Island.

Also, their criticism of their system is always constructive. The don't say "It's all bullshit" or non-understandable political talks. Instead, they said things like "This is not going well because this and that. We are aware of the problem, we want to correct it, and we are discussing the possible solutions. One is that, the other is this, and a few other peoples think like this. We must deepen the discussion in order to find the better solution." Sometime they add "because of the US blockade, we don't have the means to do it know and this is a wishful thinking".

Also, the nature of the Island is one of the most beautiful I have never seen. If you like to walk, prefer the winter, it is less hot.

In short, I am in love with Cuba, its inhabitants, their way of life, their choices, and also and of course with my future Cuban wife. She will be my third wife, and I hope the good and last one.

User:Libre

2011-10-21T17:58:37Z

Libre: Created page with 'Hi all, I am an old linux user, my first working linux installation was a real pain, one week of work to get it running on my 386 box. A few weeks later, I try on my Amiga 2000,…'

Hi all,

I am an old linux user, my first working linux installation was a real pain, one week of work to get it running on my 386 box. A few weeks later, I try on my Amiga 2000, and surprise, in one hour the same work was done. But the 1.3 Amiga OS was so better, than i just installed it back... Now, the heart of my box is a phenom and it just work like hell with gentoo-linux. This is the fastest and more stable boy I ever had.

For the distribution, Suse, Suse again, Suse always. But I get sick of a few things like the inability of such distributions to deal reliably on the long run with multiple repositories. I shifted to gentoo. I learned a lot more on linux but eventually not enough, and I get back to Suse. Same problem than before with it, so I shifted to debian. Debian is not better with its management of multiple repositories, so I shifted back to gentoo. This time, I took my time to experiment with the most critical part of the gentoo install: the cflags.

My conclusion is that, if you use sane cflags, a gentoo system is more stable than even debian. But with insane cflags, it is possible to crash it to death in a few months, days, or even hours, and the only way to get it back will be trough, like with window$, a format and a full reinstall.

What are sane cflags: the ones used in the gentoo handbook.
What are insane cflags: any other combination.

Conclusion bis: if you are not 100% sure, use the same cflags than in the handbook.

The problem posed by the cflags is multiple. They are optimization flags used by gcc when compiling a program. On one hand, you can get a speed boost with them. On the other hand, more optimizations can introduce very strange bugs that can be very difficult to trace: as example, a software can compile just fine, but you can get troubles during its execution, and that even if it doesn't crash.

It is 2 solutions to that problem:
1) Use sane cflags as explained before.
2) Do flags optimization for each single program in the box with a profiler like valgrind.

The problem with 2 is than I know nobody that have the time to do that with each and every single installed package, and to redone this work at each upgrade.

And it is more. Flag optimization can give you a speed boost. But this boost will be very marginal with most software, and for the other, the software developers of the program, or the package maintainers of the distribution, will do the profiling for you.

It is much more, but I skip it... In short, the same flag can behave differently with different gcc versions... ... ... -:)

And last, it is a much better way to get a speed boost: compile your kernel with a processor type that is corresponding to the processor in your box. On gentoo, you already know that. With the other distributions, you have to install the kernel sources that correspond to your kernel in use, copy the .config file of this kernel into the kernel sources, run "make oldconfig" and "make menuconfig". In this menu, go to "Processor tape and features" -> "Processor family" and select the most appropriated family. Exit the menu, compile and install the kernel and its modules. For more information of the process of kernel compilation and installation, take a look at the forum of your distribution. It can be important distribution specific tricks that will make this easier and safer in case of system upgrade and so on.

== More about me ==
Hopefully, it is a life outside the computadores, the real life.

For now, I have one foot in Switzerland and one in Cuba.

Switzerland is an amazing country, but behind its goodies, it is very boring, peoples here are like in all the rich countries I know, obsessed by the money and so selfish. But it is here than I get at work 5 days a week. And for that, it is yet a good country.

Cuba is another amazing country. It is not only a tropical island, but also a socialist country. And the people here is truly kind and free. OK, they are not free to travel because they are too poor, but they are free to go at school at any age, they have free housing, free healthcare, phone and electricity prices are very very low, and they have many other advantages that are just unthinkable in a capitalist country. They can watch the TV canals from both Cuba and the US, same thing with the radio canals, and if they choose the Cuban's ones most of the time, it is because they are better. It is even 2 educational TV canals with subjects of all kinds, from the ground level up to the university level.

One time, I was walking into the country side, and I come into a very little village. Peoples was very surprised to see a tourist here, but very kind. The houses was simple, but in very good condition, it was electricity and a clean water system in all the houses, it was a common house with a TV and other amenities (as well than TV sets in the other houses), it was a little healthcare center done by a family doctor, and even a house with a popular university. I have never seen a so little village with so many facilities into a so rich country such as Switzerland. I was not in Switzerland but in Cuba.

I discussed with a lot of peoples, from a Police Commissioner or the director of one the biggest society in Cuba (the one that rent cars to the tourists), to ordinary peoples of all kinds, even with some rogue guys. I noticed 2 things unthinkable in Switzerland: all have a good education, are very open-minded and very critical of the Cuban system, all know their system better than most of us know the capitalism, and all of them don't want another system than the Cuban one. They are all very proud of what they are accomplishing in Cuba, and they all never forget that the first conquest of the Cuban revolution is the real independence of the Island.

Also, their criticism of their system is always constructive. The don't say "It's all bullshit" or non-understandable political talks. Instead, they said things like "This is not going well because this and that. We are aware of the problem, we want to correct it, and we are discussing the possible solutions. One is that, the other is this, and a few other peoples think like this. We must deepen the discussion in order to find the better solution." Sometime they add "because of the US blockade, we don't have the means to do it know and this is a wishful thinking".

Also, the nature of the Island is one of the most beautiful I have never seen. If you like to walk, prefer the winter, it is less hot.

In short, I am in love with Cuba, its inhabitants, their way of life, their choices, and also and of course with my future Cuban wife. She will be my third wife, and I hope the good and last one.

HowTo Compile In Gentoo

2011-10-21T16:00:19Z

Libre: /* amule SVN */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ 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
For more details, see the [http://forum.amule.org/index.php?topic=17143.0 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

DEB_HOST_ARCH="no" 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_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 [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

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

HowTo Compile In Gentoo

2011-10-14T19:46:12Z

Libre: /* amule SVN + mmap USE flag; DEB_HOST_ARCH="no" */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.

# 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

DEB_HOST_ARCH="no" 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_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 [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

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

HowTo Compile In Gentoo

2011-04-16T16:23:22Z

Libre: /* amule SVN */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.

# 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 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 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_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 [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

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

HowTo Compile In Gentoo

2011-04-12T18:00:37Z

Libre: /* amule SVN */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.

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

EAPI="2"

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 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 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_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 [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

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

HowTo Compile In Gentoo

2011-04-12T17:22:38Z

Libre: /* amule SVN */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

# bleeding-edge development
MY_P="aMule-SVN-r${PV}"
# 2_2_X branch, currently unavailable
# MY_P="aMule-SVN-r${PV}-RELEASE-2_2_X"

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 geoip gtk nls remote 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 )
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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

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

HowTo Compile In Gentoo

2011-04-12T17:17:38Z

Libre: /* amule SVN */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

# bleeding-edge development
MY_P="aMule-SVN-r${PV}"
# 2_2_X branch, currently unavailable
# MY_P="aMule-SVN-r${PV}-RELEASE-2_2_X"

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 geoip gtk nls remote 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 )
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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

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

Ed2k links handling

2011-02-05T12:59:48Z

Libre: /* Add multiple downloads to aMule at once */

<center>
'''English''' |
[[Ed2k_links_handling-de|Deutsch]] |
[[Ed2k_links_handling-nl|Nederlands]] |
[[Ed2k_links_handling-ko_KR|Korean]] |
[[Ed2k_links_handling-es|Español]]
</center>

The way to make [[aMule]] handle your [[ed2k link|ed2k links]] on your favorite web browser will depend on which web browser you use and which operating system you have installed. So, here's a list of mini-HowTos for each of the most popular web browsers and operating systems.

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.

= Local handling of ed2k links =
== GNU/Linux ==
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.opensuse.org SuSE] packages install it in ''/usr/local/bin/ed2k''.

If you have installed Debian or Ubuntu '''you must install''' "'''amule-utils'''" (and "'''amule-ed2k'''" only for Debian) to get this way working.

To know where amule and ed2k are located, just do ''which amule'' and ''which ed2k'' in console!

=== [http://www.mozilla.org/products/firefox Firefox] 2 and 3 (or later)===
Handling ED2k links in Firefox can be configured in two ways: either for an individual user, or for all users of the computer.

==== Configuration for a single user ====
*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'''.

For Ubuntu Lucid users, you should set the Value to just "ed2k" instead of "/usr/bin/ed2k".

For Firefox 3 and higher only, you should also:

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

After that, click over an ed2k link, and Firefox should ask which app you want to use to open the link. Choose /usr/bin/ed2k and it should work.

[[Image:Ed2k-ff3.png]]

==== System-wide configuration ====
*Having root privileges, open the file ''/usr/share/firefox/greprefs/all.js'' (or ''/usr/local/share/firefox/greprefs/all.js'') in a text editor

*Add the following lines at the end of the file:
// ED2K link handling
pref("network.protocol-handler.external.ed2k", true);
pref("network.protocol-handler.app.ed2k", "/path/to/ed2k");
Substitute the "/path/to/ed2k" string with the program's real path.

For Firefox 3 and higher only:
*Add yet another line to the ''all.js''file:
pref("network.protocol-handler.expose.ed2k", false);

After saving changes, restart the browser. After clicking over an ed2k link, Firefox should ask which app you want to use to open the link. Choose /usr/local/bin/ed2k and it should work.

==== Add multiple downloads to aMule at once ====
Setup Firefox as already explained and install the [https://addons.mozilla.org/fr/firefox/addon/firemule/ FireMule] module for Firefox.

=== [http://wiki.debian.org/Iceweasel Iceweasel] ===

==== Configuration for a single user ====
In addition to what was said for Firefox, do the following:
*Right click on the list, select '''New''', then '''Boolean'''; insert ''network.protocol-handler.warn-external.ed2k'' as '''Preference Name''' and ''true'' as '''Value'''.
This is necessary so that Iceweasel asks you which application you want to use to open the link.

=== [http://www.opera.com Opera] ===

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

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

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

[[Image:Ed2k-op.png]]

=== [http://www.konqueror.org Konqueror] ===
To have ed2k links work from [http://www.konqueror.com Konqueror] you have to add a protocol-file to the directory with the other protocol-files. You can find this directory by searching for file names ending with ''.protocol''. To search run ''`find /usr -name "*.protocol"`'' or ''`find /opt -name "*.protocol"`''. If you're not sure about the directory where KDE is installed you can even put ''/'' as search path.

If the search was successful, create a file named like ''ed2k.protocol'' in the mentioned directory:
[Protocol]
exec=/path/to/ed2k "%u"
protocol=ed2k
input=none
output=none
helper=true
listing=false
reading=false
writing=false
makedir=false
deleting=false

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

Execute the following three commands to create the appropriate ''gconf'' keys:

*''gconftool-2 -t string -s /desktop/gnome/url-handlers/ed2k/command "/usr/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/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://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.

== Windows ==
To make Windows aware of the ed2k link protocol we need to add some keys to the registry. Create a file called ed2k.reg and add this code:
REGEDIT4

[HKEY_CLASSES_ROOT\ed2k]
@="URL: ed2k Protocol"
"URL Protocol"=""

[HKEY_CLASSES_ROOT\ed2k\DefaultIcon]
@="C:\\Program Files\\aMule\\amulegui.exe"

[HKEY_CLASSES_ROOT\ed2k\shell]
@="open"

[HKEY_CLASSES_ROOT\ed2k\shell\open]

[HKEY_CLASSES_ROOT\ed2k\shell\open\command]
@="\"C:\\Program Files\\aMule\\ed2k\" \"%1\""
Save the file and run it (double click) to add these keys to the registry.

If your config directory is in d:\amule\config instead of the default place you have to pass it as an option:
[HKEY_CLASSES_ROOT\ed2k\shell\open\command]
@="\"C:\\Program Files\\aMule\\ed2k\" -c d:\\amule\\config \"%1\""

=== [http://www.microsoft.com/windows/ie Internet Explorer] ===
Internet Explorer will recognize ed2k links with just the changes in the registry.

== Mac OS X ==

Adapted from Ken's post in the [http://forum.amule.org/index.php?topic=5679.msg30209#msg30209 forum].

# Run aMule at least once
# Run Safari (even if you normally use Firefox or another browser)
# Browse to a page with an ed2k link that you want to download
# Drag the link to the location field at the top of the window
# The OS will present a dialog asking if you want to allow a program to run to handle the link. Allow it.

Now, the program that helps aMule handle ed2k links is known to the system.

=== Safari ===
If you use Safari, you will have to drag the link to the location field every time. For unclear reasons, Safari will not process ed2k (or other non-Apple protocol) links if you click on them.

=== Firefox ===
If you use Firefox, clicking on an ed2k link will work. The first time, for security purposes, Firefox will present a dialog asking if you want to allow the helper program to run. (Yes, even though the OS already asked you the same question.) After that, it will work just as you would expect.

= Remote handling of ed2k 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. It works by using [[aMuleCMD]] instead of using the [[ed2k command]].

== Linux ==
Instead of using the [[ed2k command]], use the following as the command to use:

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

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

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

== Windows ==
Make sure aMule is installed with the [[aMuleCMD]] option checked.

We need a batch script to handle the ed2k links from the browser, and we need to add some keys to the registry to make the browser recognize the ed2k links. Things are different for 32 and 64 bit versions of Windows so pick the right section below. After you created the files and updated the registry, configure your browser if neccesary.

=== 32 bit ===
Create a file named '''ed2k_remote.bat''' containing the following code:
@echo off
set link=%1
for /f "useback tokens=*" %%a in ('%link%') do set link=%%~a
"c:\Program Files\aMule\amulecmd.exe" /h '''server''' /P '''pass''' /c "add %link%"
Don't forget to replace '''server''' and '''pass''' with your data and save the file in your aMule directory ''C:\Program Files\aMule''.

Create a file named '''ed2k_remote.reg''' containing the following code:
REGEDIT4

[HKEY_CLASSES_ROOT\ed2k]
@="URL: ed2k Protocol"
"URL Protocol"=""

[HKEY_CLASSES_ROOT\ed2k\DefaultIcon]
@="C:\\Program Files\\aMule\\amulegui.exe"

[HKEY_CLASSES_ROOT\ed2k\shell]
@="open"

[HKEY_CLASSES_ROOT\ed2k\shell\open]

[HKEY_CLASSES_ROOT\ed2k\shell\open\command]
@="\"C:\\Program Files\\aMule\\ed2k_remote.bat\" \"%1\""
Save the file and run it (double click) to add these keys to the registry.

=== 64 bit ===
Create a file named '''ed2k_remote.bat''' containing the following code:
@echo off
set link=%1
for /f "useback tokens=*" %%a in ('%link%') do set link=%%~a
"c:\Program Files (x86)\aMule\amulecmd.exe" /h '''server''' /P '''pass''' /c "add %link%"
Don't forget to replace '''server''' and '''pass''' with your data and save the file in your aMule directory ''C:\Program Files (x86)\aMule''.

Create a file named '''ed2k_remote_64.reg''' containing the following code:
REGEDIT4

[HKEY_CLASSES_ROOT\ed2k]
@="URL: ed2k Protocol"
"URL Protocol"=""

[HKEY_CLASSES_ROOT\ed2k\DefaultIcon]
@="C:\\Program Files (x86)\\aMule\\amulegui.exe"

[HKEY_CLASSES_ROOT\ed2k\shell]
@="open"

[HKEY_CLASSES_ROOT\ed2k\shell\open]

[HKEY_CLASSES_ROOT\ed2k\shell\open\command]
@="\"C:\\Program Files (x86)\\aMule\\ed2k_remote.bat\" \"%1\""
Save the file and run it (double click) to add these keys to the registry.

=== Internet Explorer ===
You should be OK with just the changes to the registry and the batch script in your aMule directory.

=== Safari ===
Safari will take over the settings in the registry, like Internet Explorer.

=== Chrome ===
Chrome will take over the settings in the registry. It asks for confirmation, so tick the "Don't ask me again" box.
[[File:Chrome confirm.png]]

=== Firefox ===
The first time you click an ed2k link in Firefox you will get the following dialog:

[[Image:Firefox ed2k link.PNG]]

Tick the Remember box and click OK.

=== Opera ===
Open the preferences window and click the Programs tab

[[Image:Opera preferences programs.PNG]]

Click the Add... button

Make Opera aware of the ed2k link protocol with these settings:

[[Image:Opera_protocols_ed2k.PNG]]

Talk:HowTo Compile In Gentoo

2010-10-21T16:14:46Z

Libre:

PORTAGE_OVERLAY="/usr/local/portage" can't be use anymore must use :

PORTDIR_OVERLAY="/usr/local/portage"

'''Done'''

--------------------------

You forgot to mention that the (allegedly stable) build usually fails. For a while it worked only with the crypto++ library installed; now it doesn't compile at all. Perhaps this is because of the recent gcc 3.4 update, but I don't know for sure.

Done. It is a bug into recent libcrypto++. 2 solutions, see the article.
----

--------------------------

Also, you should add the fact that, you *must not* have "-gtk" in your USE flags... It was a real pain in the ... grass to find out, because the error message displayed gets you to search around problems with wxGTK and such...

Résumé: -gtk must not be in the USE flags, else, it won't compile, even though other dependencies will

-------------

# emerge -vp amule

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] net-p2p/amule-9900 USE="daemon debug geoip gtk
nls remote stats unicode upnp -xchat" 0 kB [1]

Compile and work fine here on ~amd64 with gcc-4.4.2, gtk+-2.18.3 and wxGTK-2.8.10.1. --[[User:Libre|Libre]] 16:45, 14 December 2009 (UTC)

And it depend of what you want to do. Wuth USE="-gtk", it will compile the console version, and you will be able to control it from your browser or from another computer with the appropriate setup. --[[User:Libre|Libre]] 16:14, 21 October 2010 (UTC)

HowTo Compile In Gentoo

2010-10-21T16:04:56Z

Libre: /* Possible crash */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

# bleeding-edge development
MY_P="aMule-SVN-r${PV}"
# 2_2_X branch, currently unavailable
# MY_P="aMule-SVN-r${PV}-RELEASE-2_2_X"

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 geoip gtk nls remote stats unicode upnp xchat"

RESTRICT="nomirror"

DEPEND="=x11-libs/wxGTK-2.8*
>=dev-libs/crypto++-5.5.2
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26[jpeg] )
geoip? ( dev-libs/geoip )
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

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

HowTo Compile In Gentoo

2010-10-10T23:46:30Z

Libre: /* Possible crash */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

# bleeding-edge development
MY_P="aMule-SVN-r${PV}"
# 2_2_X branch, currently unavailable
# MY_P="aMule-SVN-r${PV}-RELEASE-2_2_X"

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 geoip gtk nls remote stats unicode upnp xchat"

RESTRICT="nomirror"

DEPEND="=x11-libs/wxGTK-2.8*
>=dev-libs/crypto++-5.5.2
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26[jpeg] )
geoip? ( dev-libs/geoip )
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

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

HowTo Compile In Gentoo

2010-10-10T23:29:10Z

Libre: /* amule SVN */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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 [http://amule.sourceforge.net/tarballs/ tarballs page], otherwise your ebuild will fail.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

# bleeding-edge development
MY_P="aMule-SVN-r${PV}"
# 2_2_X branch, currently unavailable
# MY_P="aMule-SVN-r${PV}-RELEASE-2_2_X"

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 geoip gtk nls remote stats unicode upnp xchat"

RESTRICT="nomirror"

DEPEND="=x11-libs/wxGTK-2.8*
>=dev-libs/crypto++-5.5.2
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26[jpeg] )
geoip? ( dev-libs/geoip )
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

==== Possible crash ====

Talk:HowTo Compile In Gentoo

2009-12-14T16:45:46Z

Libre:

PORTAGE_OVERLAY="/usr/local/portage" can't be use anymore must use :

PORTDIR_OVERLAY="/usr/local/portage"

'''Done'''

--------------------------

You forgot to mention that the (allegedly stable) build usually fails. For a while it worked only with the crypto++ library installed; now it doesn't compile at all. Perhaps this is because of the recent gcc 3.4 update, but I don't know for sure.

--------------------------

Also, you should add the fact that, you *must not* have "-gtk" in your USE flags... It was a real pain in the ... grass to find out, because the error message displayed gets you to search around problems with wxGTK and such...

Résumé: -gtk must not be in the USE flags, else, it won't compile, even though other dependencies will

-------------

# emerge -vp amule

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] net-p2p/amule-9900 USE="daemon debug geoip gtk
nls remote stats unicode upnp -xchat" 0 kB [1]

Compile and work fine here on ~amd64 with gcc-4.4.2, gtk+-2.18.3 and wxGTK-2.8.10.1. --[[User:Libre|Libre]] 16:45, 14 December 2009 (UTC)

HowTo Compile In Gentoo

2009-08-27T16:29:16Z

Libre: /* amule SVN - updated ebuild for 2_2_X trunk */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

# old trunk
# MY_P="aMule-SVN-r${PV}"
# current 2_2_X trunk
MY_P="aMule-SVN-r${PV}-RELEASE-2_2_X"

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 geoip gtk nls remote stats unicode upnp xchat"

RESTRICT="nomirror"

DEPEND="=x11-libs/wxGTK-2.8*
>=dev-libs/crypto++-5.5.2
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26[jpeg] )
geoip? ( dev-libs/geoip )
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

HowTo Compile In Gentoo

2009-08-04T06:59:57Z

Libre: /* amule SVN - updated ebuild */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic 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 geoip gtk nls remote stats unicode upnp xchat"

RESTRICT="nomirror"

DEPEND="=x11-libs/wxGTK-2.8*
>=dev-libs/crypto++-5.5.2
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26[jpeg] )
geoip? ( dev-libs/geoip )
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

Backtraces

2009-08-02T06:27:02Z

Libre: /* On Gentoo */

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

== Introduction ==
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 [http://subversion.tigris.org SVN] 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.

== The GNU Debugger ==
First of all, you need the [http://www.gnu.org/software/gdb/gdb.html 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 don't have [http://www.gnu.org/software/gdb/gdb.html GDB] installed, you will get a message like this: 

$ which gdb
which: no gdb in (/bin:/usr/bin:[etc])

If that is the case, the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] is most likely not installed on your system and you should install it before you proceed.

If your OS is [http://www.gentoo.org Gentoo Linux] you have just to type this:
# emerge -av gdb

== Compiling [[aMule]] ==
Then, compile [[aMule]] with debugging information:

$ ./configure --enable-debug --disable-optimize --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-optimize
$ make

[[aMule]] can then be run by going into 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.

=== On Gentoo ===
You must follow [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo].

In short, most gentoo users want to edit ''/etc/make.conf'', add ''-ggdb'' into their CFLAGS and
FEATURES="splitdebug"
Those are needed by gdb in order to find the debug symbols.
Emerge amule as usual with
USE="debug" emerge amule
If you don't use ''USE="debug"'', you will get a little bit less information from gdb, so it is better to use it.
After merging amule, you can safely remove ''-ggdb'' and ''splitdebug'' from ''/etc/make.conf''.

== Create a backtrace ==
Now create in your home directory the file ''.gdbinit'' and put these lines into it (or you can type them in at the ''(gdb)'' prompt later):

ha SIGPIPE nostop noprint pass
ha SIG32 nostop noprint pass
ha SIG33 nostop noprint pass
ha SIG34 nostop noprint pass

For those who want to know the meaning of the previous lines:
the first one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at broken pipes;
the second one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at new thread.

To create a backtrace, open a console and do the following:

$ gdb /where/to/install/aMule/bin/amule
(gdb) run

Now use [[aMule]] normally until it crashes. If it crashes do the following:

(gdb) bt
(gdb) bt full
(gdb) thread apply all bt

Post the output of the last three commands in the [http://forum.amule.org/index.php?board=33.0 backtraces forum] with some additional comment about the circumstances the segfault happened and what [[aMule]] version you used (or checkout time for [http://www.gnu.org/software/cvs CVS]).

== The core file ==
If your [[aMule]] executable has been compiled with debug information (''--enable-debug'' configure flag), but you were not running it from within [http://www.gnu.org/software/gdb/gdb.html GDB], there is still a way to generate a backtrace, if your system was configured to generate '''core files'''.

Core files are the full memory image of a process that crashed. Your session must be properly configured, so that the system generates core files. Add the following command to ''~/.bashrc'':

''ulimit -c unlimited''

Now, when a program crashes, suppose it generate the file ''core.1234'' (this name can be different, but usually will start with 'core') you can enter [http://www.gnu.org/software/gdb/gdb.html GDB] like that:

''$ gdb --core=/path/to/amule /path/to/core/file/core.1234''

REMARK: ''$ gdb /path/to/amule --core=/path/to/core/file/core.<pid>''

and then proceed as in the last session and issue 'bt' and 'bt full'.

So, that's it, have fun with [[aMule]]

Greetings, [[User:Citroklar|Citroklar]] & [[User:Phoenix|Phoenix]]

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

Please read [[Using_gdb_and_valgrind|this]] to learn more about [http://www.gnu.org/software/gdb/gdb.html GDB] and [http://valgrind.kde.org Valgrind].

== General pitfalls and caveats ==

;<tt>-fomit-frame-pointer</tt>
:On <tt>x86</tt> platforms the <tt>-fomit-frame-pointer</tt> compiler flag usually results in an extra free register to use, but unfortunately it most likely causes ''gdb'' to be unable to parse the resulting executable. Check your <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> variables.

;<tt>-fPIE</tt>
:If you use the <tt>-fPIE</tt> compiler flag to compile aMule, you must use <tt>-nopie</tt> for the linking stage: add <tt>-nopie</tt> to your <tt>LDFLAGS</tt>.

;Stripping binaries
:You must not strip the binaries (remove debug info), if you want to create a backtrace. The make process does not automatically strip the binaries, except for the <tt>install-strip</tt> target. Do not use it.
:The GNU linker (<tt>ld</tt>) is capable of automatically stripping the binaries, if the <tt>-s</tt> or <tt>-S</tt> flag is passed to it. This is usually passed via <tt>LDFLAGS</tt> as <tt>-Wl,-s</tt> or <tt>-Wl,-S</tt>. Please check that you don't use any of them.

== Examples ==

#0 0x000000000057b790 in ?? ()
#1 0x000000000051e66b in ?? ()
#2 0x000000000051edb6 in ?? ()
...

This is an exmple of an unuseful backtrace. It doesn't show where the error happened and what went wrong. If your backtrace looks like this, it is pretty unuseful for us. This backtrace is either created from a binary without debug information (stripped), or ''gdb'' was unable to parse it (see above section).

#0 0x1003f604 in CUpDownClient::ClearDownloadBlockRequests ()
#1 0x10044978 in CUpDownClient::Disconnected ()
#2 0x1004d958 in CClientList::ProcessDirectCallbackList ()
...

Now this is better, but still not enough. We now have global symbols, so we can see which function called which. But this still lacks line number and local symbol information, making it really hard to find the cause of the crash.

#0 0x000000000046fcab in CUpDownClient::ClearDownloadBlockRequests (this=0x45bf9e0) at BaseClient.cpp:1175
#1 0x00000000004d1480 in CUpDownClient::SetDownloadState (this=0x45bf9e0, byNewState=1 '\001') at DownloadClient.cpp:541
#2 0x00000000004703bd in CUpDownClient::Disconnected (this=0x45bf9e0, strReason=@0x7ffffc74e2b0, bFromSocket=false) at BaseClient.cpp:1239
...

Well, this is what I call a useful backtrace. It has both global and local symbols and line numbers. Now we can see the program state as it was at the time of the crash, and can possibly "easily" identify, what went wrong.

== Links ==
* [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo]

HowTo Compile In Gentoo

2009-08-02T06:13:24Z

Libre: /* amule SVN */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

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

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

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

RESTRICT="nomirror"

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

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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

HowTo Compile In Gentoo

2009-08-02T06:11:55Z

Libre: /* added xchat into ehe ebuild */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

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

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

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

RESTRICT="nomirror"

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

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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
$(use_enable xchat xas) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

HowTo Compile In Gentoo

2009-08-01T20:19:08Z

Libre: /* amule SVN */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

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

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

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

RESTRICT="nomirror"

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

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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

HowTo Compile In Gentoo

2009-08-01T19:52:01Z

Libre: /* Introduction */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

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

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

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

RESTRICT="nomirror"

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

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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

HowTo Compile In Gentoo

2009-08-01T19:48:18Z

Libre: /* Introduction */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

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

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

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

RESTRICT="nomirror"

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

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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

HowTo Compile In Gentoo-es

2009-08-01T19:44:00Z

Libre:

<h1>Someone should check how recent this Article is, and update it for 2.2.5</h1>

<center>[[HowTo_Compile_In_Gentoo|English]] | '''Español''' | [[HowTo_Compile_In_Gentoo-de|Alemán]]</center>

== Introducción ==
Gentoo es conocido por sus opciones. Desgraciadamente, algunas opciones requieren más trabajo que otras. Como tal, [[aMule]] entra una variedad de versiones y de metodos de instalación basados en la versión de [[WxWidgets|wxGTK]] que usted decide utilizar.

== Métodos de Instalación ==
=== amule-2.0.3.ebuild ===
Este ebuild esta marquado como '''estable''' para todas arquitecturas.

Este ebuild se corresponde con la version mas actualizada y estable disponible de [[aMule]].

Dependencias: >=x11-libs/wxGTK-2.6.0; >=sys-libs/zlib-1.2.2; sys-devel/gettext; >=media-libs/libpng-1.2.8; >=media-libs/gd-2.0.32

=== amule-svn ===
Este ebuild esta marcado como '''inestable''' para todas arquitecturas.

No destinado para el publico general. Si usted quere probar el paquete desarrollado diariamente, entonces esta es la version para usted.

Dependencias: >=x11-libs/wxGTK-2.6.0; >=sys-libs/zlib-1.2.1; >=media-libs/gd-2.0.26; >=media-libs/libpng-1.2.0 
Status: Desarrollo; no en Portage; requiere portage overlay

== Instrucciones de Instalación ==
=== amule-2.0.3.ebuild ===
1. Haga emerge del paquete:
emerge --sync
emerge amule -pv
emerge amule

=== amule-svn ===
El ebuild acutal para [[aMule SVN]] se puede encontrar [http://forum.amule.org/index.php?topic=5732 aquí]. Descárguelo y continúe con este artículo.

1. Definir ''PORTDIR_OVERLAY''. Abra ''/etc/make.conf'' con su editor de texto preferido y defina la varible ''PORTDIR_OVERLAY''. Por defecto es:
PORTDIR_OVERLAY="/usr/local/portage"

2. Cree el overlay para ''amule-svn-2'':
mkdir -p {PORTDIR_OVERLAY}/net-p2p/amule-svn-2

3. Agregue a package.keywords:
echo "net-p2p/amule-svn ~x86" >> /etc/portage/package.keywords

4. Copie [http://forum.amule.org/thread.php?postid=38002#post38002 amule-svn-2.ebuild] a ''{PORTDIR_OVERLAY}/net-p2p/amule-svn-2'':

5. Cambie al directorio:
cd {PORTDIR_OVERLAY}/net-p2p/amule-svn-2/

6. Haga touch en el archivo:
touch amule-svn-2.ebuild

7. Digiera el ebuild:
ebuild amule-svn-2.ebuild digest

8. Revise las opciones de la instalación:
emerge amule-svn -pv

9. Modifique ''/etc/portage/package.use'' para convenir sus necesidades (por favor nota que ''debug'' será activado sin condición).
net-p2p/amule-svn X -amuled -debug gtk2 kad nls -nosystray -optimize -remote -remote-gui -stats unicode

10. Finalmente, haga emerge [[aMule SVN]].
emerge amule-svn

'''POR FAVOR! POR FAVOR! POR FAVOR!''' haga ''emerge amule-svn -pv'' antes de instalar para determinar como quires compilar aMule-SVN.

HowTo Compile In Gentoo

2009-08-01T19:43:04Z

Libre: /* update date */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

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

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

== 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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

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

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

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

RESTRICT="nomirror"

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

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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

HowTo Compile In Gentoo

2009-08-01T19:41:14Z

Libre: /* Removed outdated aMule 2.1.1 Compilation FAQ */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>
I am currently editing this very outdated article!
English version updated: 23.12.2007 - Newest Gentoo Version are now 2.2.5.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

== 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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

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

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

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

RESTRICT="nomirror"

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

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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die
}

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. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

HowTo Compile In Gentoo

2009-08-01T19:39:15Z

Libre: /* amule SVN */

HowTo Compile In Gentoo

2009-08-01T19:18:50Z

Libre: /* amule SVN - current ebuild */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>
I am currently editing this very outdated article!
English version updated: 23.12.2007 - Newest Gentoo Version are now 2.2.5.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

== 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: [http://en.gentoo-wiki.com/wiki/Overlay#Creating_a_local_overlay 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.

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

EAPI="2"

inherit eutils flag-o-matic wxwidgets

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

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

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

RESTRICT="nomirror"

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

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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable daemon amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die
}

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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2009-08-01T19:03:53Z

Libre: /* Installation instructions - 2.2.5 */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>
I am currently editing this very outdated article!
English version updated: 23.12.2007 - Newest Gentoo Version are now 2.2.5.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

== 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 (latest one) ===
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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

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

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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-svn"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/svn/${MY_PN}-SVN-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2009-08-01T18:59:04Z

Libre: /* Removed outdated amule and wxGTK-2.8* */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>
I am currently editing this very outdated article!
English version updated: 23.12.2007 - Newest Gentoo Version are now 2.2.5.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

== 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 ==
They must be updated to reflect the actual portage state. Some volunteer?
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule SVN (latest one) ===
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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

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

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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-svn"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/svn/${MY_PN}-SVN-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2009-08-01T18:58:21Z

Libre: /* amule-2.1.3.ebuild */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>
I am currently editing this very outdated article!
English version updated: 23.12.2007 - Newest Gentoo Version are now 2.2.5.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

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

=== amule and wxGTK-2.8* ===
It is a few ebuilds for compiling amule against wxGTK-2.8* at that time of writing (1-11-2008): amule-2.1.3-r1.ebuild (the same as above, but for wxGTK-2.8*); amule-2.2.0_pre20080304.ebuild (2.2.0 pre-release); amule-2.2.1.ebuild (stable version of amule); amule-2.2.2.ebuild (last stable amule release).

They can be marked as stable or unstable depending to your arch.

Dependencies for the 2.2.2 version: >=x11-libs/wxGTK-2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/crypto°°-5.5.2; unicode? stats? >=media-libs/gd-2.0.26; remote? >=media-libs/libpng-1.2.0; geoip? devs-libs/geoip ; upnp? net-libs/libupnp.

== Installation instructions ==
They must be updated to reflect the actual portage state. Some volunteer?
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule SVN (latest one) ===
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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

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

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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-svn"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/svn/${MY_PN}-SVN-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2009-08-01T18:48:19Z

Libre: /* Introduction */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>
I am currently editing this very outdated article!
English version updated: 23.12.2007 - Newest Gentoo Version are now 2.2.5.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

== Methods of Installation ==
=== amule-2.1.3.ebuild ===
This ebuild matches the 2.1.3 stable [[aMule]] release, it is available 13.10.2007 in portage.

Dependencies: >=x11-libs/wxGTK-2.6.*; >=sys-libs/zlib-1.2.1; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support.

=== amule and wxGTK-2.8* ===
It is a few ebuilds for compiling amule against wxGTK-2.8* at that time of writing (1-11-2008): amule-2.1.3-r1.ebuild (the same as above, but for wxGTK-2.8*); amule-2.2.0_pre20080304.ebuild (2.2.0 pre-release); amule-2.2.1.ebuild (stable version of amule); amule-2.2.2.ebuild (last stable amule release).

They can be marked as stable or unstable depending to your arch.

Dependencies for the 2.2.2 version: >=x11-libs/wxGTK-2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/crypto°°-5.5.2; unicode? stats? >=media-libs/gd-2.0.26; remote? >=media-libs/libpng-1.2.0; geoip? devs-libs/geoip ; upnp? net-libs/libupnp.

== Installation instructions ==
They must be updated to reflect the actual portage state. Some volunteer?
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule SVN (latest one) ===
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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

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

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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-svn"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/svn/${MY_PN}-SVN-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2009-08-01T18:46:36Z

Libre:

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>
I am currently editing this very outdated article!
English version updated: 23.12.2007 - Newest Gentoo Version are now 2.2.5.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

Also, if you plan to build a GUI-less core, you might want to take a look at http://bugs.gentoo.org/show_bug.cgi?id=109515, comment #3 contains a patch for wxGTK-2.6 ebuild that removes the dependency on X.

== Methods of Installation ==
=== amule-2.1.3.ebuild ===
This ebuild matches the 2.1.3 stable [[aMule]] release, it is available 13.10.2007 in portage.

Dependencies: >=x11-libs/wxGTK-2.6.*; >=sys-libs/zlib-1.2.1; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support.

=== amule and wxGTK-2.8* ===
It is a few ebuilds for compiling amule against wxGTK-2.8* at that time of writing (1-11-2008): amule-2.1.3-r1.ebuild (the same as above, but for wxGTK-2.8*); amule-2.2.0_pre20080304.ebuild (2.2.0 pre-release); amule-2.2.1.ebuild (stable version of amule); amule-2.2.2.ebuild (last stable amule release).

They can be marked as stable or unstable depending to your arch.

Dependencies for the 2.2.2 version: >=x11-libs/wxGTK-2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/crypto°°-5.5.2; unicode? stats? >=media-libs/gd-2.0.26; remote? >=media-libs/libpng-1.2.0; geoip? devs-libs/geoip ; upnp? net-libs/libupnp.

== Installation instructions ==
They must be updated to reflect the actual portage state. Some volunteer?
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule SVN (latest one) ===
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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

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

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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-svn"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/svn/${MY_PN}-SVN-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2009-08-01T18:42:07Z

Libre: /* Removed outdated amule SVN (portage) */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

English version updated: 23.12.2007 - Newest Gentoo Version are now 2.1.3 as well that 2 SVN versions.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

Also, if you plan to build a GUI-less core, you might want to take a look at http://bugs.gentoo.org/show_bug.cgi?id=109515, comment #3 contains a patch for wxGTK-2.6 ebuild that removes the dependency on X.

== Methods of Installation ==
=== amule-2.1.3.ebuild ===
This ebuild matches the 2.1.3 stable [[aMule]] release, it is available 13.10.2007 in portage.

Dependencies: >=x11-libs/wxGTK-2.6.*; >=sys-libs/zlib-1.2.1; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support.

=== amule and wxGTK-2.8* ===
It is a few ebuilds for compiling amule against wxGTK-2.8* at that time of writing (1-11-2008): amule-2.1.3-r1.ebuild (the same as above, but for wxGTK-2.8*); amule-2.2.0_pre20080304.ebuild (2.2.0 pre-release); amule-2.2.1.ebuild (stable version of amule); amule-2.2.2.ebuild (last stable amule release).

They can be marked as stable or unstable depending to your arch.

Dependencies for the 2.2.2 version: >=x11-libs/wxGTK-2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/crypto°°-5.5.2; unicode? stats? >=media-libs/gd-2.0.26; remote? >=media-libs/libpng-1.2.0; geoip? devs-libs/geoip ; upnp? net-libs/libupnp.

== Installation instructions ==
They must be updated to reflect the actual portage state. Some volunteer?
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule SVN (latest one) ===
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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

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

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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-svn"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/svn/${MY_PN}-SVN-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2009-08-01T18:41:14Z

Libre: /* Remived outdated amule-2.2.0_pre-20071204, */

<center>
'''English''' |
[[HowTo_Compile_In_Gentoo-de|Deutsch]] |
[[HowTo_Compile_In_Gentoo-es|Español]]
</center>

English version updated: 23.12.2007 - Newest Gentoo Version are now 2.1.3 as well that 2 SVN versions.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[WxWidgets|wxGTK]] you decide to use...

Also, if you plan to build a GUI-less core, you might want to take a look at http://bugs.gentoo.org/show_bug.cgi?id=109515, comment #3 contains a patch for wxGTK-2.6 ebuild that removes the dependency on X.

== Methods of Installation ==
=== amule-2.1.3.ebuild ===
This ebuild matches the 2.1.3 stable [[aMule]] release, it is available 13.10.2007 in portage.

Dependencies: >=x11-libs/wxGTK-2.6.*; >=sys-libs/zlib-1.2.1; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support.

=== amule and wxGTK-2.8* ===
It is a few ebuilds for compiling amule against wxGTK-2.8* at that time of writing (1-11-2008): amule-2.1.3-r1.ebuild (the same as above, but for wxGTK-2.8*); amule-2.2.0_pre20080304.ebuild (2.2.0 pre-release); amule-2.2.1.ebuild (stable version of amule); amule-2.2.2.ebuild (last stable amule release).

They can be marked as stable or unstable depending to your arch.

Dependencies for the 2.2.2 version: >=x11-libs/wxGTK-2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/crypto°°-5.5.2; unicode? stats? >=media-libs/gd-2.0.26; remote? >=media-libs/libpng-1.2.0; geoip? devs-libs/geoip ; upnp? net-libs/libupnp.

== Installation instructions ==
They must be updated to reflect the actual portage state. Some volunteer?
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule SVN (portage) ===
Portage have 2 SVN ebuilds: amule-2.2.0_pre20070422.ebuild with wXgtk-2.6 support and amule-2.2.0_pre20071204.ebuild with wXgtk-2.8 support. Both are marked as '''unstable''' for all architectures.

====To install amule-2.2.0_pre20070422:====
1. Add to ''package.keywords'':
echo "net-p2p/amule ~x86" >> /etc/portage/package.keywords

2. Review installation flags:
emerge amule -pv

3. Modify ''/etc/portage/package.use'' to suit your needs :
net-p2p/amule -amuled -debug 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 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

Personally, I have the unicode USE flag in /etc/make.conf so that any program that support unicode will be compiled with unicode support.

4. Install [[aMule]]:
emerge amule

=== amule SVN (latest one) ===
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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

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

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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-svn"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/svn/${MY_PN}-SVN-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule SVN]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

Backtraces

2009-07-31T16:39:29Z

Libre: /* On Gentoo */

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

== Introduction ==
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 [http://subversion.tigris.org SVN] 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.

== The GNU Debugger ==
First of all, you need the [http://www.gnu.org/software/gdb/gdb.html 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 don't have [http://www.gnu.org/software/gdb/gdb.html GDB] installed, you will get a message like this: 

$ which gdb
which: no gdb in (/bin:/usr/bin:[etc])

If that is the case, the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] is most likely not installed on your system and you should install it before you proceed.

If your OS is [http://www.gentoo.org Gentoo Linux] you have just to type this:
# emerge -av gdb

== Compiling [[aMule]] ==
Then, compile [[aMule]] with debugging information:

$ ./configure --enable-debug --disable-optimize --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-optimize
$ make

[[aMule]] can then be run by going into 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.

=== On Gentoo ===
You must follow [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo].

In short, most gentoo users want to edit /etc/make.conf, add "-ggdb" into their CFLAGS and
FEATURES="splitdebug"
Those are needed by gdb in order to find the debug symbols.
Emerge amule as usual with
USE="debug" emerge amule
If you don't use "USE="debug"", you will get a little bit less information from gdb, so it is better to use it.
After merging amule, you can safely remove -ggdb and splitdebug from /etc/make.conf.

== Create a backtrace ==
Now create in your home directory the file ''.gdbinit'' and put these lines into it (or you can type them in at the ''(gdb)'' prompt later):

ha SIGPIPE nostop noprint pass
ha SIG32 nostop noprint pass
ha SIG33 nostop noprint pass
ha SIG34 nostop noprint pass

For those who want to know the meaning of the previous lines:
the first one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at broken pipes;
the second one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at new thread.

To create a backtrace, open a console and do the following:

$ gdb /where/to/install/aMule/bin/amule
(gdb) run

Now use [[aMule]] normally until it crashes. If it crashes do the following:

(gdb) bt
(gdb) bt full
(gdb) thread apply all bt

Post the output of the last three commands in the [http://forum.amule.org/index.php?board=33.0 backtraces forum] with some additional comment about the circumstances the segfault happened and what [[aMule]] version you used (or checkout time for [http://www.gnu.org/software/cvs CVS]).

== The core file ==
If your [[aMule]] executable has been compiled with debug information (''--enable-debug'' configure flag), but you were not running it from within [http://www.gnu.org/software/gdb/gdb.html GDB], there is still a way to generate a backtrace, if your system was configured to generate '''core files'''.

Core files are the full memory image of a process that crashed. Your session must be properly configured, so that the system generates core files. Add the following command to ''~/.bashrc'':

''ulimit -c unlimited''

Now, when a program crashes, suppose it generate the file ''core.1234'' (this name can be different, but usually will start with 'core') you can enter [http://www.gnu.org/software/gdb/gdb.html GDB] like that:

''$ gdb --core=/path/to/amule /path/to/core/file/core.1234''

REMARK: ''$ gdb /path/to/amule --core=/path/to/core/file/core.<pid>''

and then proceed as in the last session and issue 'bt' and 'bt full'.

So, that's it, have fun with [[aMule]]

Greetings, [[User:Citroklar|Citroklar]] & [[User:Phoenix|Phoenix]]

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

Please read [[Using_gdb_and_valgrind|this]] to learn more about [http://www.gnu.org/software/gdb/gdb.html GDB] and [http://valgrind.kde.org Valgrind].

== General pitfalls and caveats ==

;<tt>-fomit-frame-pointer</tt>
:On <tt>x86</tt> platforms the <tt>-fomit-frame-pointer</tt> compiler flag usually results in an extra free register to use, but unfortunately it most likely causes ''gdb'' to be unable to parse the resulting executable. Check your <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> variables.

;<tt>-fPIE</tt>
:If you use the <tt>-fPIE</tt> compiler flag to compile aMule, you must use <tt>-nopie</tt> for the linking stage: add <tt>-nopie</tt> to your <tt>LDFLAGS</tt>.

;Stripping binaries
:You must not strip the binaries (remove debug info), if you want to create a backtrace. The make process does not automatically strip the binaries, except for the <tt>install-strip</tt> target. Do not use it.
:The GNU linker (<tt>ld</tt>) is capable of automatically stripping the binaries, if the <tt>-s</tt> or <tt>-S</tt> flag is passed to it. This is usually passed via <tt>LDFLAGS</tt> as <tt>-Wl,-s</tt> or <tt>-Wl,-S</tt>. Please check that you don't use any of them.

== Examples ==

#0 0x000000000057b790 in ?? ()
#1 0x000000000051e66b in ?? ()
#2 0x000000000051edb6 in ?? ()
...

This is an exmple of an unuseful backtrace. It doesn't show where the error happened and what went wrong. If your backtrace looks like this, it is pretty unuseful for us. This backtrace is either created from a binary without debug information (stripped), or ''gdb'' was unable to parse it (see above section).

#0 0x1003f604 in CUpDownClient::ClearDownloadBlockRequests ()
#1 0x10044978 in CUpDownClient::Disconnected ()
#2 0x1004d958 in CClientList::ProcessDirectCallbackList ()
...

Now this is better, but still not enough. We now have global symbols, so we can see which function called which. But this still lacks line number and local symbol information, making it really hard to find the cause of the crash.

#0 0x000000000046fcab in CUpDownClient::ClearDownloadBlockRequests (this=0x45bf9e0) at BaseClient.cpp:1175
#1 0x00000000004d1480 in CUpDownClient::SetDownloadState (this=0x45bf9e0, byNewState=1 '\001') at DownloadClient.cpp:541
#2 0x00000000004703bd in CUpDownClient::Disconnected (this=0x45bf9e0, strReason=@0x7ffffc74e2b0, bFromSocket=false) at BaseClient.cpp:1239
...

Well, this is what I call a useful backtrace. It has both global and local symbols and line numbers. Now we can see the program state as it was at the time of the crash, and can possibly "easily" identify, what went wrong.

== Links ==
* [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo]

Backtraces

2009-07-31T16:37:15Z

Libre: /* Compiling aMule on gentoo */

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

== Introduction ==
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 [http://subversion.tigris.org SVN] 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.

== The GNU Debugger ==
First of all, you need the [http://www.gnu.org/software/gdb/gdb.html 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 don't have [http://www.gnu.org/software/gdb/gdb.html GDB] installed, you will get a message like this: 

$ which gdb
which: no gdb in (/bin:/usr/bin:[etc])

If that is the case, the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] is most likely not installed on your system and you should install it before you proceed.

If your OS is [http://www.gentoo.org Gentoo Linux] you have just to type this:
# emerge -av gdb

== Compiling [[aMule]] ==
Then, compile [[aMule]] with debugging information:

$ ./configure --enable-debug --disable-optimize --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-optimize
$ make

[[aMule]] can then be run by going into 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.

=== On Gentoo ===
You must follow [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo].

In short, most gentoo users want to edit /etc/make.conf, add "-ggdb" into their CFLAGS and
FEATURES="splitdebug"
Those are needed by gdb in order to find the debug symbols.
Emerge amule as usual with
USE="debug" emerge amule
If you don't use "USE="debug"", you will get a little bit less information from gdb, so it is better to use it.

== Create a backtrace ==
Now create in your home directory the file ''.gdbinit'' and put these lines into it (or you can type them in at the ''(gdb)'' prompt later):

ha SIGPIPE nostop noprint pass
ha SIG32 nostop noprint pass
ha SIG33 nostop noprint pass
ha SIG34 nostop noprint pass

For those who want to know the meaning of the previous lines:
the first one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at broken pipes;
the second one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at new thread.

To create a backtrace, open a console and do the following:

$ gdb /where/to/install/aMule/bin/amule
(gdb) run

Now use [[aMule]] normally until it crashes. If it crashes do the following:

(gdb) bt
(gdb) bt full
(gdb) thread apply all bt

Post the output of the last three commands in the [http://forum.amule.org/index.php?board=33.0 backtraces forum] with some additional comment about the circumstances the segfault happened and what [[aMule]] version you used (or checkout time for [http://www.gnu.org/software/cvs CVS]).

== The core file ==
If your [[aMule]] executable has been compiled with debug information (''--enable-debug'' configure flag), but you were not running it from within [http://www.gnu.org/software/gdb/gdb.html GDB], there is still a way to generate a backtrace, if your system was configured to generate '''core files'''.

Core files are the full memory image of a process that crashed. Your session must be properly configured, so that the system generates core files. Add the following command to ''~/.bashrc'':

''ulimit -c unlimited''

Now, when a program crashes, suppose it generate the file ''core.1234'' (this name can be different, but usually will start with 'core') you can enter [http://www.gnu.org/software/gdb/gdb.html GDB] like that:

''$ gdb --core=/path/to/amule /path/to/core/file/core.1234''

REMARK: ''$ gdb /path/to/amule --core=/path/to/core/file/core.<pid>''

and then proceed as in the last session and issue 'bt' and 'bt full'.

So, that's it, have fun with [[aMule]]

Greetings, [[User:Citroklar|Citroklar]] & [[User:Phoenix|Phoenix]]

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

Please read [[Using_gdb_and_valgrind|this]] to learn more about [http://www.gnu.org/software/gdb/gdb.html GDB] and [http://valgrind.kde.org Valgrind].

== General pitfalls and caveats ==

;<tt>-fomit-frame-pointer</tt>
:On <tt>x86</tt> platforms the <tt>-fomit-frame-pointer</tt> compiler flag usually results in an extra free register to use, but unfortunately it most likely causes ''gdb'' to be unable to parse the resulting executable. Check your <tt>CFLAGS</tt> and <tt>CXXFLAGS</tt> variables.

;<tt>-fPIE</tt>
:If you use the <tt>-fPIE</tt> compiler flag to compile aMule, you must use <tt>-nopie</tt> for the linking stage: add <tt>-nopie</tt> to your <tt>LDFLAGS</tt>.

;Stripping binaries
:You must not strip the binaries (remove debug info), if you want to create a backtrace. The make process does not automatically strip the binaries, except for the <tt>install-strip</tt> target. Do not use it.
:The GNU linker (<tt>ld</tt>) is capable of automatically stripping the binaries, if the <tt>-s</tt> or <tt>-S</tt> flag is passed to it. This is usually passed via <tt>LDFLAGS</tt> as <tt>-Wl,-s</tt> or <tt>-Wl,-S</tt>. Please check that you don't use any of them.

== Examples ==

#0 0x000000000057b790 in ?? ()
#1 0x000000000051e66b in ?? ()
#2 0x000000000051edb6 in ?? ()
...

This is an exmple of an unuseful backtrace. It doesn't show where the error happened and what went wrong. If your backtrace looks like this, it is pretty unuseful for us. This backtrace is either created from a binary without debug information (stripped), or ''gdb'' was unable to parse it (see above section).

#0 0x1003f604 in CUpDownClient::ClearDownloadBlockRequests ()
#1 0x10044978 in CUpDownClient::Disconnected ()
#2 0x1004d958 in CClientList::ProcessDirectCallbackList ()
...

Now this is better, but still not enough. We now have global symbols, so we can see which function called which. But this still lacks line number and local symbol information, making it really hard to find the cause of the crash.

#0 0x000000000046fcab in CUpDownClient::ClearDownloadBlockRequests (this=0x45bf9e0) at BaseClient.cpp:1175
#1 0x00000000004d1480 in CUpDownClient::SetDownloadState (this=0x45bf9e0, byNewState=1 '\001') at DownloadClient.cpp:541
#2 0x00000000004703bd in CUpDownClient::Disconnected (this=0x45bf9e0, strReason=@0x7ffffc74e2b0, bFromSocket=false) at BaseClient.cpp:1239
...

Well, this is what I call a useful backtrace. It has both global and local symbols and line numbers. Now we can see the program state as it was at the time of the crash, and can possibly "easily" identify, what went wrong.

== Links ==
* [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo]

HowTo Compile In Gentoo

2007-12-23T21:42:23Z

Libre: /* amule CVS (latest one) */

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

English version updated: 23.12.2007 - Newest Gentoo Version are now 2.1.3 as well that 2 CVS versions.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[wxGTK]] you decide to use...

Also, if you plan to build a GUI-less core, you might want to take a look at http://bugs.gentoo.org/show_bug.cgi?id=109515, comment #3 contains a patch for wxGTK ebuild that removes the dependency on X.

== Methods of Installation ==
=== amule-2.1.3.ebuild ===
This ebuild matches the most current, stable [[aMule]] release, it is available 13.10.2007 in portage.

Dependencies: >=x11-libs/wxGTK-2.6.*; >=sys-libs/zlib-1.2.1; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support.

=== amule-cvs ===
This ebuild is marked as '''unstable''' for all architectures.

Not intended for the general public. If you'd like to test out the daily development snapshot, then this is the version for you.

Dependencies: >=x11-libs/wxGTK-2.6.* or 2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/gd-2.0.26; >=media-libs/libpng-1.2.0; devs-libs/geoip 
Status: In development; 2 versions in portage; the latest tarball need a personal portage overlay

== Installation instructions ==
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule CVS (portage) ===
Portage have 2 CVS ebuilds: amule-2.2.0_pre20070422.ebuild with wXgtk-2.6 support and amule-2.2.0_pre20071204.ebuild with wXgtk-2.8 support. Both are marked as '''unstable''' for all architectures.

====To install amule-2.2.0_pre20070422:====

1. Add to ''package.keywords'':
echo "net-p2p/amule ~x86" >> /etc/portage/package.keywords

2. Review installation flags:
emerge amule -pv

3. Modify ''/etc/portage/package.use'' to suit your needs :
net-p2p/amule -amuled -debug 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 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

Personally, I have the unicode USE flag in /etc/make.conf so that any program that support unicode will be compiled with unicode support.

4. Install [[aMule]]:
emerge amule

====To install amule-2.2.0_pre-20071204,====
we need to unmask wXgtk-2.8. Process like for amule-2.2.0_pre20070422, but with this supplementary step:

1. Unmask amule-2.2.0_pre-20071204 and wXgtk-2.8
echo "=net-p2p/amule-2.2.0_pre20071204" >> /etc/portage/package.unmask
echo "=x11-libs/wxGTK-2.8.7.1" >> /etc/portage/package.unmask

=== amule CVS (latest one) ===
It is no ebuild for the current [[aMule CVS]] 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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

We will also follow the naming scheme of portage. CVS ebuild from a CVS tarball are not named as '''package_name-cvs''' but as '''package_name-version_date_of_the_tarball'''. That is to distinguish them from real CVS ebuilds (the so called live ebuilds) named as '''package_name-9999''' and using keywords="".

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-cvs:
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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-cvs"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/cvs/${MY_PN}-CVS-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

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

9. Install [[aMule CVS]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2007-12-23T21:40:31Z

Libre:

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

English version updated: 23.12.2007 - Newest Gentoo Version are now 2.1.3 as well that 2 CVS versions.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[wxGTK]] you decide to use...

Also, if you plan to build a GUI-less core, you might want to take a look at http://bugs.gentoo.org/show_bug.cgi?id=109515, comment #3 contains a patch for wxGTK ebuild that removes the dependency on X.

== Methods of Installation ==
=== amule-2.1.3.ebuild ===
This ebuild matches the most current, stable [[aMule]] release, it is available 13.10.2007 in portage.

Dependencies: >=x11-libs/wxGTK-2.6.*; >=sys-libs/zlib-1.2.1; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support.

=== amule-cvs ===
This ebuild is marked as '''unstable''' for all architectures.

Not intended for the general public. If you'd like to test out the daily development snapshot, then this is the version for you.

Dependencies: >=x11-libs/wxGTK-2.6.* or 2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/gd-2.0.26; >=media-libs/libpng-1.2.0; devs-libs/geoip 
Status: In development; 2 versions in portage; the latest tarball need a personal portage overlay

== Installation instructions ==
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule CVS (portage) ===
Portage have 2 CVS ebuilds: amule-2.2.0_pre20070422.ebuild with wXgtk-2.6 support and amule-2.2.0_pre20071204.ebuild with wXgtk-2.8 support. Both are marked as '''unstable''' for all architectures.

====To install amule-2.2.0_pre20070422:====

1. Add to ''package.keywords'':
echo "net-p2p/amule ~x86" >> /etc/portage/package.keywords

2. Review installation flags:
emerge amule -pv

3. Modify ''/etc/portage/package.use'' to suit your needs :
net-p2p/amule -amuled -debug 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 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

Personally, I have the unicode USE flag in /etc/make.conf so that any program that support unicode will be compiled with unicode support.

4. Install [[aMule]]:
emerge amule

====To install amule-2.2.0_pre-20071204,====
we need to unmask wXgtk-2.8. Process like for amule-2.2.0_pre20070422, but with this supplementary step:

1. Unmask amule-2.2.0_pre-20071204 and wXgtk-2.8
echo "=net-p2p/amule-2.2.0_pre20071204" >> /etc/portage/package.unmask
echo "=x11-libs/wxGTK-2.8.7.1" >> /etc/portage/package.unmask

=== amule CVS (latest one) ===
It is no ebuild for the current [[aMule CVS]] 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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

We will also follow the naming scheme of portage. CVS ebuild from a CVS tarball are not named as '''package_name-cvs''' but as '''package_name-version_date_of_the_tarball'''. That is to distinguish them from real CVS ebuilds (the so called live ebuilds) named as '''package_name-9999''' and using keywords="".

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-cvs:
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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-cvs"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/cvs/${MY_PN}-CVS-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

8. 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 X amuled -debug geoip gtk nls -nosystray -optimize remote remote-gui -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

9. Install [[aMule CVS]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2007-12-23T21:40:09Z

Libre:

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

English version updated: 23.12.2007 - Newest Gentoo Version are now 2.1.3 as well as 2 CVS versions.

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[wxGTK]] you decide to use...

Also, if you plan to build a GUI-less core, you might want to take a look at http://bugs.gentoo.org/show_bug.cgi?id=109515, comment #3 contains a patch for wxGTK ebuild that removes the dependency on X.

== Methods of Installation ==
=== amule-2.1.3.ebuild ===
This ebuild matches the most current, stable [[aMule]] release, it is available 13.10.2007 in portage.

Dependencies: >=x11-libs/wxGTK-2.6.*; >=sys-libs/zlib-1.2.1; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support.

=== amule-cvs ===
This ebuild is marked as '''unstable''' for all architectures.

Not intended for the general public. If you'd like to test out the daily development snapshot, then this is the version for you.

Dependencies: >=x11-libs/wxGTK-2.6.* or 2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/gd-2.0.26; >=media-libs/libpng-1.2.0; devs-libs/geoip 
Status: In development; 2 versions in portage; the latest tarball need a personal portage overlay

== Installation instructions ==
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule CVS (portage) ===
Portage have 2 CVS ebuilds: amule-2.2.0_pre20070422.ebuild with wXgtk-2.6 support and amule-2.2.0_pre20071204.ebuild with wXgtk-2.8 support. Both are marked as '''unstable''' for all architectures.

====To install amule-2.2.0_pre20070422:====

1. Add to ''package.keywords'':
echo "net-p2p/amule ~x86" >> /etc/portage/package.keywords

2. Review installation flags:
emerge amule -pv

3. Modify ''/etc/portage/package.use'' to suit your needs :
net-p2p/amule -amuled -debug 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 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

Personally, I have the unicode USE flag in /etc/make.conf so that any program that support unicode will be compiled with unicode support.

4. Install [[aMule]]:
emerge amule

====To install amule-2.2.0_pre-20071204,====
we need to unmask wXgtk-2.8. Process like for amule-2.2.0_pre20070422, but with this supplementary step:

1. Unmask amule-2.2.0_pre-20071204 and wXgtk-2.8
echo "=net-p2p/amule-2.2.0_pre20071204" >> /etc/portage/package.unmask
echo "=x11-libs/wxGTK-2.8.7.1" >> /etc/portage/package.unmask

=== amule CVS (latest one) ===
It is no ebuild for the current [[aMule CVS]] 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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

We will also follow the naming scheme of portage. CVS ebuild from a CVS tarball are not named as '''package_name-cvs''' but as '''package_name-version_date_of_the_tarball'''. That is to distinguish them from real CVS ebuilds (the so called live ebuilds) named as '''package_name-9999''' and using keywords="".

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-cvs:
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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-cvs"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/cvs/${MY_PN}-CVS-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

8. 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 X amuled -debug geoip gtk nls -nosystray -optimize remote remote-gui -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

9. Install [[aMule CVS]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2007-12-23T21:38:11Z

Libre: /* amule CVS */

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

<h1>Someone should check how recent this Article is, and update it for 2.1.3 or better 2.2.0</h1>

English version updated: 24.10.2006 - Newest Gentoo Version is now 2.1.2

== Introduction ==
Gentoo is known for choices. Unfortunately, some choices require more labor than others. As such, [[aMule]] comes in a variety of versions and installation methods based on what version of [[wxGTK]] you decide to use...

Also, if you plan to build a GUI-less core, you might want to take a look at http://bugs.gentoo.org/show_bug.cgi?id=109515, comment #3 contains a patch for wxGTK ebuild that removes the dependency on X.

== Methods of Installation ==
=== amule-2.1.3.ebuild ===
This ebuild matches the most current, stable [[aMule]] release, it is available 13.10.2007 in portage.

Dependencies: >=x11-libs/wxGTK-2.6.*; >=sys-libs/zlib-1.2.1; >=media-libs/libpng-1.2.0 for remote support; >=media-libs/gd-2.0.26 for unicode support.

=== amule-cvs ===
This ebuild is marked as '''unstable''' for all architectures.

Not intended for the general public. If you'd like to test out the daily development snapshot, then this is the version for you.

Dependencies: >=x11-libs/wxGTK-2.6.* or 2.8.*; >=sys-libs/zlib-1.2.1; >=media-libs/gd-2.0.26; >=media-libs/libpng-1.2.0; devs-libs/geoip 
Status: In development; 2 versions in portage; the latest tarball need a personal portage overlay

== Installation instructions ==
=== amule-2.1.3.ebuild ===
1. Emerge package:
emerge --sync
emerge amule -pv
emerge amule

=== amule CVS (portage) ===
Portage have 2 CVS ebuilds: amule-2.2.0_pre20070422.ebuild with wXgtk-2.6 support and amule-2.2.0_pre20071204.ebuild with wXgtk-2.8 support. Both are marked as '''unstable''' for all architectures.

====To install amule-2.2.0_pre20070422:====

1. Add to ''package.keywords'':
echo "net-p2p/amule ~x86" >> /etc/portage/package.keywords

2. Review installation flags:
emerge amule -pv

3. Modify ''/etc/portage/package.use'' to suit your needs :
net-p2p/amule -amuled -debug 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 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

Personally, I have the unicode USE flag in /etc/make.conf so that any program that support unicode will be compiled with unicode support.

4. Install [[aMule]]:
emerge amule

====To install amule-2.2.0_pre-20071204,====
we need to unmask wXgtk-2.8. Process like for amule-2.2.0_pre20070422, but with this supplementary step:

1. Unmask amule-2.2.0_pre-20071204 and wXgtk-2.8
echo "=net-p2p/amule-2.2.0_pre20071204" >> /etc/portage/package.unmask
echo "=x11-libs/wxGTK-2.8.7.1" >> /etc/portage/package.unmask

=== amule CVS (latest one) ===
It is no ebuild for the current [[aMule CVS]] 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://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds HOWTO Installing 3rd Party Ebuilds]

We will also follow the naming scheme of portage. CVS ebuild from a CVS tarball are not named as '''package_name-cvs''' but as '''package_name-version_date_of_the_tarball'''. That is to distinguish them from real CVS ebuilds (the so called live ebuilds) named as '''package_name-9999''' and using keywords="".

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-cvs:
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-2.2.0_p20071217.ebuild''

I use here the tarball from 17 December 2007 that was working fine for me, but you can change the date like you want. I use '''p''' in order to distinguish this ebuild from the ones in portage (using '''pre''').

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

inherit eutils flag-o-matic wxwidgets

MY_PN=${PN/m/M}
MY_PV="${PV/2.2.0_p/}"
S="${WORKDIR}/amule-cvs"

DESCRIPTION="aMule, the all-platform eMule p2p client"
HOMEPAGE="http://www.amule.org/"
SRC_URI="http://www.hirnriss.net/files/cvs/${MY_PN}-CVS-${MY_PV}.tar.bz2"

RESTRICT="nomirror"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~hppa ~ppc ~ppc64 ~sparc ~x86"
IUSE="amuled debug geoip gtk nls remote stats unicode"

DEPEND="=x11-libs/wxGTK-2.8*
>=sys-libs/zlib-1.2.1
stats? ( >=media-libs/gd-2.0.26 )
geoip? ( dev-libs/geoip )
remote? ( >=media-libs/libpng-1.2.0
unicode? ( >=media-libs/gd-2.0.26 ) )"

pkg_setup() {
if ! use gtk && ! use remote && ! use amuled; then
eerror ""
eerror "You have to specify at least one of gtk, remote or amuled"
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

if use stats && ! built_with_use media-libs/gd jpeg; then
die "media-libs/gd should be compiled with the jpeg use flag when you have the stats use flag set"
fi
}

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

src_compile() {
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} \
--with-wxbase-config=${WX_CONFIG} \
--enable-amulecmd \
$(use_enable debug) \
$(use_enable !debug optimize) \
$(use_enable amuled amule-daemon) \
$(use_enable geoip) \
$(use_enable nls) \
$(use_enable remote webserver) \
$(use_enable stats cas) \
$(use_enable stats alcc) \
${myconf} || die

# we filter ssp until bug #74457 is closed to build on hardened
filter-flags -fstack-protector -fstack-protector-all

emake -j1 || die
}

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

if use amuled; 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. Digest the ebuild:
ebuild amule-2.2.0_p10071217.ebuild digest

7. Review installation flags:
emerge amule -pv

8. 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 X amuled -debug geoip gtk nls -nosystray -optimize remote remote-gui -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

9. Install [[aMule CVS]]:
emerge amule

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

== aMule 2.1.1 Compilation FAQ ==
When compiling aMule-2.1.1 on a hardened system with gcc-3.4.5(at least), it will fail with something like:
WebServer.h: In member function `T* UpdatableItemsContainer<T, G, I>::GetByID(I) [with T = SharedFile, G = CEC_SharedFile_Tag, I = CMD4Hash]':
WebServer.h:270: internal compiler error: in sweep_string_variable, at protector.c:1158

The possible problem is the -fPIE CFLAG because using `gcc-config` to select ''i386-pc-linux-gnu-3.4.5-hardenednopiessp'' fixed the problem, and you can even remove from the ebuild:
if has_hardened; then
filter-flags -fstack-protector -fstack-protector-all
fi

You can read more on the subject following the link http://bugs.gentoo.org/show_bug.cgi?id=74457

HowTo Compile In Gentoo

2007-12-23T20:08:55Z

Libre: /* amule-cvs */

HowTo Compile In Gentoo

2007-12-23T20:08:25Z

Libre: /* amule-cvs */