This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug ports/15505] ARM glibc missing __aeabi_ctype_table_C and __aeabi_ctype_table_
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 31 May 2013 19:24:01 +0000
- Subject: [Bug ports/15505] ARM glibc missing __aeabi_ctype_table_C and __aeabi_ctype_table_
- Auto-submitted: auto-generated
- References: <bug-15505-131 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15505
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The point of the CLIBABI symbols (such as the ones in this bug report) is
to support .o files that can be used with more than one C library
implementation. The glibc headers can't be used to compile such objects,
but given objects built with C library headers that support
_AEABI_PORTABILITY_LEVEL != 0, it should be possible to link those objects
with glibc and have the code work as expected.
The symbols intended for compiler rather than library portability of .o
files are generally those defined in RTABI; most of those are in libgcc,
with only a few such as __aeabi_memcpy* and __aeabi_read_tp being in
glibc.
--
You are receiving this mail because:
You are on the CC list for the bug.