Bug 38878

Summary: Too many levels of symbolic links
Product: [Retired] Red Hat Linux Reporter: Magnus Johansson <l_magnus_j>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED CURRENTRELEASE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-05-03 05:17:31 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 Magnus Johansson 2001-05-03 05:17:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3 i686; en-US; 0.7) Gecko/20010316


This is a system that has been upgraded from 7.1beta2 (Wolverine) to 7.1
(Seawolf).

When I try to compile the new kernel 2.4.4 using kgcc instead of gcc, I get
the following message:

/usr/include/stdio.h:33: stddef.h: Too many levels of symbolic links
In file included from /usr/include/stdio.h:35,
                 from tkparse.c:48:
/usr/include/bits/types.h:29: stddef.h: Too many levels of symbolic links
In file included from /usr/include/libio.h:30,
                 from /usr/include/stdio.h:64,
                 from tkparse.c:48:
...

This did not happen in Wolverine. Should kgcc still be used in R.H. 7.1 for
kernel compilation?

Reproducible: Always
Steps to Reproduce:
1.untar the kernel source code under /usr/src
2.Change in Makefile to use kgcc instead of gcc
3.make xconfig
	

Actual Results:  /usr/include/stdio.h:33: stddef.h: Too many levels of
symbolic links
In file included from /usr/include/stdio.h:35,
                 from tkparse.c:48:
/usr/include/bits/types.h:29: stddef.h: Too many levels of symbolic links
In file included from /usr/include/libio.h:30,
                 from /usr/include/stdio.h:64,
                 from tkparse.c:48:


Expected Results:  No error message, kernel compilation should have
proceeded without problems.

Comment 1 Jakub Jelinek 2001-05-03 08:12:08 UTC
Upgrades from beta releases to the final release are NOT supported.
This is one of the cases.
Basically, rpm -e all the compat-* stuff, then install it again.
Wolverine had files from two directories hardlinked together which for
various reasons did not work well, so they were replaced with symlinks.