One of my biggest uses for Linux is to run VMware and thusly being able to execute different versions of Windows. However, in order to use VMware, some modules need to be compiled and installed. My procedure failed on the second step.
Changed into /usr/src/linux
make cloneconfig
Cloning configuration file /proc/config.gz
scripts/kconfig/conf: invalid option – ‘D’
See README for usage info
make[1]: *** [cloneconfig] Error 1
make: *** [cloneconfig] Error 2
I could not find what the ‘D’ option is for -but- I experimented and removed it from the Makefile in scripts/kconfig/. As expected, it did not help. In fact, things got worse. Any clues or suggestions??
I did. It says nothing about this kind of failure nor has info about the switches. If you have the source installed please try cd’ing to /usr/src/linux and typing in “make cloneconfig” and let me know what happens. I have, like always, installed the kernel sources and the syms. Failures in prior versions were cause it couldn’t find the header files. This version didn’t even get that far.
Hi to all … and thanks for the replies -BUT- Please re-read what I said. Even though I was wanting to compile for VMware the first thing I always do is a “straight compile” of the kernel … just the kernel … nothing else. That is what I was trying to do. Please disregard VMware. The problem is … I can not make cloneconfig.
On 12/17/2010 05:06 PM, chucktr wrote:
>
> Hi to all … and thanks for the replies -BUT- Please re-read what I
> said. Even though I was wanting to compile for VMware the first thing I
> always do is a “straight compile” of the kernel … just the kernel …
> nothing else. That is what I was trying to do. Please disregard VMware.
> The problem is … I can not make cloneconfig.
Does it work when you replace the “make cloneconfig” step by a simple
“zcat /proc/config.gz > .config”?
Hi lw,
Thanks for the info. Yes, it does create a .config. Now then, I haven’t played with all the kernel building stuff and most of the time I was just putting in fixes from others in order to get a compile. Before executing your request I checked the /usr/src/linux dir and I found a .config.running. After performing the zcat operation I then had a .config and a .config.running. I performed a diff on them and there were no differences. I was under the impression, in the past, that “make cloneconfig” performed this step. Appears that some changes were made … and some were missed. But that is what we are to find out in these Milestones… right? I presume I should follow this up with a bug report??
**From myself in version 10.2 — to myself in version 11.3 **
Do a full compile of the kernel before trying the install so that all the dependencies are loaded and in the correct locations. Besides, if you can’t compile the kernel, then you can’t install VMware. The two go hand in hand.
1. cd /usr/src/linux
2. make cloneconfig <<---- this was the problem. The zcat "fixed" it.?.?
3. make prepare
4. make modules
There are those who claim the above is not necessary. However, every time I have encountered problems, performing all three operations above seemed to be the cure. There are usually other things that also have to be “fixed”. I’ve already seen that there are some patches for VMware that must be made in order to get a successful compile.
Now then, after performing the zcat above I did a “make prepare” and then started a “make modules”. It will be over an hour from now till I know the final results -but- it is looking good.
Thanks lwfinger… and I’ll let you know the result,
Chuck
Hi,
Compile … Re-Compile… ??? Same thing ain’t it. When you do a ‘make’ … only newer source code is supposed to get compiled. So, IF what is on the System has never been compiled … then it will get compiled. I have tried to install VMware …* for the first time* … after installing a version of SuSE or openSuSE … without doing the above three steps. It never seems to work… for me. Once they have been done, future installs are just a ‘Re-Compile’ … ie; only the items that need it. Also, I do believe that version.h doesn’t get created until either a ‘make’ or a ‘make prepare’ is performed. I have experienced the same scenario with the nVidia Drivers. My experiences over the last couple of versions have not been the most delightful. IF you care to read about them you can venture over to my site and take a look at the last version on:
the later one I am in the process of building -and- trying some new Web Page stuff so it will be more jumbled than any of the others. And anything concerning this latest problem will not be in there until at least tomorrow or later.
'make cloneconfig' should work -or- it should be removed. I will report it and let the developers decide.
Compiling the complete kernel vs compiling a few modules is not the
same. version.h exists, if you read about the changes in later kernels
all that happened was the location has moved and the software (eg
vmware) hasn’t caught up…
I use both vmware and nvidia on this system, dual boot with SLED and
openSUSE, again I will reiterate, you don’t need to recompile the
kernel to build kernel modules for the running kernel either here or on
the openSUSE Build Service.
In saying that, you can feel free to recompile the kernel as much as
you want
Would I recommend it to a user for installing vmware workstation,
server or nvidia drivers… no
> Compiling the complete kernel vs compiling a few modules is not the
> same. version.h exists, if you read about the changes in later kernels
> all that happened was the location has moved and the software (eg
> vmware) hasn’t caught up…
Why has vmware not caught up? That change has been in effect since 2.6.36-rc1
(nearly 6 months). When the change was reported to VirtualBox, they posted a
patch within hours, and made it part of the next minor release.
All of this is silly. Do you or don't you need to compile?? That was not the question. The question way back up at the top concerned an error in making cloneconfig. I didn't want to start a heated debate or cause any hard feelings -but- it is difficult sometimes, when what is said is taken wrong because it is only text and there is no real person to express tones or jesters. So, let me say this ... I am not mad, yelling or angry or any of those things. So please do not take anything the wrong way. Course I need to read that myself and hope that none of you are replying in a harsh way. Anyway, to the point.
I would like to suggest that all read the entire question before answering. The only person in the above list that replied with something concerning the original question was lwfinger... and what he suggested worked ... for the situation. I was finally able to get a compile. I do believe that mentioning VMware also added to the confusion. IF I had just asked about the cloneconfig, without mentioning VMware, this whole thing would have probably would have been a lot shorter.
After the compile, I installed VMware 7.1.3 and the initial installation was successful. Upon the execution it failed. This was corrected with a patch from VMware: [openSUSE Lizards](http://lizards.opensuse.org/2010/11/15/make-vmware-workstation-7-1-3-running-with-11-4-kernel-2-6-37/)
All in all the System(s) are working and I have openSuSE 11.4 M5 with VMware 7.1.3 operational.
Thanks for the conversations and Merry Christmas to all,
Chuck
They have in the latest versions (>=7.1 AFAIK) some of use still run old
versions, even the latest 6.5.5 released a few weeks ago wasn’t fixed.
Vmware Server won’t be either. I think the push is for ESXi nowdays.
But for me, 6.5.5 does all I need, just needs patching.
> 1. cd /usr/src/linux
> 2. make cloneconfig <<---- this was the problem. The zcat
> “fixed” it.?.?
A cloneconfig is the same as the zcat (it is part of the procedure) if the
sources tree is the exact same version than the running kernel. But
cloneconfig does more, it can adapt for different versions (how different I
don’t know; I think it gives the default answer when a setting does not
exist). It is a suse addition, I understand, so you should report this
problem in a bugzilla or ask in the factory mail list - I’m afraid that the
devs don’t lurk in the forum.
> 3. make prepare
> 4. make modules
>
> There are those who claim the above is not necessary. However, every
> time I have encountered problems, performing all three operations above
> seemed to be the cure.
Without #4, yes. That step should not be necessary if you just want to
install vmware. Actually, I do:
make cloneconfig && make scripts && make prepare
as a previous step before attempting to install vmware. But I haven’t tried
11.3 nor 11.4
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
I just experienced this error in slightly different circumstances and this is the only google hit so I thought I’d ask here to see if anybody has discovered anything else
/usr/src/linux # ls -ld ../linux
lrwxrwxrwx 1 root root 15 Jan 25 23:43 ../linux -> linux-2.6.37-41
/usr/src/linux # make clean
/usr/src/linux # make cloneconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
Cloning configuration file /proc/config.gz
scripts/kconfig/conf: invalid option -- 'D'
See README for usage info
make[1]: *** [cloneconfig] Error 1
make: *** [cloneconfig] Error 2
I’m trying to compile the HEAD kernel on a box running 11.2, prior to modifying the kernel to investigate a hardware issue.
# uname -a
Linux piglet 2.6.37-41-desktop #1 SMP PREEMPT 2011-01-22 00:41:44 +0100 x86_64 x86_64 x86_64 GNU/Linux
So if anybody knows anything, I’d appreciate it.
If not, is the factory mail list appropriate, given I’m running 11.2? Or would the opensuse-kernel list be more appropriate?
@djh-novell - Hi there and welcome to our forum. Now then, I have had problems with various versions with kernel compiles mainly cause of module builds — nVidia Driver and VMware. Rather than go into a lengthy reply here on the forum I would like to direct to my Website and all the info that I have collected. For your particular version please visit: SuSE 11.2
There is also another version of this that is referenced in the beginning. Between the two of them you should be able to get enough info to compile your kernel.
Take care and have fun,
Chuck
Thanks for your reply. I reported my “scripts/kconfig/conf: invalid option – ‘D’” problem on the opensuse-kernel list today and got a swift response to say that it was a bug in the script that would be fixed (only --long-option-names are now allowed). So that will solve the problem in time and meanwhile the zcat workaround got me moving again.
I’ll be sure to look at your site to see what else I can learn.
