Solved

Glibc and the "undefined reference to __ctype_b" error

Posted on 2003-12-11
3
19,167 Views
Last Modified: 2013-12-15
After installing Redhat 9.0 some older libraries (part of Talarian Smartsockets if you are interested) are no longer working for us.
While linking, the error message "undefined reference to __ctype_b" appears - this is a feature of glibc no longer avaiable in glibc-2.3.2-11.9, but avaiable in glibc-2.2.

To gain a better understanding of the problem you can also read
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=91290

I will give points for a detailed description of a solution, those come to mind:

1. Install older version of glibc, i.e. 2.3.2-5, the last version that seems to work. Questions: Will Redhat still work, how to downgrade an installation of glibc
   (parameters to force rpm to install older version?)

2. Parallel install of two glibc versions? Is this even possible?

3. A patch/compatibility addon for the newer version of glibc, I haven't found one but perhaps I have not looked hard enough?

Please try to give a detailed description of the solution, I'm still a bit shaky when it comes to managing libraries and dependencies in Linux.
0
Comment
Question by:Wojciech Duda
  • 2
3 Comments
 
LVL 24

Expert Comment

by:shivsa
ID: 9923602
did u try the workaround given in bug report.
0
 
LVL 24

Accepted Solution

by:
shivsa earned 450 total points
ID: 9923905
I got this from the bug reports filed.
-----------------------------
As u can see in bug report this is a compatibility problem between old libs versus new libs.
Static binaries that uses something old and have  the dynamic linking code linked in statically. so in your code, when u compile your code, your code loads old binaries and its dependency(like libc.so or something), so your old dynamic linking code try  loading new glibc 2.3 code and link together.

The bug you are seeing is in the old dynamic linking code, which cannot handle references to "hidden" version set symbols defined in the
same object.  Redhat fixed that bug in the 2.3 dynamic linking code, and in fact found it because it was tickled by the unexported compatibility-only
symbols like __ctype_toupper.  It's exactly these symbols that are crashing the old 2.2.5 dynamic linking code in your static binaries.

If you want to hack your glibc 2.3 build to work around the problem, here is how to do it:
Remove the "compat_symbol" lines from ctype/ctype-info.c
and recompile libc.  
This makes those symbols be exported again and that removes the only cases of this combination of symbols and relocations that
the old dynamic linker code doesn't handle.  It means that link-time references against those symbols will resolve happily in your libc.so
binary, which is exactly what we don't want for these obsolete symbols.

So this workaround won't go into glibc, but you can use it yourself.  The Red Hat Linux 8.0 version of glibc (which is otherwise not much modified
from glibc 2.2) has this very workaround, not for the problem of old static binaries that you are having, but to support old static libraries.
------------------
So the simple solution will be to remove
"compat_symbol" lines from ctype/ctype-info.c and recompile libc,
and then recompile all your binaries and all and see if it works.
0
 
LVL 8

Author Comment

by:Wojciech Duda
ID: 9948404
Well, while I don't know if this will be a working solution for us (as we'll have to always use the modified glibc version), this workaround description is a vaiable solution and I'll try this. Thanks for your input.
0

Featured Post

Master Your Team's Linux and Cloud Stack

Come see why top tech companies like Mailchimp and Media Temple use Linux Academy to build their employee training programs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This is the error message I got (CODE) Error caused by incompatible libmp3lame 3.98-2 with ffmpeg I've googled this error message and found out sometimes it attaches this note "can be treated with downgrade libmp3lame to version 3.97 or 3.98" …
I am a long time windows user and for me it is normal to have spaces in directory and file names. Changing to Linux I found myself frustrated when I moved my windows data over to my new Linux computer. The problem occurs when at the command line.…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question