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

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

[cmosis5 at hotmail dot com]

I'm trying to crate a cross compiler for AVR using GCC3.3.3.  

My system is RH9, with GCC3.2.2

the options given when GCC was configured/built; 
./configure --target=avr --program-prefix="avr-" --enable-language=c

the complete command line that triggers the bug; 
make

Error message:
gcc   -g -O2 -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long
  -DHAVE_CONFIG_H  -o Tcollect2 \
        collect2.o tlink.o intl.o version.o   ../libiberty/libiberty.a 
../libiberty/libiberty.a(cp-demangle.o)(.text+0xd51): In function
`demangle_identifier':
/usr/delme/gcc-3.3.3/libiberty/cp-demangle.c:1489: undefined reference to
`__ctype_b'
collect2: ld returned 1 exit status
make[1]: *** [collect2] Error 1
make[1]: Leaving directory `/usr/delme/gcc-3.3.3/gcc'
make: *** [all-gcc] Error 2

-- 
           Summary:  undefined reference to `__ctype_b'  (can't compile gcc
                    for avr using gcc3.3.3)
           Product: gcc
           Version: 3.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: cmosis5 at hotmail dot com
                CC: gcc-bugs at gcc dot gnu dot org


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

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

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-02-16 13:27 -------
This is not a bug in GCC, the problem for you looks like you are using a new or older version of glibc 
headers than what the glibc library you have.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID
            Summary| undefined reference to     |undefined reference to
                   |`__ctype_b'  (can't compile |`__ctype_b'  (can't compile
                   |gcc for avr using gcc3.3.3) |gcc for avr using gcc3.3.3)


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

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

[cmosis5 at hotmail dot com]

------- Additional Comments From cmosis5 at hotmail dot com  2004-02-16 14:45 -------
(In reply to comment #1)
> This is not a bug in GCC, the problem for you looks like you are using a new
or older version of glibc 
> headers than what the glibc library you have.

Nope, it appears to be a problem with RedHat's newest glibc, here is a summary
of what I have found experts saying:
"The glibc-2.3.2-5 exports __ctype_b as compatibility
symbol, but glibc-2.3.2-11.9 doesn't. "

My question is, is GCC using ctype_b in a way that it shouldn't be?

-- 


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

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

[cmosis5 at hotmail dot com]

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

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

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-02-16 15:01 -------
Again this cannot be a GCC issue as GCC does not use __ctype_b at all in any of it headers except for 
libstdc++ but that is ifdef on the version of glibc so it cannot be this problem because this happening 
too soon.  Again it looks like your headers do not match the version of the library which is installed.

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


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