Hello guys! In order to install vmware 6.5 I needed gcc and kernel source packages. kernel source installation fails with error:
installing: kernel-source-2.6.27.19-3.2.1 [error]
Installation of kernel-source-2.6.27.19-3.2.1 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: ln: creating symbolic link `/usr/src/linux-obj/x86_64/default’: No such file or directory
error: %post(kernel-source-2.6.27.19-3.2.1.i586) scriptlet failed, exit status 1
I tried with zypper and through YAST. Same result…
Deinstall kernel-source, remove all symbolic links or folders containing “linux” in /usr/src/ and reinstall kernel-source.
I would also install kernel-syms together with kernel-source.
Did you remove things by hand? It’s the second time in a couple of days that i see people using a nodeps option. And all this on something concerning the linux kernel. Yes, it is possible to build kernel-modules that damage your hardware. This should never be done.
QUOTE](with --nodeps --force) Error: Subprocess failed. Error: RPM failed: ln: creating symbolic link `/usr/src/linux-obj/x86_64/default’: No such file or directory
error: %post(kernel-source-2.6.27.19-3.2.1.i586) scriptlet failed, exit status 1 [/QUOTE]
This explains it all: you are mixing x86_64 and i586 packages. Either a 64-bit running kernel with 32-bit kernel-sources or the other way around.
If the rest of your system is the same, you definitely should reinstall, there’s no way that you’ll end up with a stable system.
There are 32-bit packages for 64-bit systems, but they are compiled for 64bit systems. You’ll recvognize them from their ‘32bit’ part in the names.
Ehm, this “nodeps and force” is done by YaST/zypper (not kidding).
Looks really strange but YaST/zypper resolve dependencies before installing, so no worries there.
//Edit:
This explains it all: you are mixing x86_64 and i586 packages.
Oh, well spotted, I missed that one out, yeah, mixing i586 and x86_64 is of course a very bad idea.
I have x64 and yast installed 32-bit kernel source by default. This is definitely a bug.
OK selected x64 version from yast and everything is working like a charm. Even vmware compiles its modules without problems. Thanks guys.
You figured it out - well done!