aMule Forum
English => Compilation problems => Topic started by: wootletootle on October 18, 2011, 12:15:06 PM
-
The ./configure script executes without error
Libraries aMule will use to build:
wxWidgets 2.8.12 (gtk2,shared)
crypto++ 5.6.1 (sources, in /usr/local/src/cryptopp561/)
libupnp 1.6.13
libintl system
zlib 1.2.3
but I get link errors beginning with
amule-CaptchaDialog.o: In function `wxStringBase':
/usr/local/include/wx-2.8/wx/string.h:368: undefined reference to `wxStringBase::InitWith(wchar_t const*, unsigned int, unsigned int)'
down to
./libmuleappgui.a(libmuleappgui_a-muuli_wdr.o):(.rodata._ZTV12wxSliderBase[vtable for wxSliderBase]+0x264): undefined reference to `wxWindow::ApplyToolTip(_GtkTooltips*, wchar_t const*)'
collect2: ld returned 1 exit status
make[2]: *** [amule] Error 1
make[1]: *** [install-recursive] Error 1
make: *** [install-recursive] Error 1
I installed both wxwidgets for both gtk+ and x11. Is it possible that the x11 install has overwritten the gtk+?
Thanks for your help.
-
Possibly. But it's also possible it's not compiled with unicode support.
-
Possibly. But it's also possible it's not compiled with unicode support.
Thanks for your response.
You mean wxWidgets/gtk+? Yes, it is. Here is the configuration summary:
Configured wxWidgets 2.8.12 for `i686-pc-linux-gnu'
Which GUI toolkit should wxWidgets use? GTK+ 2
Should wxWidgets be compiled into single library? no
Should wxWidgets be compiled in debug mode? no
Should wxWidgets be linked as a shared library? yes
Should wxWidgets be compiled in Unicode mode? yes
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.4 no
wxWidgets 2.6 yes
Which libraries should wxWidgets use?
jpeg sys
png sys
regex builtin
tiff sys
zlib sys
odbc no
expat sys
libmspack no
sdl no
Should I select "Single library"?
-
No, it's configured fine. Probably a mixup with the other wx installed.
Either you remove all other wxs so you have just one on your system,
or you configure aMule using --with-wxdir as described here (http://wiki.amule.org/index.php/HowTo_Compile_In_Ubuntu).
-
No, it's configured fine. Probably a mixup with the other wx installed.
Thanks for the advice. I removed wxX11 and did a careful re-install of wxgtk+.
Then aMule compilation succeeded.
I then ran into this aMule run-time error :
Assertion failed: must call CalculateSize() first
reported in this link
http://forum.amule.org/index.php?topic=18228.msg99468#msg99468
Recompilation of wxgtk+ without the debug option (as you suggested Stu)
cured this problem. :)
Thanks again.
Roger.
-
It's not technically a solution tho.
-
Well, technically it's not a solution. The question is just if the problem is severe enough to justify throwing assertions. Obviously not.
It's like the lot of GTK "assertions" printed in the console because some gui element is half hidden or something alike.
-
The problem IS a problem, just not an aMule problem. It's a wx bug that we trigger. Check 10629.