Mr Faber,
amuled is relatively new code and is under heavy development. In fact, it needs a lot of testing and your feedback is fundamental to improove it.
If you must run the webserver, but can afford an X interface, amule can also handle this job. But of course, we wan't the daemon to become stable, so we need testing.
If you can keep providing us backtraces of the crashes, we can certainly make it better.
As for building wxGTK, I use to build my own, I don't use rpm nor emerge. Unpack it in a directory in your home and go to the root of the tar and do:
(for non-unicode debug build)
$ ./configure --enable-debug --disable-optimise --enable-debug_flag --enable-debug_info --enable-debug_gdb --enable-gtk2 --disable-unicode --prefix=~/usr/wxWidgets-cvs
(for unicode debug build)
$ ./configure --enable-debug --disable-optimise --enable-debug_flag --enable-debug_info --enable-debug_gdb --enable-gtk2 --enable-unicode --prefix=~/usr/wxWidgets-cvsu
configure aMule like this:
(for non-unicode debug build)
./configure --enable-debug --disable-optimize --enable-verbose --enable-webserver --enable-webservergui --enable-amulecmd --enable-amulecmdgui --enable-amule-daemon --enable-ccache --with-wx-config=~/usr/wxWidgets-cvs/bin/wx-config
(for unicode debug build)
$ ./configure --enable-debug --disable-optimize --enable-verbose --enable-webserver --enable-webservergui --enable-amulecmd --enable-amulecmdgui --enable-amule-daemon --enable-ccache --with-wx-config=~/usr/wxWidgets-cvsu/bin/wx-config
And run it like this:
(for non-unicode debug build)
LD_LIBRARY_PATH=~/usr/wxWidgets-cvs/lib/ /path/to/non-unicoded/amule&
(for unicode debug build)
LD_LIBRARY_PATH=~/usr/wxWidgets-cvsu/lib/ /path/to/unicoded/amule&
The advantage is that you can have many different wxGTK versions installed with different options, with many different aMule versions and options, and you don't have to do make install, so there is no need to be superuser.
Cheers!