Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 47276 - Conflicting types for xtime during make boot
Conflicting types for xtime during make boot
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-07-04 06:34 EDT by Reuben Thomas
Modified: 2007-04-18 12:34 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-04 06:34:34 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 Reuben Thomas 2001-07-04 06:34:31 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3-12 i686; en-US; rv:0.9.1)

Description of problem:
(N.B. This is a bug in kernel-source, which doesn't seem to be an option in
the packages list):

When I try to make boot in /usr/src/linux-2.4, I get the error:

timer.c:40: conflicting types for `xtime'
/usr/src/linux-2.4.3/include/linux/sched.h:548: previous declaration of `xtime'

How reproducible:

Steps to Reproduce:
1.Install kernel-source 2.4.3-12
2.Configure the kernel
3.make dep
4.make boot

Actual Results:  I get the error reported above.

Additional info:

I have the gcc-3.0 package installed. I understand this might not work for
building a kernel, but it doesn't seem to be the problem in this instance,
where the two declarations simply don't match (AFAICS).
Comment 1 Arjan van de Ven 2001-07-04 06:37:50 EDT
Thanks for the report. This is a known point where gcc3 breaks the kernel, and 
there are several others as well. This will be fixed for later kernels we put
out, but I'd strongly recommend not using gcc3 for a kernel for now, not until
there's been more testing.

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