On Wed, Apr 09, 2008 at 08:29:17AM +0200, Mike Hommey wrote: > On Wed, Apr 09, 2008 at 01:35:06AM +0300, Riku Voipio wrote: > > on arm EABI, wchar_t is "unsigned int", while -fshort-wchar enforces > > "short unsigned int". One is creating code that is incompatible with > > platform ABI, which the linker refuses to mix.
> Is arm EABI the only ABI with such incompatibility ? Good question. All other our archs seem to define wchar_t as int, while on arm it's unsigned int. Handling signed values on arm is slower than unsigned and negative values for wchar_t make little point. The gcc manpage seems to indicate that -fshort-wchar creates ABI incompatability, and is only usefull for wine programming (since windowsen wchar_t is unsigned short). Why in practice it's only causing problems on arm eabi with gcc >= 4.3 is weird. > PS: I wonder if gcc shouldn't dump -fshort-wchar in such situation. The > option doesn't make sense if it will always lead to this error. Theoretically it is valid option on arm eabi too, if you are not linking against the system libraries (building kernel, bootloader or static binaries with your own libc-like functionality ). -- "rm -rf" only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
