Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
kernel version and RHEL version?
RHEL 6.1 Kernel version 2.6.32 snapshot 5
root@ATCA-N7> uname -a
Linux ATCA-N7 2.6.32-131.0.5.el6.x86_64 #1 SMP Wed Apr 20 00:16:35 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
root@ATCA-N7> cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.1 Beta (Santiago)
how is it supposed to work?
Compliation should succeed. With RHEL 6.0, we do not see this problem
how is it working currently?
We have linker errors in while compiling our application
what are the configurations/ parameters set ?
RHEL 6.1 Beta tool set -> /usr/lib, /usr/lib64, /lib, /lib64 of RHEL 6.1 is used for compilationconclusion/remarks/findings
We are not sure, but we suspect some kind of incompatibility from the new library versionns distributed with RHEL 6.1
is solution available already?
No
RPM or Module the problem is seen?
/tools/Linux/LINUX/usr/lib/librt.so: undefined reference to `__fortify_fail@GLIBC_PRIVATE'
/tools/Linux/LINUX/usr/lib/libm.so: undefined reference to `__get_cpu_features@GLIBC_PRIVATE'
/tools/Linux/LINUX/lib/libnsl.so.1: undefined reference to `__libc_clntudp_bufcreate@GLIBC_PRIVATE'
/tools/Linux/LINUX/lib64/libgssapi_krb5.so.2: undefined reference to `__isoc99_sscanf'
/tools/Linux/LINUX/lib64/libglib-2.0.so.0: undefined reference to `pipe2'
/tools/Linux/LINUX/usr/lib64/libcrypto.so.10: undefined reference to `__fread_chk'
/tools/Linux/LINUX/lib64/libglib-2.0.so.0: undefined reference to `__vasprintf_chk'
/tools/Linux/LINUX/lib64/libglib-2.0.so.0: undefined reference to `__isoc99_fscanf'
/tools/Linux/LINUX/lib64/libselinux.so.1: undefined reference to `__asprintf_chk'
/tools/Linux/LINUX/lib64/libkrb5support.so.0: undefined reference to `__open_2'
/tools/Linux/LINUX/lib64/librt.so.1: undefined reference to `__fortify_fail@GLIBC_PRIVATE'
/tools/Linux/LINUX/lib64/librt.so.1: undefined reference to `__vdso_clock_gettime@GLIBC_PRIVATE'
Hardware type ( if applicable)?
None
impact? Critical/liveable
Critical
urgency of solution required
As early as possible
steps to reproduce problem
Its reproducible , but in our application compilation environment.