Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 146614 - Inconsistent struct gconvcache_header
Inconsistent struct gconvcache_header
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: glibc (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-01-30 13:45 EST by H.J. Lu
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: 2.3.4-2.9
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-30 15:25:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description H.J. Lu 2005-01-30 13:45:28 EST
When I was checking glibc from 2005-01-30's CVS on i686, I got

modules.cache.29517 /usr/lib/gconv/gconv-modules.cache differ: byte 
15, line 1
make[4]: *** [test-iconvconfig] Error 1

[hjl@gnu-10 glibc-nptl]$ rpm -qf /usr/lib/gconv/gconv-modules.cache

I have no problems on RHEL4/x86_64, RHEL3/x86_64 nor RHEL3/ia64.
Comment 2 H.J. Lu 2005-03-01 20:41:36 EST
Here is the glibc bug report

Comment 3 Jakub Jelinek 2005-03-10 04:26:50 EST
This is fixed in glibc-2.3.4-2.7.  Thanks.
Comment 4 Ulrich Drepper 2005-06-30 15:02:09 EDT
I'm closing this.  It's not really a RHEL issue since we don't support you
compiling glibc and using it with the system.
Comment 5 H.J. Lu 2005-06-30 15:08:26 EDT
I am not sure if I understand what you were trying to say. I did

# cvs co libc
# .../configure
# make
# make xcheck

and got the faulure on RHEL 4. Were you saying I shouldn't build glibc
on RHEL4? Do you have a stable Linux distribution you can recommend for
working on glibc?
Comment 6 Jakub Jelinek 2005-06-30 15:25:19 EDT
RHEL4 U1 included the fix.

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