Bug 150680
Summary: | glibc does not export functions | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Jens Westermann <jens.westermann> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-03-09 20:36:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jens Westermann
2005-03-09 16:18:19 UTC
Those symbols are prohibited for all newly linked programs/libraries, because they aren't thread safe. glibc ensures binary compatibility for shared libraries and binaries only, while apparently Progress is trying to link objects that were compiled on different glibc against the RHEL3 glibc. That never worked reliably and never will. Either you need to recompile them against RHEL3 glibc, then you can also link them against that glibc, or you need to link them against the glibc that was used to compile them. RHEL3 includes compat-glibc package, which could help you, as that's glibc from AS 2.1. So compiling and linking with gcc -B /usr/lib/i386-redhat-linux7/lib/ -static-libgcc -L /usr/lib/i386-redhat-linux7/lib/ -I/usr/lib/i386-redhat-linux7/include/ could work. |