Carl, Perhaps the reason people are not willing to help is two fold. First, it appears that you feel that either the SuSE mailing lists or SuSE itself are expected or even required to answer your questions. No one owes you an answer. Based on other posts, it does seem that other people have the same impressions, I do not think it is just my interpretation. I get frustrated sometimes when I post and the question is not answered. Sometimes I have to post multiple times before I get a response, but I certainly do not require anyone to answer. If this is required for some contract or assignment (if memory serves me correctly) then why not pay to get support? 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! (sorry for shouting). The answer from Alan Cox was "You chose to recompile the firmware ...on a box without the right tools installed." (Well Christopher didn't need Alan to tell him that!). Second, the KDE list was split away from the general list because the KDE issues were getting lost within the sheer volumn of general Linux issues, like kernel re-builds. So here you are insisting that this list that was **intentionally** split from the general list to talk **specifically** about the KDE now become a dumping ground for any and all subjects just because you **insist** because you don't want **your** message lost in the volume of posts on the general list. That annoys people because you obviously feel that you are not required to adher to the rules that the rest of us have agreed upon. Since SuSE is **paying** to run this list which we get to use for **free**, the very least we can do is have the necessary respect and adher to the rules they set down. One of which is NOT to post in the wrong places (like non-KDE issues here). Based on the problems you seem to be having, it appears as if you have a non-standard installation. In the many relinks I have done, I have never had a problem with it not finding yacc. I never even knew that yacc was required for a kernel rebuild. I did not install anything special, but yacc is there. So, why isn't it on your system? Did whoever install the system think yacc wasn't necessary? 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? 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. 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. Have you tried rebuilding the kernel with "make clean; make dep; make"? Do you get the same error? 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. What is non-standard about your system? 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? The problem appears to be specific to your system and is not a standard problem with either the kernel, the rebuild or VMware. Try and figure out what is different and why. Maybe that will give you some clues as to why you are having these problems and others are not. Regards, jimmo On Tuesday 08 October 2002 15:12, Carl wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Does anyone know of a Suse kernel-source build that will actually compile?
I need to experiment and try to get VMware running.
Build 2.4.18-91 fails as below, consistently. Earlier builds fail in different ways, one in 1394Lynx, and others, elsewhere. I had found one that actually compiled, but have lost track of it.
And while I'm at it, why are there two different source sets? (kernel-source and linux) Which one to use? And why does Yast say that linux is the REST of the source, when installing it conflicts with kernel-source?
make[2]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/block' gcc -D__KERNEL__ -I/usr/src/linux-2.4.18.SuSE/include -Wall - -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common - -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE - -DKBUILD_BASENAME=umem -c -o umem.o umem.c umem.c:136: field `tasklet' has incomplete type umem.c: In function `mm_start_io': umem.c:343: warning: right shift count >= width of type umem.c: In function `mm_unplug_device': umem.c:386: warning: implicit declaration of function `local_bh_disable' umem.c:388: warning: implicit declaration of function `local_bh_enable' umem.c: In function `mm_interrupt': umem.c:646: warning: implicit declaration of function `tasklet_schedule' umem.c: In function `mm_pci_probe': umem.c:1178: warning: implicit declaration of function `tasklet_init' umem.c: In function `mm_pci_remove': umem.c:1313: warning: implicit declaration of function `tasklet_kill' make[2]: *** [umem.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/block' make[1]: *** [_modsubdir_block] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers' make: *** [_mod_drivers] Error 2 hydra:/usr/src/linux # -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj2i2dwACgkQnQ18+PFcZJt89QCdEbGM3RN5Lo395JATLmTL3iGd e+4An08UqgYJUpFwbI8z8bBdoIA3NxMB =VXFB -----END PGP SIGNATURE-----
-- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info --------------------------------------- NOTE: All messages sent to me in response to my posts to newsgroups or forums are subject to reposting.