RFC: __x() functions and gcc

[Peter S. Mazinger]

On Fri, 3 Mar 2006, Khem Raj wrote:

> 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.

libc.so has to export them as __x so that libstdc++ can see them. I think 
that libstdc++ should behave like any other ordinary lib and use the normal 
symbols e.g. w/o __

(nl_langinfo_l/strxfrm/strcoll...)

Peter

> > 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
> >
> >   
> 
> 

-- 
Peter S. Mazinger <ps dot m at gmx dot net>           ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08  BB6E C389 975E A5F0 59F2