aMule Bug Tracker - aMule
View Issue Details
0001289aMuleMiscpublic2008-03-20 14:112008-03-29 18:08
Gentoo Linux
0001289: amule fails to build on non glibc systems (e.g. uclibc)
Attempt to build amule with non glibc (e.g. with uclibc) fails with errors like:

MuleDebug.cpp:36:23: execinfo.h: No such file or directory
MuleDebug.cpp: In function `wxString get_backtrace(unsigned int)':
MuleDebug.cpp:291: error: `backtrace' was not declared in this scope
MuleDebug.cpp:291: warning: unused variable 'backtrace'
MuleDebug.cpp:296: error: `backtrace_symbols' was not declared in this scope
MuleDebug.cpp:296: warning: unused variable 'backtrace_symbols'
make[4]: *** [libmulecommon_a-MuleDebug.o] Error 1
make[4]: Leaving directory
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/amule-2.1.3/work/aMule-2.1.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/amule-2.1.3/work/aMule-2.1.3'
make: *** [all] Error 2

This was build with uclibc, but similar problem is reported to exist on FreeBSD.

But as it was told by our base-sytem developer (and he is uclibc developer too) at :

"yeah, amule should make sure execinfo.h is provided and if not, stub out its backtrace calls ... those functions are a total GNUism"

Another possible solution is to disable debugging like wxGTK does (in attachment you'll find relevant code).

Yea, I know that such reports are looking better when patches are applied, but currently I don't have enough time to delve into code, so may be somebody else will look at this problem before...

Thank you for your time.
No tags attached.
? wxPython-src- (1,442) 2008-03-20 14:11
Issue History
2008-03-20 14:11pva0xdNew Issue
2008-03-20 14:11pva0xdFile Added: wxPython-src-
2008-03-20 14:11pva0xdOperating System => Gentoo Linux
2008-03-29 18:08GonoszTopiStatusnew => resolved
2008-03-29 18:08GonoszTopiResolutionopen => fixed
2008-03-29 18:08GonoszTopiAssigned To => GonoszTopi

There are no notes attached to this issue.