Bug 329203

Summary:	kernel was built with "gcc" version "4.1.2" / yast provides "gcc" only version "4.1.0"
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Volker Kiefer <edv>
Component:	Development	Assignee:	Michael Matz <matz>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	ag, crh, ibz, sndirsch
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	SuSE Linux 10.1
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Volker Kiefer 2007-09-28 07:22:55 UTC

Hi,

could you pls. provide "gcc" in version "4.1.2" in yast?

While trying to install VMware Server 1.0.4 on Opensuse 10.1 i got the following error:

############################
...Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Server is suitable for your
running kernel.  Do you want this program to try to build the vmmon module for
your system (you need to have a C compiler installed on your system)? [yes]

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

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. Do you want to go with compiler
"/usr/bin/gcc" version "4.1.0" anyway? [no]...
############################

Thank you!

Comment 1 Miquel A. Noguera 2007-09-28 08:13:03 UTC

You can workaround this problem installing kernel-source for your kernel version and compiling it with your available 4.1.0 gcc.

Regards.

Comment 2 Stefan Dirsch 2007-10-16 13:06:11 UTC

After 10.1 release gcc has been updated to 4.1.2, which means that also updated kernels for 10.1 are built with 4.1.2, but for gcc itself no updateds are provided. This looks like a mistake to me.

Comment 4 Richard Biener 2007-10-16 13:10:15 UTC


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