aMule Forum
English => aMule News => Topic started by: Kry on December 17, 2006, 10:45:59 PM
-
While we work on 2.2.0 (which is cooking, and I might repeat an odd release day from the old times), HERE (http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/aMule-wx.patch?rev=1.2) you have a patch to build aMule 2.1.3 against new wxWidgets 2.8.0 (thanks to arekm (http://mailto:arekm@pld-linux.org) on IRC).
wxWidgets 2.8.0 is now the new stable wxWidgets, our recomended version is now that one, and support for wxWidgets < 2.8.0 will be dropped from our forums very soon. As in, right now. Right now pleases me.
Remember that the "crash on search tab close" is an wxWidgets bug, not an aMule bug, and it's fixed on the 2.8.0 version. Every thread refering to that bug from now on will be closed, and so will bug reports, without any further info. I'm sorry, but I saw that "bug" report one too many times ;) I must remind you guys to do search on forum and tracker before posting to avoid such things to happen. We encourage bug reports, and we thank you for it, but please check for duplicates.
See, I still make posts with a lot of text, where the main news are lost somewhere in very little words.
-
But with the 2.1.3 patch it also continue to work with wxwidgets 2.6.x or not?
-
Of course. But you don't need it if you use 2.6.x.
-
Use the utiliy 'patch'.
example usage: patch < diff.file
You might have to add the -p argument followed by a number, if you run the patch of a different directory. e.g. patch -p2 < diff.file
-
How I can compile WxWidgets with "base" tollkit? I'm running amuled on a Kurobox, a powerPc without monitor and I don't have (because I don't need) GTK.In the past, with versione 2.6.3 I download WxBase and running:
./configure --prefix=/usr --enable-unicode --disable-compat24 --enable-optimise
the configure automatically selects Base toolkit. Now with WxBase-2.8.0 the configure (uncorrectly) selects GTK toolkit returning in an error (missing GTK). Which is the ./configure parameter to enable Base toolkit? Bye!!!!
--edit--
Find, you should use --disable-gui. Do I need to use also --disable-compat26 (to disable 2.6.x compatibility)?
-
--disable-gui
-
Eh eh, sorry, cross "editing" :D. Thank you Kry!!!!
-
Any tentative release date for aMule 2.2.0 for Mac OS X? Thanks.
-
Maybe direct after the 2.2.0 for Linux.
-
Originally posted by Kry
While we work on 2.2.0 (which is cooking, and I might repeat an odd release day from the old times), HERE (http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/aMule-wx.patch?rev=1.2) you have a patch to build aMule 2.1.3 against new wxWidgets 2.8.0 (thanks to arekm (http://mailto:arekm@pld-linux.org) on IRC).
wxWidgets 2.8.0 is now the new stable wxWidgets, our recomended version is now that one, and support for wxWidgets < 2.8.0 will be dropped from our forums very soon. As in, right now. Right now pleases me.
Remember that the "crash on search tab close" is an wxWidgets bug, not an aMule bug, and it's fixed on the 2.8.0 version. Every thread refering to that bug from now on will be closed, and so will bug reports, without any further info. I'm sorry, but I saw that "bug" report one too many times ;) I must remind you guys to do search on forum and tracker before posting to avoid such things to happen. We encourage bug reports, and we thank you for it, but please check for duplicates.
See, I still make posts with a lot of text, where the main news are lost somewhere in very little words.
You said this about new WxWidgets... and now in my Amule statistics i only can see Amule 2.1.3 (95,65% users) and Amule 2.1.2 (4,35%). Does most of Amule users use Ubuntu? I think so, and this "post-tip"has helped a lot (including me to migrate form 2.1.0 to 2.1.3). Thanks Kry.
-
I think left support for 2.6 immediately is not a good idea, all distro uses wx 2.6 and you cannot think that all users compile by them self.
So be blind and think that all have 2.8 now, but it's not true.
-
Originally posted by Cimmo
I think left support for 2.6 immediately is not a good idea, all distro uses wx 2.6 and you cannot think that all users compile by them self.
So be blind and think that all have 2.8 now, but it's not true.
Ok. Then we'll take the blame for the distro not updating it, and face the bugs that are not caused by aMule, and... do nothing about it. Because we can't.
If your distro doesn't update to the new stable wxWidgets, you can still use aMule with no problem, we're not removing wxWidgets 2.6 compatibility. We're, however, only taking bug reports coming from wxWidgets 2.8. For obvious reasons.
-
Sorry for asking this if it is already answered, but I cannot find the response.
Will protocol obfuscation be included in 2.2.0?
-
Yes, according to this thread (http://forum.amule.org/thread.php?threadid=11925)
-
Originally posted by wuischke
Use the utiliy 'patch'.
example usage: patch < diff.file
You might have to add the -p argument followed by a number, if you run the patch of a different directory. e.g. patch -p2 < diff.file
Given, I put the patch file in the aMule-2.1.3 source directory. What command do I have to enter when I changed to that directory?
EDIT: I tried "patch -p1 < ./file.patch". That seemed to work:
patching file src/utils/wxCas/src/wxcasprefs.cpp
patching file src/utils/wxCas/src/wxcasprefs.h
patching file src/MuleGifCtrl.cpp
patching file src/MuleGifCtrl.h
patching file src/MuleTextCtrl.cpp
patching file src/amule.cpp
Hunk #1 succeeded at 97 (offset 1 line).
then configuring with "./configure --disable-debug --enable-optimize --disable-ed2k" and make (with installed wxgtk 2.8.0 on debian sarge) results in:
/usr/include/wx-2.8/wx/gdicmn.h:486: Warnung: declaration of `x' shadows a
member of `this'
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BI
TS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -D__WXGTK__ -pthread -I./libs -DUSE_EMBEDDED_CRYPTO -W -Wall -Wshadow -Wundef -O2
-MT libmuleappgui_a-listctrl.o -MD -MP -MF ".deps/libmuleappgui_a-listctrl.Tpo" -c -o libmuleappgui_a-listctrl.o `test -f 'l
istctrl.cpp' || echo './'`listctrl.cpp; \
then mv -f ".deps/libmuleappgui_a-listctrl.Tpo" ".deps/libmuleappgui_a-listctrl.Po"; else rm -f ".deps/libmuleappgui_a-listct
rl.Tpo"; exit 1; fi
In file included from /usr/include/wx-2.8/wx/event.h:21,
from /usr/include/wx-2.8/wx/app.h:20,
from extern/listctrl.262.cpp:36,
from listctrl.cpp:4:
/usr/include/wx-2.8/wx/gdicmn.h: In member function `bool wxRect::Inside(int,
int) const':
/usr/include/wx-2.8/wx/gdicmn.h:486: Warnung: declaration of `y' shadows a
member of `this'
/usr/include/wx-2.8/wx/gdicmn.h:486: Warnung: declaration of `x' shadows a
member of `this'
In file included from listctrl.cpp:4:
extern/listctrl.262.cpp: In member function `int
MuleExtern::wxListLineDataArray::Index(const
MuleExtern::_wxObjArraywxListLineDataArray&, bool) const':
extern/listctrl.262.cpp:375: Warnung: declaration of `Item' shadows a member of
`this'
In file included from listctrl.cpp:4:
extern/listctrl.262.cpp: In member function `bool
MuleExtern::wxListItemData::IsHit(int, int) const':
extern/listctrl.262.cpp:925: Warnung: `Inside' is deprecated (declared at
/usr/include/wx-2.8/wx/gdicmn.h:486)
In file included from listctrl.cpp:4:
extern/listctrl.262.cpp: In member function `void
MuleExtern::wxListHeaderWindow::OnPaint(wxPaintEvent&)':
extern/listctrl.262.cpp:1703: Warnung: `BeginDrawing' is deprecated (declared
at /usr/include/wx-2.8/wx/dc.h:392)
extern/listctrl.262.cpp:1818: Warnung: `EndDrawing' is deprecated (declared at
/usr/include/wx-2.8/wx/dc.h:393)
In file included from listctrl.cpp:4:
extern/listctrl.262.cpp: In member function `long int
MuleExtern::wxListMainWindow::HitTestLine(unsigned int, int, int) const':
extern/listctrl.262.cpp:2374: Warnung: `Inside' is deprecated (declared at
/usr/include/wx-2.8/wx/gdicmn.h:486)
extern/listctrl.262.cpp:2385: Warnung: `Inside' is deprecated (declared at
/usr/include/wx-2.8/wx/gdicmn.h:486)
In file included from listctrl.cpp:4:
extern/listctrl.262.cpp: In member function `void
MuleExtern::wxListMainWindow::OnPaint(wxPaintEvent&)':
extern/listctrl.262.cpp:2623: Warnung: `BeginDrawing' is deprecated (declared
at /usr/include/wx-2.8/wx/dc.h:392)
extern/listctrl.262.cpp:2811: Warnung: `EndDrawing' is deprecated (declared at
/usr/include/wx-2.8/wx/dc.h:393)
In file included from listctrl.cpp:4:
extern/listctrl.262.cpp: In member function `bool
MuleExtern::wxGenericListCtrl::Create(wxWindow*, int, const wxPoint&, const
wxSize&, long int, const wxValidator&, const wxString&)':
extern/listctrl.262.cpp:4889: Warnung: `SetBestSize' is deprecated (declared at
/usr/include/wx-2.8/wx/window.h:1415)
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BI
TS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -D__WXGTK__ -pthread -I./libs -DUSE_EMBEDDED_CRYPTO -W -Wall -Wshadow -Wundef -O2
-MT libmuleappgui_a-MuleGifCtrl.o -MD -MP -MF ".deps/libmuleappgui_a-MuleGifCtrl.Tpo" -c -o libmuleappgui_a-MuleGifCtrl.o `t
est -f 'MuleGifCtrl.cpp' || echo './'`MuleGifCtrl.cpp; \
then mv -f ".deps/libmuleappgui_a-MuleGifCtrl.Tpo" ".deps/libmuleappgui_a-MuleGifCtrl.Po"; else rm -f ".deps/libmuleappgui_a-
MuleGifCtrl.Tpo"; exit 1; fi
In file included from /usr/include/wx-2.8/wx/image.h:19,
from /usr/include/wx-2.8/wx/gifdecod.h:19,
from MuleGifCtrl.cpp:26:
/usr/include/wx-2.8/wx/gdicmn.h: In member function `bool wxRect::Inside(int,
int) const':
/usr/include/wx-2.8/wx/gdicmn.h:486: Warnung: declaration of `y' shadows a
member of `this'
/usr/include/wx-2.8/wx/gdicmn.h:486: Warnung: declaration of `x' shadows a
member of `this'
MuleGifCtrl.cpp: At global scope:
MuleGifCtrl.cpp:69: error: 'uint32_t' is used as a type, but is not defined as
a type.
MuleGifCtrl.cpp: In constructor `MuleGIFDecoder::MuleGIFDecoder(wxInputStream*,
bool)':
MuleGifCtrl.cpp:45: error: `m_nframe' undeclared (first use this function)
MuleGifCtrl.cpp:45: error: (Each undeclared identifier is reported only once
for each function it appears in.)
make[3]: *** [libmuleappgui_a-MuleGifCtrl.o] Fehler 1
make[3]: Leaving directory `/daten/bauen/amule_compile/aMule-2.1.3/src'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/daten/bauen/amule_compile/aMule-2.1.3/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/daten/bauen/amule_compile/aMule-2.1.3'
make: *** [all] Fehler 2
-
same here.
didn't tried the cvs yet; i'll rather wait 2.2, if it doesn't long too much.
-
> Will protocol obfuscation be included in 2.2.0?
Yes, according to this thread (http://forum.amule.org/thread.php?threadid=11925)
see here instead now:
http://forum.amule.org/index.php?topic=11627.msg61196#msg61196 (http://forum.amule.org/index.php?topic=11627.msg61196#msg61196)
-
Hi, what is the release date ( in forecast) for 2.2.0 version?
My ISP blocks P2P traffic and I don't want to use emule ( and windows )
-
there is no fixed release date. It's simply released when it's done. Or soon (TM). Whatever comes first. But I think the release date of 2.2.0 is pretty close, since Kry has already advanced a lot in the implementation of PO. We just have to wait :)
Regards.
-
Thanks. I know that developers are working at the best of their possibilities and I'm pleasing to them for their work..
P.S:In the latest cvs-tarball PO is in testing ?
-
Uhm, actually Kry was on vacation and I doubt he wrote a single line of code. ;)
PO is partly implemented since 2007/05/22 and afaik there are no further commits regarding PO. There's no active testing necessary, but feel free to play around.
-
So when we could expect the new aMule version to be released???
-
There is no fixed release date. It's simply released when it's done. Or soon (TM). Whatever comes first.
This pretty much sums it up. (No, we are not happy about it either.)
There are some bugs preventing the release of 2.2.0, but due to personal reasons we currently lack the necessary skilled developers to fix them.
-
What are the bugs? I think it would be a nice idea if we used a trac system like Transmission does. It's easy to see what's wrong, and what is being worked on.
-
We do have a bug tracker for this purpose, even though our development process is not that well organized as with a trac system. At least the developers know usually what's not working as it should.
-
This pretty much sums it up. (No, we are not happy about it either.)
More or less maybe?
-
74 years, 6 months, 3 weeks, 5 days, 13 hours, 1 minute and 37 seconds.
-
Can you speed that up some minutes. At this time I'm on the toilette and I don't want to miss that moment.
-
I'm still unhappy with the 2.2.0 CVS at the moment to be honest..
There still are some very nasty bugs that need to be solved with the integration of amuleweb and the daemon. For example,
* From the docs i read, you can only connect to KAD if you manually click on the Connect button (instead of, say, double clicking on a server or whatever). This cannot be done through amuleweb.. I haven't found a way through amuleweb to do so.
* Clicking on the Connect button from amulegui doesn't work.
* amulecmd also doesn't seem to connect properly.
* amuleweb shows KAD as one state, while amulecmd shows it as another state, while amule shows it as a third state.. which is it? connected? disconnected? firewalled?
* amuleweb is really weird when it comes to connecting to Servers.. It's too fast, doesn't give you a good log, and hardly ever connects, while you can connect in seconds through aMule.
* I still can't search.. Searching through amuleweb gives no results. Searching through amule sometimes gives results. I'm not sure if this is a server thing or not.. but i always search on Global.
* I still get amuleweb segfaults on amd64 using it.
This is what i can remember from the top of my head. I hope it helps.
As soon as i get a new router that supports upnp and forwarding more than 10 ports, i'll get to testing aMule on OS X.
-
amulecmd also doesn't seem to connect properly.
I heard other reports.
amuleweb shows KAD as one state, while amulecmd shows it as another state, while amule shows it as a third state.. which is it? connected? disconnected? firewalled?
Not on my machine. Can you please be more specific? When this happen? What is correct state? What is reported where?
I still can't search.. Searching through amuleweb gives no results
Works fine for me.
amuleweb is really weird when it comes to connecting to Servers
I don't know what are you talking about.
I still get amuleweb segfaults on amd64 using it.
Not very informative. I can not test such thing since I don't have amd64, so please provide more info if you want see this fixed.
-
amulecmd also doesn't seem to connect properly.
I heard other reports.
amuleweb shows KAD as one state, while amulecmd shows it as another state, while amule shows it as a third state.. which is it? connected? disconnected? firewalled?
Not on my machine. Can you please be more specific? When this happen? What is correct state? What is reported where?
I still can't search.. Searching through amuleweb gives no results
Works fine for me.
amuleweb is really weird when it comes to connecting to Servers
I don't know what are you talking about.
I still get amuleweb segfaults on amd64 using it.
Not very informative. I can not test such thing since I don't have amd64, so please provide more info if you want see this fixed.
Sure thing. Yea i'll get you more information as soon as I have the time in the weekend. Maybe submit a bug report for each of the list above.
But there's one thing i'm having trouble with, and that's gathering debug info from gdb when amuleweb segfaults. If i run gdb on amuleweb itself, it does not get binded with amuled. If i run gdb on amuled, it does not detect or report anything when amuleweb crashes.
If you can give me a hand on this, i'll really appreciate it, and can offer a lot in terms of detailed bug reports.
Edit: lfroen, how about postponing this for a day or two, and I'll meet you on IRC where we can solve it more quickly ?
-
But there's one thing i'm having trouble with, and that's gathering debug info from gdb when amuleweb segfaults.
Enable core dumps, and create backtrace postmortem, i.e. by loading executable (amuleweb) and core dump into gdb and executing "bt"
lfroen, how about postponing this for a day or two, and I'll meet you on IRC where we can solve it more quickly ?
Postpone what? Unfortunately I can't get to IRC, but you can reach me by mail/PM/forum.
-
Postpone what? Unfortunately I can't get to IRC, but you can reach me by mail/PM/forum.
Postpone getting into the errors above.. And nevermind. I'll just start a new thread or PM you later :)
Thanks for the help.
-
Well, if you make detailed bug reports with enough information to reproduce these bugs, maybe we can help.
Cheers!
-
wxGTK2.8.6 can still use this patch ?
-
ok, applied the patch but while "make" i still get this error:
++ -DUSE_EMBEDDED_CRYPTO -W -Wall -Wshadow -Wundef -g -ggdb -fno-inline -D__DEBUG__ -fmessage-length=0 -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC -lpthread -o amule amule-AICHSyncThread.o amule-AddFileThread.o amule-amule.o amule-BaseClient.o amule-ClientList.o amule-ClientCreditsList.o amule-ClientTCPSocket.o amule-ClientUDPSocket.o amule-DownloadClient.o amule-DownloadQueue.o amule-EMSocket.o amule-ECSpecialCoreTags.o amule-ExternalConn.o amule-Friend.o amule-FriendList.o amule-HTTPDownload.o amule-IPFilter.o amule-KnownFileList.o amule-ListenSocket.o amule-MuleUDPSocket.o amule-SearchList.o amule-ServerConnect.o amule-ServerList.o amule-ServerSocket.o amule-ServerUDPSocket.o amule-SharedFileList.o amule-UploadBandwidthThrottler.o amule-UploadClient.o amule-UploadQueue.o amule-Kademlia.o amule-Search.o amule-Indexed.o amule-KademliaUDPListener.o amule-Prefs.o amule-RoutingZone.o amule-Contact.o amule-amule-gui.o amule-amuleDlg.o amule-AddFriend.o amule-ChatSelector.o amule-ClientDetailDialog.o amule-FileDetailDialog.o amule-KadDlg.o amule-OScopeCtrl.o amule-PartFileConvert.o amule-PrefsUnifiedDlg.o amule-SearchDlg.o amule-ServerWnd.o amule-SharedFilesWnd.o amule-StatisticsDlg.o amule-SearchListCtrl.o amule-DownloadListCtrl.o amule-ClientListCtrl.o amule-FriendListCtrl.o amule-ServerListCtrl.o amule-SharedFilesCtrl.o amule-MuleTrayIcon.o amule-TransferWnd.o amule-ClientCredits.o amule-ECSpecialMuleTags.o amule-KnownFile.o amule-GetTickCount.o amule-Logger.o amule-PartFile.o amule-Preferences.o amule-Proxy.o amule-Server.o amule-Statistics.o amule-StatTree.o amule-SHAHashSet.o amule-OtherFunctions.o -L. -lmuleappcommon -Llibs/common -Llibs/ec -lmulecommon -lec -lz -lbfd -liberty -L. -lmuleappcore -L. -lmuleappgui -pthread -L/usr/X11R6/lib -lwx_gtk2u_adv-2.8 -lwx_gtk2u_core-2.8 -lwx_baseu_net-2.8 -lwx_baseu-2.8
/usr/local/lib/librt.so.1: undefined reference to `__fortify_fail@GLIBC_PRIVATE'
collect2: ld returned 1 exit status
make[3]: *** [amule] Error 1
make[3]: Leaving directory `/home/kit/src/aMule-2.1.3/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/kit/src/aMule-2.1.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/kit/src/aMule-2.1.3'
make: *** [all] Error 2
I'm using slack 12.0
-
Use the utiliy 'patch'.
example usage: patch < diff.file
You might have to add the -p argument followed by a number, if you run the patch of a different directory. e.g. patch -p2 < diff.file
What I did was:
1. opened http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/aMule-wx.patch?rev=1.2
2. saved it as aMule-wx.patch into the directory where I unpacked aMule-2.1.3.tar.bz2 i.e. ...something/aMule-2.1.3
3. went to that directory and typed:
> patch -Np1 -i ./aMule-wx.patch
4. continued as usual, from that directory: > ./configure; make; su -c "make install"
and here's the result - latest released package (2.1.3) for openSUSE-10.3 :
http://rapidshare.com/files/103098841/aMule-2.1.3-1.zj.openSUSE10.3.i586.rpm