Bug 6443 - kernel build error on kernel-2.2.12-20 rebuild as normal user
kernel build error on kernel-2.2.12-20 rebuild as normal user
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-10-28 00:14 EDT by carenas
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-04 17:26:24 EST
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 carenas 1999-10-28 00:14:58 EDT
on kernel-2.2.12-20's SPEC there is a bug on %build where
BuildPCMCIA would be called twice when there is an i386
Build, resulting on an error on a build of the spec as a
normal user, because of an attempt to overwrite a read only

actually, the first files build for BuildPCMCIA are tagged
as BOOT and then overwriten for the final ones (if building
the spec as root).

as can be seen on the following extract of the kernel spec,
when arch = i386, the BuildPCMCIA instruction is called

#BOOT kernel
BuildKernel BOOT
%ifarch i386
SaveHeaders BOOT

%ifarch i386 i586 i686
BuildiBCS no

actually the first call of BuildPCMCIA has no sense.., since
there isn't a corresponding -pcmcia package for boot
subpackage, so this could be commented, keeping like this

#BOOT kernel
BuildKernel BOOT
SaveHeaders BOOT
Comment 1 Bill Nottingham 1999-11-04 18:33:59 EST
The call for building it in the BOOT section is for
building the modules, which are used in the -BOOT kernel.
Comment 2 Cristian Gafton 2000-01-04 17:26:59 EST
Assigned to dledford
Comment 3 Ben LaHaise 2002-06-03 17:54:43 EDT
I believe this bug to be fixed in the 2.4 kernel rpm of current releases. 
Please reopen if it is still a problem in 7.3.

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