[Bug c/14157] undefined reference to `__ctype_b' (can't compile gcc for avr using gcc3.3.3)

["cmosis5 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>]

------- Additional Comments From cmosis5 at hotmail dot com  2004-02-16 14:48 -------

Hi,
  Yes, it appears that applications should NOT be using this __ctype_b, and thus
REDHAT isn't supporting it anymore with their glibc libraries. 

So should gcc avoid this?


What's the status on this? Why has Red Hat suddenly changed this in Red Hat 9
between glibc-2.3.2-5 and glibc-2.3.2-11.9? And will Red Hat exports __ctype_b
as compatibility symbol again?

Or should I open a new ticket?

Werner


------- Additional Comment #6 From Michael Young on 2003-06-20 17:19 -------

I am sure I have seen the answer to this query elsewhere in bugzilla. The
reasoning (if I remember correctly) is that the __ctype_b isn't safe in the TLS
environment, so they removed it to discourage people from using it. Hence don't
expect it to reappear, though it is apparently quite easy to modify the glibc
source to turn the exporting back on.


------- Additional Comment #7 From Michael Young on 2003-06-20 17:33 -------

See http://lists.debian.org/debian-glibc/2002/debian-glibc-200210/msg00093.html
for information on how to modify the glibc source so the symbols work again.
Also the problem is with uselocale, not TLS.


------- Additional Comment #8 From Shawn Walker on 2003-06-20 22:03 -------

The point is that they're internal symbols and no sane application should be
using them anyway.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14157