-----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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Does anyone know of a Suse kernel-source build that will actually compile?
and the relation to KDE is which? besides that both KDE and KERNEL begin with the letter K? you'd better try the general suse list... bye, [MH]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for your generous and kindhearted advice. But that list is unusable due to its volume, for mere mortals. Result is all questions, and no answers. The system needs to be adjusted, and this is a symptom. So can anyone actually advise? On Tuesday, 08 October 2002 8:27, Mathias Homann wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Does anyone know of a Suse kernel-source build that will actually compile?
and the relation to KDE is which? besides that both KDE and KERNEL begin with the letter K?
you'd better try the general suse list...
bye, [MH] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj2i33UACgkQnQ18+PFcZJueKwCfcEUuj1i5dvj/hFJIu1UuoUiX KxIAn2H4om908mxzi+K1yzXHgveOE+zH =VfXR -----END PGP SIGNATURE-----
Many, many questions are answered each day on the general list, it's a matter of patience sifting through them. I use Ximian Evolution with filters, and the list hasn't failed me yet. Your kernel problem could probably be answered by one of the gurus there. My only suggestion is you head over to http://kernel.org/ and get 2.4.19 and try using that one. It's supposedly better, but gives trouble with Nvidia drivers. You could also try changing around settings during kernel setup, I fiddled around with mine when it didn't compile and then all of a sudden it did. Matthew On Tue, 2002-10-08 at 09:36, Carl wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for your generous and kindhearted advice. But that list is unusable due to its volume, for mere mortals. Result is all questions, and no answers. The system needs to be adjusted, and this is a symptom. So can anyone actually advise? On Tuesday, 08 October 2002 8:27, Mathias Homann wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Does anyone know of a Suse kernel-source build that will actually > > compile? > > and the relation to KDE is which? besides that both KDE and KERNEL begin > with the letter K? > > you'd better try the general suse list... > > > bye, > [MH] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2i33UACgkQnQ18+PFcZJueKwCfcEUuj1i5dvj/hFJIu1UuoUiX KxIAn2H4om908mxzi+K1yzXHgveOE+zH =VfXR -----END PGP SIGNATURE----- -- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 08 October 2002 2:06, Matthew Kennedy wrote:
Many, many questions are answered each day on the general list, it's a matter of patience sifting through them. I use Ximian Evolution with filters, and the list hasn't failed me yet. Your kernel problem could probably be answered by one of the gurus there.
Good to know questions are being answered now. But as to filtering, I object on philisophical grounds, the demanding of hundreds of emails each day, then elimination of 95% of them without reading. Poor bandwidth ecology. The real solution is splitting up the main list. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2jRUoACgkQnQ18+PFcZJtWZACdHehW/BlyDIle8Pz4z9iLLxSJ l3YAn3MDCvc35vjGz8aek7eOREMvO74K =RlcW -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's failing on umem, which I suspect is the upper-memory driver. I do have High Memory turned off in the config, in order to enable VMware, and this is necessary. Maybe related to umem? Also, since running a compiled kernel I've lost PCMCIA. Must this package be recompiled, as well as Alsa? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2i4FEACgkQnQ18+PFcZJsncACeMjJNmGLH53Xgzign6PJlgLhO wIYAn0IQKaXueO8XqbMYgq4nxrHj4Lnj =LnUA -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's another example, my old pal, "yacc: Command not found": make[2]: Leaving directory `/usr/src/linux-2.4.18.SuSE/drivers/pnp' make -C scsi modules make[2]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/scsi' make -C aic7xxx modules make[3]: Entering directory `/usr/src/linux-2.4.18.SuSE/drivers/scsi/aic7xxx' 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 make[4]: yacc: Command not found make[4]: *** [aicasm_gram.h] Error 127 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 # -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2i+fcACgkQnQ18+PFcZJskGwCeKBwzezExJdWGN+gZ1zbA7n02 M3cAoICyPx25tIL3Lubb7NWMei/zGNqJ =CAcS -----END PGP SIGNATURE-----
* Carl (quantum@ultra2k.com) [021008 08:31]:
Here's another example, my old pal, "yacc: Command not found":
So install yacc or don't try to rebuild the aic7xxx firmware. As Mathias already said, this really belongs on the general lists. -- -ckm
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.
-----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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
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 #
See above, where it says
gcc -I/usr/include -I. -ldb ?
This is constructed from the Makefile in /usr/src/linux-2.4.18.SuSE/drivers/scsi/aic7xxx/aicasm If that is changed to a file that actually =exists=, like /usr/lib/libdb2.a (-ldb2) then it works. So, a problem in the 'dep' script. Not my fault, dammit! I'm simply doing more than most. Still haven't figured out the 1394 driver problem, and don't have time for it. Obviously: - - no checks are made before .rpm's are posted, and - - no users are =actually compiling= the kernel. This is kernel-source.SuSE-91 . -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj2lySwACgkQnQ18+PFcZJtS6gCeMfK030yAgjl8F92JIpWUb753 ezIAnjszZuWCSeYZ4uNj/loNt8L7gxen =l+sC -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Even if I think too you're posting the question in the wrong list, I have troubles updating some packages in the past (I've been using SuSE since the 5.x releases), and since then I've been updating by hand. I use now the 2.4.19 kernel, but got it from kernel.org (.tar.gz) not from SuSE. My distro was a 7.2, but now is simmilar to the 8.0 in the versions. It compiles correctly (I use some AIC drivers for my server and the workstation) and the unique trouble I've was with the drm module. I had to update to drm module from XFree and install it manually. Now, I've available every extension from Xfree 4.2.0 available (even render for antialiasing) and 3D hardware support (some other people has troubles with it with SuSE's packages, who disables it by default). I upgrade also KDE3 from the sources by recompiling,or from binaries from kde.org, not SuSE, YoU, YasT, etc. the same for windowmaker and some other packages. This helps me to maintain a strict control of versions and apps, since I don't like any system maintained by some type of mega-ultra-intelligent updater. Regards Alberto Curro El Jue 10 Oct 2002 20:38, Carl escribió:
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 #
See above, where it says
gcc -I/usr/include -I. -ldb ?
This is constructed from the Makefile in /usr/src/linux-2.4.18.SuSE/drivers/scsi/aic7xxx/aicasm
If that is changed to a file that actually =exists=, like /usr/lib/libdb2.a (-ldb2) then it works. So, a problem in the 'dep' script. Not my fault, dammit! I'm simply doing more than most.
Still haven't figured out the 1394 driver problem, and don't have time for it.
Obviously: - no checks are made before .rpm's are posted, and - no users are =actually compiling= the kernel.
This is kernel-source.SuSE-91 . -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iD8DBQE9pdNlmTqFb1DS57wRApo2AKC87YuwBez9AaYOOXi7kx+Zm2MH6gCg6zCB zhnmdN28oM3SmW0UvzJoG8c= =Qak2 -----END PGP SIGNATURE-----
participants (6)
-
Alberto Curro -
Carl -
Christopher Mahmood -
James Mohr -
Mathias Homann -
Matthew Kennedy