On Thu, 7 Apr 2011, Henderson, Stuart wrote: > The originally suggested fix is very messy and Bernd suggests the fix > should be made in uClibc, which I agree with. However I'm not sure what > the best way to do it is. Will simply disabling this enum when > IN_LIBGCC2 be sufficient?
It is quite clear to me that this is a bug in GCC (namely, that this sort of host-side definition shouldn't be used in target-side code; ideally tm.h shouldn't be used in target-side code at all, though you've got over 80 target macros listed on <http://gcc.gnu.org/wiki/Top-Level_Libgcc_Migration> to deal with to achieve that). Maybe a fix in uClibc is more pragmatic, but definitely not one with a condition on IN_LIBGCC2, since IN_LIBGCC2 is part of the user's namespace so installed system headers should not use it in any way. -- Joseph S. Myers [email protected] _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
