aMule Bug Tracker - aMule
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
`/var/tmp/portage/amule-2.1.3/work/aMule-2.1.3/src/libs/common'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/amule-2.1.3/work/aMule-2.1.3/src/libs'
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 bugs.gentoo.org/146693 :
"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 configure.in 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.
wxPython-src-2.8.7.1.m4 (1,442) 2008-03-20 14:11https://bugs.amule.org/file_download.php?file_id=232&type=bug