RFC: __x() functions and gcc

[Khem Raj]

Peter S. Mazinger said the following on 03/03/2006 12:45 PM:
> Hello!
>
> I have removed from uClibc svn (almost) all __x() functions. This results 
> in gcc failing to build libstdc++ if UCLIBC_HAS_XLOCALE is enabled.
>   
usually __ is good for internal symbols. What is the motivation to 
change it.
> There are 2 ways to solve this:
> 1. redo all the gcc patches in buildroot to use x() instead of __x() (__x 
> being considered internal for libc)
> 2. readd __x() to libc (visible), pollution
>
> Note: 1. does not need changes to uClibc-0.9.28 (stable)
>
> Votes?
>
> Thanks, Peter
>
>