Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Arichy]

Just interested: what compiler options where used to compile the debian sarge packages on amule-debian.dyndns.org ?

Greets, Arichy

[Gerd78]

There must be a source package. Look at the file "debian/rules" in that source package.

[Arichy]

oh, I made a mistake:
I wanted to ask, what configure options for compiling amule where used, not compiler options.

[Vollstrecker]

And jep, you would get the same answer.

[thedude0001]

...And all the answers would be wrong as there is no source package. Why? Basically because I didn't think anybody would need it and because dpkg-scansources wouldn't work for me for some reason and nobody pestered me into looking into it ^^

Back to the original question:

./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --enable-debug --enable-amule-daemon --enable-amulecmd --enable-webserver --enable-cas --enable-wxcas --enable-alc --enable-alcc --enable-amule-gui --enable-ccache

That's the configure line I use on those packages. Any special reason you're asking or is it just out of curiosity? ^^


P.S.:
Before telling people "Don't bother people in here with questions you can find the answers to at xyz" you should be sure that the answers really are there

[Arichy]

Because it runs awfully slow. I think --disable-debug and --enable-optimize make amule run faster. I need a slim and fast amule because I am running it on a Pentium 166 MMX under vncserver (do not like fizzling with half functioning amule-gui etc.). So I used Your wx*-dev-Packages and compiled amule yesterday for my own. But now it crashed. So the --enable-debug option maybe right: I think 2.1.0 is just Alpha Status (sorry, if I am false), so there are some better backtraces.

[thedude0001]

Well, definitely not alpha status, it's what we call "ready for release" ^^
There are always bugs in such a large project, you won't find any non-trivial pogram without bugs. And that's why I compiled the packages with --enable-debug (and that's why this is the default on amule compilation)...

[stefanero]

@Arichy maybe you just uses some wrong flags for compiling...

if amule would be alpha status, I think there would be more then just 4-5 bug reports...and half of them belong to amule-gui who is noone working on atm

[thedude0001]

Humm, amule running on a P-166 with a full blown X Server and vncserver... I think that's where you get your speed problems. Yes, we've had reports of amule running on a P166, but that was amuled, without X...

[Arichy]

Originally posted by thedude0001
Humm, amule running on a P-166 with a full blown X Server and vncserver... I think that's where you get your speed problems. Yes, we've had reports of amule running on a P166, but that was amuled, without X...

2.0.3 run fine and very stable all the time that way. By the way, I nevertheless tried Your amule binary and wx* but it crashed after some hours:

Code: [Select]

Error on CKademliaUDPListener::processPublishRequest received from: 229.129.201.86:4672
No ip match

(amule:13267): GLib-WARNING **: giounix.c:400Error while getting flags for FD: Ungültiger Dateid
eskriptor (9)


--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    [URL]http://forum.amule.org/board.php?boardid=67[/URL]
    If possible, please try to generate a real backtrace of this crash:
        [URL]http://www.amule.org/wiki/index.php/Backtraces[/URL]

        ----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
        Current version is: aMule 2.1.0 using wxGTK2 v2.6.2 (Unicoded)
        Running on: Linux 2.4.27-2-386 i586

        [2] ?? in amule [0x8075881]
        [3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.6.so.0[0x406ba278]
        [4] ?? in /lib/libpthread.so.0 [0x4002a825]
        [5] ?? in /lib/libc.so.6 [0x408366f8]
        [6] ?? in /usr/lib/libgdk-x11-2.0.so.0 [0x40c3a6ab]
        [7] ?? in /usr/lib/libglib-2.0.so.0 [0x40da7dbf]
        [8] ?? in /usr/lib/libglib-2.0.so.0 [0x40d82582]
        [9] g_main_context_dispatch in /usr/lib/libglib-2.0.so.0[0x40d835f8]
        [10] ?? in /usr/lib/libglib-2.0.so.0 [0x40d83930]
        [11] g_main_loop_run in /usr/lib/libglib-2.0.so.0[0x40d83ed3]
        [12] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0x40a62bb3]
        [13] wxEventLoop::Run() in /usr/lib/libwx_gtk2u_core-2.6.so.0[0x402f9e88]
        [14] wxAppBase::MainLoop() in /usr/lib/libwx_gtk2u_core-2.6.so.0[0x4038f073]
        [15] wxAppBase::OnRun() in /usr/lib/libwx_gtk2u_core-2.6.so.0[0x4038f1da]
        [16] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.6.so.0[0x4064901e]
        [17] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.6.so.0[0x4064911d]
        [18] ?? in amule [0x8155b20]
        [19] __libc_start_main in /lib/libc.so.6[0x40822e36]
        [20] ?? in amule [0x806ae41]


--------------------------------------------------------------------------------
Abgebrochen


[thedude0001]

Well, Kad was added which can take quite some CPU time...

Please post your crash reports on the crash forum since they are likely not to be specific to my packages, and most devs don't read the threads in here...