-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 08 October 2002 16:03, James Mohr wrote:
Carl,
Perhaps the reason people are not willing to help is two fold. First, ...
Thanks, but a lecture was not necessary.
Curiously enough when I just did a search on google for "make[4]: yacc: Command not found" there were a number of hits. Some with almost cut-n-paste copies of the text you provided. The solution? INSTALL YACC!
Yes, Christopher told me this offline. I thought "yacc" was gibberish, or a corruption of gcc. Now I know.
Based on the problems you seem to be having, it appears as if you have a non-standard installation.
No. Standard Suse8. I'm very conservative with software I install.
but yacc is there. So, why isn't it on your system? Did whoever install the system think yacc wasn't necessary?
I don't know. I did the install; and had never heard of yacc, and no, I don't know WTF it is.
Unless I am mistaken, Error 1 is "Operation not permitted", could it be you do not have write permission on a directory or some file that you need to? Is the rebuild being done as root?
Done as root, on a fresh install of kernel-source, after make mrproper .
It is not a VMware problem. As I wrote this post, I reinstalled VMWare 3.2.0 , having had to re-install the entire OS a couple of weeks ago. There was no kernel re-build required and VMware started with no errors and without having to reboot. It is specific to your system. A requirement that high memory be turned off is new to me. I am not denying it, just it is new. However, I have not changed my kernel and VMware works like it always did.
Glad it works for you. But VMware hasn't worked for me since build 55; dies trying to allocate upper memory on Power-On. All over Google are complaints about Suse over this. Does no one here know? No one run newest VMware? The issue is a new patch Suse put in to allow kernel use of high memory, for the first time. VMware expects to be able to use this area though, and croaks. Suse recommends turning off all but 850M of memory, but this doesn't work for half the people, including me. Until VMware adjusts to this paradigm (if they do), the only solution (that actually works) is to TURN OFF High Memory Support in the kernel. In order to do this, one must recompile. I am struggling to stay with the official Suse kernel, but seem to be failing. It irks me, when I help and answer questions for others on this list, and then when I have a question, get all kinds of crap. Reflects badly on everyone, and discourages me from helping is all it does.
After installing the kernel source from the CD, I do not have a directory kernel-source. How did you install the kernel source? From where? BTW use the directory /usr/src/linux for the rebuild.
The package kernel-source is what provides /usr/src/linux . But there seems to be an entirely alternative kernel source package, linux. No explanation. Thus the question.
Have you tried rebuilding the kernel with "make clean; make dep; make"? Do you get the same error?
I always: make mrproper make bzImage make install make modules <--Never get past here make modules-install repeat The error I get is consistent no matter how many times I compile. As I turn off one problem module, I then get another. Into xconfig I load /boot/vmlinuz.config then make changes, such as turning off himem, Save & Exit. Is anyone else here compiling their kernel?
Have you tried removing and reinstalling the kernel source and then trying the rebuild again? Installing the kernel source on my system (8.0 with the online updates) does **not** conflict with anything.
At least 5 times. rpm -e kernel-source and rpm -Uvh kernel-source* . The conflict is when you install kernel-source and THEN linux. Does not want to install linux, due to conflict. The description of linux in Yast2 is that it is the REST of the kernel sources. So I'm asking, "If it is the rest of the sources why do the releases on FTP right now, conflict? If linux is not the rest of the sources, then what's the distinction between kernel-source and linux?"
What is non-standard about your system?
It's an IBM Thinkpad A22p. Nothing odd about it. Don't think it can be blamed on me.
What else what not installed (other than yacc) when you installed the system originally? A fresh install of the source on my system works fine, none of the problems you describe. What is different about your system from a standard install?
I wish I knew. The 1394 driver problem is a mystery, so I had to turn it off (though I need it). Now past that, I get: make -C aicasm make[4]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/scsi/aic7xxx/aicasm' yacc -d -b aicasm_gram aicasm_gram.y mv aicasm_gram.tab.c aicasm_gram.c mv aicasm_gram.tab.h aicasm_gram.h yacc -d -b aicasm_macro_gram -p mm aicasm_macro_gram.y mv aicasm_macro_gram.tab.c aicasm_macro_gram.c mv aicasm_macro_gram.tab.h aicasm_macro_gram.h lex -oaicasm_scan.c aicasm_scan.l lex -Pmm -oaicasm_macro_scan.c aicasm_macro_scan.l gcc -I/usr/include -I. -ldb aicasm.c aicasm_symbol.c aicasm_gram.c aicasm_macro_gram.c aicasm_scan.c aicasm_macro_scan.c -o aicasm /usr/i486-suse-linux/bin/ld: cannot find -ldb collect2: ld returned 1 exit status make[4]: *** [aicasm] Error 1 make[4]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/scsi/aic7xxx/aicasm' make[3]: *** [aicasm/aicasm] Error 2 make[3]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/scsi/aic7xxx' make[2]: *** [_modsubdir_aic7xxx] Error 2 make[2]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/scsi' make[1]: *** [_modsubdir_scsi] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers' make: *** [_mod_drivers] Error 2 hydra:/usr/src/linux # Which blimey, doesn't make sense. Another driver I need, but fails. So you're saying that you are actually running Suse8 and the latest kernel from binary rpm? Plus VMware? That should not be possible, according to newsgroups. I'm trying to use Linux in a business. Is this my real mistake? I was made lots of promises. Tell me now Suse... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2jULwACgkQnQ18+PFcZJvFXgCdEprncS2wSw9SpHjt1LJBpc+j a3IAnRsFYPvElUdq9kW8CB9668DHoueD =uVEz -----END PGP SIGNATURE-----