Bug 441940 - latest glibc breaks anaconda build
latest glibc breaks anaconda build
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
urgent Severity urgent
: rc
: ---
Assigned To: Chris Lumens
Alexander Todorov
: Regression
Depends On:
  Show dependency treegraph
Reported: 2008-04-10 15:51 EDT by Doug Chapman
Modified: 2008-05-21 11:33 EDT (History)
6 users (show)

See Also:
Fixed In Version: RHBA-2008-0397
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-21 11:33:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output of rpmbuild -bb anaconda.spec (55.58 KB, text/plain)
2008-04-10 15:51 EDT, Doug Chapman
no flags Details

  None (edit)
Description Doug Chapman 2008-04-10 15:51:59 EDT
Description of problem:
While trying to debug an unrelated anaconda issue I ran into the problem that I
cannot build anaconda with glibc-2.5-23 (which is new today it appears).

A bunch of _nl_* symbols are now multiply defined or chagned:

multiple definition of `_nl_category_name_sizes'
../stubs/libunicode-lite.a(unicode-lite.o):(.rodata+0x0): first defined here
/usr/bin/ld: Warning: size of symbol `_nl_category_name_sizes' changed from 104
in ../stubs/libunicode-lite.a(unicode-lite.o) to 13 in
multiple definition of `_nl_category_name_idxs'
first defined here
/usr/bin/ld: Warning: size of symbol `_nl_category_name_idxs' changed from 1 in
../stubs/libunicode-lite.a(unicode-lite.o) to 13 in
multiple definition of `_nl_category_names'
../stubs/libunicode-lite.a(unicode-lite.o):(.data.rel.ro.local+0x0): first
defined here
/usr/bin/ld: Warning: size of symbol `_nl_category_names' changed from 104 in
../stubs/libunicode-lite.a(unicode-lite.o) to 137 in
/usr/lib/gcc/ia64-redhat-linux/4.1.2/../../../libc.a(setlocale.o): In function
(__libc_freeres_fn+0x280): multiple definition of `_nl_locale_subfreeres'

I confirmed if I go back to glibc-2.5-21 the problem goes away.  Also a quick
diff of glibc soruces does indeed show changes in this area.

Version-Release number of selected component (if applicable):
I will upload the full log file of the build also.

How reproducible:

Steps to Reproduce:
1. yum update (to get latest glibc)
2. rpmbild -bb anaconda.spec
Actual results:

Expected results:

Additional info:
Comment 1 Doug Chapman 2008-04-10 15:51:59 EDT
Created attachment 302064 [details]
output of rpmbuild -bb anaconda.spec
Comment 2 Jakub Jelinek 2008-04-10 16:05:37 EDT
Then anaconda should be changed accordingly.  Does it use libc.a gettext but not
libc.a locale stuff?  That's risky to say at least.  I guess anaconda will have
the same problem in rawhide then...
All that changed in this area is that now __libc_setlocale_lock is a rwlock
rather than mutex.
Comment 3 Jakub Jelinek 2008-04-10 16:07:53 EDT
-Wl,-M should help figure out why these .o files are now brought in and weren't
Comment 4 Jakub Jelinek 2008-04-11 04:10:56 EDT
--- anaconda- 2008-04-08 18:17:36.000000000 -0400
+++ anaconda-    2008-04-11 03:40:02.000000000 -0400
@@ -116,5 +116,8 @@ const size_t _nl_category_name_sizes[] =
 /* avoid bringing in glibc's setlocale.o - we want to use our
    fake setlocale() */
-typedef pthread_mutex_t __libc_lock_t;
-__libc_lock_t __libc_setlocale_lock;
+  pthread_mutex_t mtx;
+  pthread_rwlock_t rwlck;
+} __libc_setlocale_lock __attribute__((nocommon));

should fix this (at least loader links).  As the stub doesn't use
__libc_setlocale_lock and so it is there only to satisfy wcsmbsload.o,
the above should make it work both with older and newer glibc (i.e. no matter
if it is actually a mutex, libc one int mutex or rwlock).  All the default
mutex, libc one int mutex and rwlock initializers are all zeros, and nocommon
means the symbol will be preferred over the one in libc.a (setlocale.o) where it
Comment 5 Chris Lumens 2008-04-11 11:22:50 EDT
A quick scratch build earlier did not reproduce this issue, though I suppose
that's simply because the latest glibc has not made it into the right tree yet.
 We have at least one more reason to do a rebuild of anaconda, so I'll ACK this.
Comment 10 Chris Lumens 2008-04-15 17:34:32 EDT
This will be fixed in anaconda-
Comment 14 errata-xmlrpc 2008-05-21 11:33:52 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.