Bug 193839 - wrong gcc version
Summary: wrong gcc version
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-02 01:47 UTC by Luis Fernando da Silva
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-06-06 20:22:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Luis Fernando da Silva 2006-06-02 01:47:49 UTC
Description of problem:
I am compiling the LFS (fast streams) however I am getting the following 
message :

configure: WARNING:
***
*** The kernel compiler was:
***   "gcc version 3.4.6 20060404 (Red Hat 3.4.6-2)",
*** and the current compiler is:
***   "gcc version 3.4.5 20051201 (Red Hat 3.4.5-2)".
***
*** These compilers do not match.
*** This will cause problems later.
***

  I tried to get the newest gcc, however it says I am already up2date, but my 
gcc version 3.4.5 20051201 (Red Hat 3.4.5-2). 
  I have recently update my kernel to this new version and it is the latest 
for my platform, so my question is how the kernel can be compiled with a newer 
version and I am not able to get the same version using the up2date ? 
  How can I get the correct version of gcc which match this new kernel ?
  Thanks very much,

  Fernando


Version-Release number of selected component (if applicable):
Linux linux2 2.6.9-34.0.1.ELsmp #1 SMP Wed May 17 16:59:36 EDT 2006 x86_64 
x86_64 x86_64 GNU/Linux


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jason Baron 2006-06-06 20:22:07 UTC
Even though the compiler version is not supplied, this should not cause any
problems with third party kernel modules. If there is a really problem please
re-open.


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