Re: Help compiling my kernel
1) I would really rather not have to go through the config process - it is my hope that I can use the standard .config file with a few modifications - in particular, sound and APM enabled. Can't I just use the standard .config file, modify a few things via an editor, and use it to recompile my kernel? If I do this, can I skip the make menuconfig step? I can't see *why* you want to skip menuconfig - it isn't that hard. Sure - there may be lots and lots of settings in menuconfig that you don't know how to use - simply don't change them! Just modify the sound settings and APM, nothing else. Using an editor is definitely harder - it is possible to make typo's, you can select incompatible options that menuconfig would complain about, and there is no help. Menuconfig has help for almost all items, sometimes with references to more detailed documentation. Menuconfig is as good as any editor - even for making just a few changes. The sections you don't touch won't be messed up in any way. Make a backup of the original .config to be on the safe side. Helge Hafting
Help compiling my kernel
I need some help compiling my kernel: 1) I would really rather not have to go through the config process - it is my hope that I can use the standard .config file with a few modifications - in particular, sound and APM enabled. Can't I just use the standard .config file, modify a few things via an editor, and use it to recompile my kernel? If I do this, can I skip the make menuconfig step? Further, I unpacked my kernel-source package, but it doesn't contain a .config file, however it does contain .config.save. Can I rename it to .config and use it? 2) After I compile my kernel, say I decide to change a few things in the source - is there a need to redo the make menuconfig step? Or does that strictly create the .config file? 3) I tried to make menuconfig, but got an error: rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts/lxdialog all make[1]: Entering directory 'usr/src/kernel-source-2.0.34/scripts/lxdialog' gcc -O2 -Wall -fomit-frame-pointer -DLOCALE -DCURSES_LOC=curses.h -c lxdialog.c -o lxdialog.o In file included from lxdialog.c:22: dialog.h:29: curses.h: No such file or directory make[1]: *** [lxdialog.o] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.0.34/scripts/lxdialog' make: *** [menuconfig] Error 2 I'm guessing I need something like ncursesxxx-dev, right? How come this isn't in the dependencies of kernel-package? 4) According to the README in /usr/src/linux, I should link as follows: ln -s /usr/src/linux/include/asm-i386 /usr/include/asm ln -s /usr/src/linux/include/linux /usr/include/linux ln -s /usr/src/linux/include/scsi /usr/include/scsi Problem is, I have libc6 installed, and it is installed in /usr/include. Should I do the links as directed? Or will the libc6 stuff work? 5) I seem to have three different versions of the header files. Do I really need them all? I have: libc6 - /usr/include libc5-altdev- /usr/i486-linuxlibc1/include linux source- /usr/src/include 6) The kernel-package docs say I need to run: make-kpkg --rootcmd fakeroot version Do I need to do this if I compile as root? I don't have fakeroot - do I need it? Will su work instead? Thanks for any help.. -Jay
Re: Help compiling my kernel
Please correct/add ANYTHING in my answers. On Mon, Feb 01, 1999 at 10:16:12PM -0600, [EMAIL PROTECTED] wrote this: I need some help compiling my kernel: 1) I would really rather not have to go through the config process - it is my hope that I can use the standard .config file with a few modifications - in particular, sound and APM enabled. Can't I just use the standard .config file, modify a few things via an editor, and use it to recompile my kernel? If I do this, can I skip the make menuconfig step? I'd say it's always best to check all the configurations BUT if you like to edit .config i guess you should do a 'make mrproper' first to clean things and then a 'make config' and just press return 'til it's done. Then edit .config for to your liking. After you are done do a 'make dep' and 'make clean'. After that you should be able to compile, and possibly install if you like that, with 'make modules;make modules_install;make bzlilo' or just plain bzimage if youd like to install it manually. Further, I unpacked my kernel-source package, but it doesn't contain a .config file, however it does contain .config.save. Can I rename it to .config and use it? Since i don't know what the configure in that file looks like i can't advise you on that. Better do a make config instead. 2) After I compile my kernel, say I decide to change a few things in the source - is there a need to redo the make menuconfig step? Or does that strictly create the .config file? I'm not quite sure what menuconfig does except makes a new config. Don't see why it should be needed. 3) I tried to make menuconfig, but got an error: rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts/lxdialog all make[1]: Entering directory 'usr/src/kernel-source-2.0.34/scripts/lxdialog' gcc -O2 -Wall -fomit-frame-pointer -DLOCALE -DCURSES_LOC=curses.h -c lxdialog.c -o lxdialog.o In file included from lxdialog.c:22: dialog.h:29: curses.h: No such file or directory make[1]: *** [lxdialog.o] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.0.34/scripts/lxdialog' make: *** [menuconfig] Error 2 I'm guessing I need something like ncursesxxx-dev, right? How come this isn't in the dependencies of kernel-package? Yup..install libncurses-dev to get that file. And it's not in the dependency-list since you don't actually NEED it...it just make life easier to 'make menyconfig' than 'make config'. 5) I seem to have three different versions of the header files. Do I really need them all? I have: libc6 - /usr/include libc5-altdev - /usr/i486-linuxlibc1/include linux source - /usr/src/include When you look at the kernel-source-package it says that the kernel-headers don't need to be installed. They are provided by the kernel-source-package. 6) The kernel-package docs say I need to run: make-kpkg --rootcmd fakeroot version Do I need to do this if I compile as root? I don't have fakeroot - do I need it? Will su work instead? I haven't used kernel-package so i really can't tell. But fakeroot seems quite obsolete when compiling as root. Why make a package of it at all? 'make bzlilo' compiles and installes the needed files all by itself. G.L. // Marwin -- | Björn Elwhagen aka Marwin Finger [EMAIL PROTECTED] | | Student at Wexio University for PGP public key. | | SwedenICQ: 356095 |
Re: Help compiling my kernel
In a message dated 2/2/99 8:11:01 AM Central Standard Time, [EMAIL PROTECTED] writes: 5) I seem to have three different versions of the header files. Do I really need them all? I have: libc6 - /usr/include libc5-altdev - /usr/i486-linuxlibc1/include linux source - /usr/src/include When you look at the kernel-source-package it says that the kernel-headers don't need to be installed. They are provided by the kernel-source-package. Should have been more clear on this... The libc6-dev package installed headers into /usr/include. The licb5-altdev package installed headers into /usr/i486-linuxlibc1/include. the kernel-source package installed headers into /usr/src/include. I'm wondering if these are duplicates of each other. I imagine the libc5 stuff is old, the libc6 stuff replaced it - but is the kernel-source stuff the same as the libc6 stuff?
Re: Help compiling my kernel
Subject: Help compiling my kernel Date: Mon, Feb 01, 1999 at 11:12:38PM -0500 In reply to:[EMAIL PROTECTED] Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): I need some help compiling my kernel: 1) I would really rather not have to go through the config process - it is my hope that I can use the standard .config file with a few modifications - in particular, sound and APM enabled. Can't I just use the standard .config file, modify a few things via an editor, and use it to recompile my kernel? If I do this, can I skip the make menuconfig step? Sure you can, but I wouldn't. Read the top of /usr/src/linux/.config. # # Automatically generated by make menuconfig: don't edit # # config is boring, menuconfig is real easy, xconfig is easier. None of them are so hard that they should cause any concern. Try one of them and use the help feature. You can learn a lot. Further, I unpacked my kernel-source package, but it doesn't contain a .config file, however it does contain .config.save. Can I rename it to .config and use it? Don't know about config.save. Do an ls .config-save and see of the selections agree with those that you want. 2) After I compile my kernel, say I decide to change a few things in the source - is there a need to redo the make menuconfig step? Or does that strictly create the .config file? You know enough to change things in the _source_?? The config file ( created by the config process) tells the compile process ( which creates the kernel) what options you want in your kernel. 3) I tried to make menuconfig, but got an error: rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts/lxdialog all make[1]: Entering directory 'usr/src/kernel-source-2.0.34/scripts/lxdialog' gcc -O2 -Wall -fomit-frame-pointer -DLOCALE -DCURSES_LOC=curses.h -c lxdialog.c -o lxdialog.o In file included from lxdialog.c:22: dialog.h:29: curses.h: No such file or directory make[1]: *** [lxdialog.o] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.0.34/scripts/lxdialog' make: *** [menuconfig] Error 2 I'm guessing I need something like ncursesxxx-dev, right? How come this isn't in the dependencies of kernel-package? I'm not on my debian box right now but if you got kernel-source, kernel-headers and kernel-package, yes the dependencies should have got everything you needed, if you used deselect or apr-get to get those packages. If you went downloaded them yourself.? 4) According to the README in /usr/src/linux, I should link as follows: ln -s /usr/src/linux/include/asm-i386 /usr/include/asm ln -s /usr/src/linux/include/linux/usr/include/linux ln -s /usr/src/linux/include/scsi /usr/include/scsi Problem is, I have libc6 installed, and it is installed in /usr/include. Should I do the links as directed? Or will the libc6 stuff work? Yes, follow the readme. Take a look in /usr/include, there are a lof of things there. So what? 5) I seem to have three different versions of the header files. Do I really need them all? I have: libc6 - /usr/include libc5-altdev - /usr/i486-linuxlibc1/include linux source - /usr/src/include Only if you want the system to work. 6) The kernel-package docs say I need to run: make-kpkg --rootcmd fakeroot version Do I need to do this if I compile as root? I don't have fakeroot - do I need it? Will su work instead? Don't know about the --rootcmd as I always make new kernels as root and I don't have fakeroot either. Hope that answers your questions. Have you ever tried reading the Kernel-HOWTO?? HTH -- Using TSO is like kicking a dead whale down the beach. -- S. C. Johnson ___ Wayne T. Topa [EMAIL PROTECTED]
Re: Help compiling my kernel
[EMAIL PROTECTED] writes: | 4) According to the README in /usr/src/linux, I should link as follows: | | ln -s /usr/src/linux/include/asm-i386 /usr/include/asm | ln -s /usr/src/linux/include/linux /usr/include/linux | ln -s /usr/src/linux/include/scsi /usr/include/scsi | | Problem is, I have libc6 installed, and it is installed in /usr/include. | Should I do the links as directed? Or will the libc6 stuff work? | | Yes, follow the readme. Take a look in /usr/include, there are a lof | of things there. So what? No, I don't think this is true anymore. At some point I remember reading a post from Linus stating that doing the above steps could be harmful to your system since, presumably, libc was compiled with what's already in /usr/include and now you're wiping that with what's there for a particular kernel. This could cause a conflict between the kernel and libc, which is NOT a Good Thing (TM). He said the best thing to do was ignore the above and not make those particular symbolic links. I never have, and my kernels compile up and run fine. | 5) I seem to have three different versions of the header files. | Do I really | need them all? I have: | | libc6 - /usr/include | libc5-altdev- /usr/i486-linuxlibc1/include | linux source- /usr/src/include | | Only if you want the system to work. Hmm, is anything essential to Debian still linked against libc5? I'm not sure, but I don't think so. The only thing I remember in hamm requiring libc5 was netscape. That's not true in slink. Of course if you try to remove libc5 it'll tell you if anything you have depends on it. | 6) The kernel-package docs say I need to run: | | make-kpkg --rootcmd fakeroot version | | Do I need to do this if I compile as root? I don't have fakeroot | - do I need | it? Will su work instead? | | | Don't know about the --rootcmd as I always make new kernels as root | and I don't have fakeroot either. Hope that answers your questions. I'll second this. Never used fakeroot and have never had a problem. Gary
Re: Help compiling my kernel
Subject: Re: Help compiling my kernel Date: Tue, Feb 02, 1999 at 01:00:59PM -0700 In reply to:Gary L. Hennigan Quoting Gary L. Hennigan([EMAIL PROTECTED]): [EMAIL PROTECTED] writes: | 4) According to the README in /usr/src/linux, I should link as follows: | | ln -s /usr/src/linux/include/asm-i386 /usr/include/asm | ln -s /usr/src/linux/include/linux/usr/include/linux | ln -s /usr/src/linux/include/scsi /usr/include/scsi | | Problem is, I have libc6 installed, and it is installed in /usr/include. | Should I do the links as directed? Or will the libc6 stuff work? | | Yes, follow the readme. Take a look in /usr/include, there are a lof | of things there. So what? No, I don't think this is true anymore. At some point I remember reading a post from Linus stating that doing the above steps could be harmful to your system since, presumably, libc was compiled with what's already in /usr/include and now you're wiping that with what's there for a particular kernel. This could cause a conflict between the kernel and libc, which is NOT a Good Thing (TM). He said the best thing to do was ignore the above and not make those particular symbolic links. I never have, and my kernels compile up and run fine. Well I haven't done the link in a long while myself, on slackware or Debian, come to think of it. In fact the 2.2.0 kernel Readme no longer mentions it. Sorry about that. I was in a foul mood afer reading this list of questions. | 5) I seem to have three different versions of the header files. | Do I really | need them all? I have: | | libc6 - /usr/include | libc5-altdev - /usr/i486-linuxlibc1/include | linux source - /usr/src/include | | Only if you want the system to work. Hmm, is anything essential to Debian still linked against libc5? I'm not sure, but I don't think so. The only thing I remember in hamm requiring libc5 was netscape. That's not true in slink. Of course if you try to remove libc5 it'll tell you if anything you have depends on it. My thought here was that, based on the questions asked, that it was better to leave them in rather then get into it deeper. | 6) The kernel-package docs say I need to run: | | make-kpkg --rootcmd fakeroot version | | Do I need to do this if I compile as root? I don't have fakeroot | - do I need | it? Will su work instead? | | | Don't know about the --rootcmd as I always make new kernels as root | and I don't have fakeroot either. Hope that answers your questions. I'll second this. Never used fakeroot and have never had a problem. Gary -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- If a listener nods his head when you're explaining your program, wake him up. ___ Wayne T. Topa [EMAIL PROTECTED]
