Bug 148997
Summary: | broken glibc-headers and glibc-kernheaders after consistently yum upgrading | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jason Vas Dias <jvdias> | ||||
Component: | yum | Assignee: | Jeremy Katz <katzj> | ||||
Status: | CLOSED NOTABUG | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-02-18 14:50:55 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: | |||||||
Attachments: |
|
Description
Jason Vas Dias
2005-02-17 20:23:18 UTC
Recompiling & installing binutils-2.15.94.0.2-1 didn't help. I'm now recompiling gcc & glibc to try to get a working FC4 build environment. And of course the gcc build fails (log file available on request). At last I finally found the root cause of this problem . It appears to be an issue with RPM, or yum, or glibc-headers, or glibc-kernheaders. I noticed that this version of the configure test function compiles into an executable fine : --- const char *inet_ntop (int af, const void *src, char *dst, unsigned cnt); main() { char a[16],b[64]; return (inet_ntop(10, (const void*)a, b, sizeof(b)) == (const char*)0); } --- ie. with no headers included . I found that even the original function compiled fine on the 'porky' build server in its dist-fc4-build buildroot, so it looks like porky has working headers while my machine did not. This is very strange because they both report the SAME versions of glibc-headers and glibc-kernheaders : hostname --fqdn; rpm -q glibc-kernheaders glibc-headers --queryformat '%{NAME} %{VERSION} %{RELEASE} %{ARCH} %{BUILDTIME} %{BUILDHOST}\n' porky.build.redhat.com glibc-kernheaders 2.4 9.1.89 i386 1106222014 decompose.build.redhat.com glibc-headers 2.3.4 10 i386 1108213652 porky.build.redhat.com $ hostname --fqdn; rpm -q glibc-kernheaders glibc-headers --queryformat '%{NAME} %{VERSION} %{RELEASE} %{ARCH} %{BUILDTIME} %{BUILDHOST}\n' jvdias.boston.redhat.com glibc-kernheaders 2.4 9.1.89 i386 1106222014 decompose.build.redhat.com glibc-headers 2.3.4 10 i386 1108213652 porky.build.redhat.com Yet there are vast differences between the files in each package on each machine. Either my machine has been hacked (unlikely, since it never leaves the office) or yum / RPM has failed to upgrade the packages properly. (I've been consistently using only 'yum upgrade' since installing a pre-FC3 rawhide) . The output of this command showing the differences between the files from porky (in include/) and in my /usr/include is attached: rpm -ql glibc-headers glibc-kernheaders | while read f; do F=${f#/usr/}; if [ -f $F ] && ! diff -q $f $F >/dev/null; then echo `perl -e 'print "-"x80,"\n";'`; echo diff -u $F $f':'; diff -u $F $f; fi; done > /tmp/broken_headers.patch I've preserved the original broken /usr/include if anyone is interested, but now my /usr/include is patched to have the files as they are on porky, everything works OK again. Created attachment 111188 [details]
diffs between my headers and porky's
differences between my headers and porky's, when both machines have the same
glibc-headers & glibc-kernheaders packages installed.
I'm moving this to yum, because that's the only tool I've been using to update the glibc header packages. But perhaps the maintainer of these packages could please check that there are no reasons why new headers would not be installed during a yum upgrade of glibc-headers and glibc-kernheaders . I know this is a very weird bug, and probably will never be solved. But I never used any tool to update the glibc-headers and glibc-kernelheaders packages except yum, and it finally left me with an unusable build environment and vast differences between the header files on my machine and those in the dist-fc4-build buildroot on porky, even though the same glibc-headers and glibc-kernelheaders package versions were installed on both machines. AARGH! It seems that while I was testing building and installing the BIND 'libbind' package, doing an install of libbind wiped out these system header files . Very Sorry! Please ignore this bug. |