| Summary: | emerge xmule 1.6.1 fails with compile error | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Bjarke Freund-Hansen <gentoo-bugs> |
| Component: | Current packages | Assignee: | Rainer Größlinger (RETIRED) <scandium> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 31264 | ||
| Bug Blocks: | |||
| Attachments: | complete emerge xmule output | ||
|
Description
Bjarke Freund-Hansen
2003-10-18 14:24:32 UTC
Created attachment 19427 [details]
complete emerge xmule output
I think I figured out what causes this error. gtk2+unicode support was enabled again in the wxGTK-2.4.2 ebuild, it seems like you linked against Gtk+-2 and did you also enable unicode ? That is known to cause problems with poorly implemented wxWindows apps like xmule and amule are that don't follow the wx guidelines for unicode support. So, if you compiled wxGTK with +unicode try again with -unicode as a work around if you don't need unicode I just checked in a check function in all xmule and amule ebuilds, please test it I've just reemerged wxGTK without unicode support, and xmule compiles against it perfectly. Unfortunatly we cannot do anything about it, it's the developers job to fix unicode support in their application, so you have to live with that work-around. I added a check function to the ebuilds wether wxGTK was compiled with unicode support and there is nothing more we can do about this at the moment. resolved / fixed |