[Bug libc/2588] New: Compatibility issue with errno and h_errno

[Bug libc/2588] New: Compatibility issue with errno and h_errno

[PARKINGSV at yahoo dot com]

I am installing cadence EDA software on CentOS 4.3, a Linux distribution
that uses glibc 2.3.4. I checked the /lib directory and found that 
there is a libc.so.6 and libc-2.3.4.so. Both report a glibc version
of 2.3.4. However, during installation, the I got error message such as:

"Incorrectly built binary which accesses errno, h_errno directly. Needs to be
fixed."

I did an online search and some people say this is with recent 
glibc releases, which provide a separate errno variable for each thread.
Accessing errno directly may not work correctly for applications that 
make use of pthreads.

Is that the course of this error message? 
Wandering if there is anyway to fix it. Can I rollback to previous
version of glibc? Your feedback is very appreciated.

-- 
           Summary: Compatibility issue with errno and h_errno
           Product: glibc
           Version: 2.3.4
            Status: NEW
          Severity: critical
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: PARKINGSV at yahoo dot com
                CC: glibc-bugs at sources dot redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=2588

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/2588] Compatibility issue with errno and h_errno

[jakub at redhat dot com]

------- Additional Comments From jakub at redhat dot com  2006-04-20 08:15 -------
You need to file a bug with whomever gave you the buggy software, glibc just
warns you about a bug in it (and in RHEL{3,4}/Fedora Core{1-4}/CentOS{3,4} works
around it, though note that in more recent distributions such buggy software is
simply out of chance to work.
errno is defined as *__errno_location () in glibc for more than 9 years,
so any properly built program (that #include <errno.h> when it wants to use
errno rather than violating the standards and definining it by itself) will
not reference errno directly and will work just fine.

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


http://sourceware.org/bugzilla/show_bug.cgi?id=2588

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.