Bug 199207 - Cannot recompile the kernel
Cannot recompile the kernel
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: gcc (Show other bugs)
5
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
:
: 199208 199209 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-17 18:46 EDT by Jose Manuel
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-29 05:29:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jose Manuel 2006-07-17 18:46:01 EDT
Description of problem:
I am not able to recompile the kernel (Fedora or Vanilla kernels). Doing make 
bzImage begins the process but it shows an error of violation of segment and it 
finalize the process. I am trying with several versions of kernels but the out 
its the same.

Hardware: AMD Athlon 3000 XP 32bits. 1GB RAM, Gforce 5200 fx

Version-Release number of selected component (if applicable):Fedora Core 5


How reproducible:


Steps to Reproduce:
1. make menuconfig
2. make clean
3. make bzImage
  
Actual results:


Expected results:


Additional info:
Comment 1 Damien Durand 2006-07-17 18:51:13 EDT
*** Bug 199208 has been marked as a duplicate of this bug. ***
Comment 2 Damien Durand 2006-07-17 18:52:59 EDT
*** Bug 199209 has been marked as a duplicate of this bug. ***
Comment 3 Dave Jones 2006-07-25 22:55:57 EDT
gcc segfaulting would be a gcc bug. (or bad hardware, be sure to give your
machine a workout for a day or so with memtest86)
Comment 4 Jakub Jelinek 2006-08-07 06:37:25 EDT
You need to paste the actual error messages you got and whether the problem
is reproduceable.
Comment 5 Jakub Jelinek 2006-08-29 05:29:43 EDT
No response, there is nothing we can do about this without it.

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