Bug 332182 - The gcc version doesn't match the one the kernel was compiled with
Summary: The gcc version doesn't match the one the kernel was compiled with
Status: RESOLVED DUPLICATE of bug 309022
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Other (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Michael Matz
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-09 13:42 UTC by Andreas Klein
Modified: 2007-10-10 12:46 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Klein 2007-10-09 13:42:10 UTC
The latest update kernel for SuSE 10.1 was compiled with a gcc which wasn't delivered for 10.1.

VMware complains, that the gcc has another version, than the gcc which was used for kernel compilation:

Your kernel was built with "gcc" version "4.1.2", while you are trying to use
"/usr/bin/gcc" version "4.1.0". This configuration is not recommended and
VMware Server may crash if you'll continue. Please try to use exactly same
compiler as one used for building your kernel.

donald:/local # cat /etc/SuSE-release 
SUSE LINUX 10.1 (X86-64)
VERSION = 10.1
donald:/local # cat /proc/version 
Linux version 2.6.16.53-0.8-smp (geeko@buildhost) (gcc version 4.1.2 20070115 (prerelease) (SUSE Linux)) #1 SMP Fri Aug 31 13:07:27 UTC 2007
donald:/local # gcc --version
gcc (GCC) 4.1.0 (SUSE Linux)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

donald:/local # 

The gcc seems to be the one which is delivered with the current SLES10.
So you should release this one for 10.1 as well, or compile the kernel with the old gcc.
Comment 1 Richard Biener 2007-10-10 12:46:33 UTC

*** This bug has been marked as a duplicate of bug 309022 ***