Anonymous | Login | Signup for a new account | 2024-12-01 19:30 CET |
My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0001289 | aMule | Misc | public | 2008-03-20 14:11 | 2008-03-29 18:08 | ||||
Reporter | pva0xd | ||||||||
Assigned To | GonoszTopi | ||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0001289: amule fails to build on non glibc systems (e.g. uclibc) | ||||||||
Description | 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 `/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. | ||||||||
Tags | No tags attached. | ||||||||
Fixed in Revision | |||||||||
Operating System | Gentoo Linux | ||||||||
Attached Files | wxPython-src-2.8.7.1.m4 [^] (1,442 bytes) 2008-03-20 14:11 | ||||||||
Issue History | |||
Date Modified | Username | Field | Change |
2008-03-20 14:11 | pva0xd | New Issue | |
2008-03-20 14:11 | pva0xd | File Added: wxPython-src-2.8.7.1.m4 | |
2008-03-20 14:11 | pva0xd | Operating System | => Gentoo Linux |
2008-03-29 18:08 | GonoszTopi | Status | new => resolved |
2008-03-29 18:08 | GonoszTopi | Resolution | open => fixed |
2008-03-29 18:08 | GonoszTopi | Assigned To | => GonoszTopi |
Copyright © 2000 - 2024 MantisBT Team |