[uClibc]C++ support
spudmonkey at racsa.co.cr
spudmonkey at racsa.co.cr
Fri Apr 12 16:50:16 UTC 2002
Hello, again,
I would still like to get support for libstdc++ with uClibc. It hasn't
been my highest priority (it will be someday), but I've been looking
around little bit. And to me, the situation looks like:
1. libstdc++ is HUGE!
2. libstdc++ depends (among other things) on libio.a and libstream.a.
3. In gcc-2.95.3, if you build a *-linux-gnu target, it assumes that
these archives are not needed, rather, that libio.a and libstream.a
functionality will be provided by glibc.
4. If you muck with gcc-2.95.3's makefile fragments, you can coerce it
to (try to) build libio.a and libstream.a using the source under the
gcc/libio directory. But, the build fails because the glibc header
files are out of sync with the libio source code*. Furthermore, it
appears the libio code depends upon acess to glibc "back door"
functions (especially if you want multi-threaded support).
The gcc-2.95.3 libio also looks like it lacks large file support
(hence, most of the incompatibility with the header files).
[[ *I can actually get libio and libstream to build if I get the right
libio.h and libioP.h from the CVS attic. I needs versions that are
over 3 years old! ]]
5. In gcc-3.0.x, libio has been completely removed from the compiler
and is only availabe with glibc (Is this true?).
Finally, the question(s): Am I on track? Is this consistent with your
understanding? Has anyone put any effort into creating a uClibc aware
libio? Maybe a "uClibio?" Has anyone thought about a smaller
libstdc++? Would anyone be interested in collaborating in such efforts?
Thanks in advance,
Greg Nutt
More information about the uClibc
mailing list