Re: [newbie] This is friggin stupid!
On Sun, 22 Oct 2000, you wrote: update on 2.3.4 -- managed to get sound working for my SB card but I still can't get anything happening with the Turtle Beach card. Anyone have any ideas? -- Mark I use a TB Montego II, and have sucessfully with the 2.2.14, 2.2.15 and 2.2.16 Kernels. I don't use the Aureal drivers, I use BOFH's tweaked drivers downloaded from here: http://www.geocities.com-bofh_666-aureal.html I/ve followed his directions to the letter and its always worked great (Clapton's turning on the CD right now). Hope this helps, eryl
Re: [newbie] This is friggin stupid!
O my gawd John! that was a good one! ROTFL -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Mon, 23 Oct 2000 1:04pm ,John Rye spake passionately in a message: Mark Weaver wrote: John, I get the impression that there was a lot I was doing wrong in the configuring of the kernel before compiling it. Most of the problems though centered around configuring for sound and Network. I'm not too clear on why yet. With Kernel 2.4.0-test9 the biggest troubles were with getting iptables and net filters to configure correctly. Never was able to get them working right. With kernel 2.3.4 I can't get the sound configured at all. Everything else works though including ipchains. I really wanna hear what this Turtle Beach sound card sounds like. Reminds me: What do call a turtle without a shell?? Dead!! -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Mon, 23 Oct 2000 4:03am ,John Rye spake passionately in a message: Mark Weaver wrote: Larry...John...Lonny and others, I've done it! I managed to get Linux-2.4-test9 to compile and work! It's running at the moment and it took a few times round and round to get TCP/IP and PPP to work, but by God it's working. Now I'm curious to see if I can get this Turtle Beach sound card working on here which was the original reason I started on this adventure in the first place. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Thu, 19 Oct 2000 1:37pm ,John Rye spake passionately in a message: [EMAIL PROTECTED] wrote: Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory snip Did you download the matching kernal-headers? I had something similar when I attempted my first kernal compile on 2.2.16 from a tarball. Cheers Did you establish what the problem was? Something missing? Malformed?
Re: [newbie] This is friggin stupid!
Mark Weaver wrote: Larry...John...Lonny and others, I've done it! I managed to get Linux-2.4-test9 to compile and work! It's running at the moment and it took a few times round and round to get TCP/IP and PPP to work, but by God it's working. Now I'm curious to see if I can get this Turtle Beach sound card working on here which was the original reason I started on this adventure in the first place. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Thu, 19 Oct 2000 1:37pm ,John Rye spake passionately in a message: [EMAIL PROTECTED] wrote: Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory snip Did you download the matching kernal-headers? I had something similar when I attempted my first kernal compile on 2.2.16 from a tarball. Cheers Did you establish what the problem was? Something missing? Malformed? -- ICQ# 89345394 Mailto: [EMAIL PROTECTED] "The number of UNIX installations has grown to 10, with more expected" (The UNIX Programmer's Manual, 2nd Edition, June 1972.)
Re: [newbie] This is friggin stupid!
John, I get the impression that there was a lot I was doing wrong in the configuring of the kernel before compiling it. Most of the problems though centered around configuring for sound and Network. I'm not too clear on why yet. With Kernel 2.4.0-test9 the biggest troubles were with getting iptables and net filters to configure correctly. Never was able to get them working right. With kernel 2.3.4 I can't get the sound configured at all. Everything else works though including ipchains. I really wanna hear what this Turtle Beach sound card sounds like. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Mon, 23 Oct 2000 4:03am ,John Rye spake passionately in a message: Mark Weaver wrote: Larry...John...Lonny and others, I've done it! I managed to get Linux-2.4-test9 to compile and work! It's running at the moment and it took a few times round and round to get TCP/IP and PPP to work, but by God it's working. Now I'm curious to see if I can get this Turtle Beach sound card working on here which was the original reason I started on this adventure in the first place. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Thu, 19 Oct 2000 1:37pm ,John Rye spake passionately in a message: [EMAIL PROTECTED] wrote: Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory snip Did you download the matching kernal-headers? I had something similar when I attempted my first kernal compile on 2.2.16 from a tarball. Cheers Did you establish what the problem was? Something missing? Malformed?
Re: [newbie] This is friggin stupid!
update on 2.3.4 -- managed to get sound working for my SB card but I still can't get anything happening with the Turtle Beach card. Anyone have any ideas? -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Sun, 22 Oct 2000 3:54pm ,Mark Weaver spake passionately in a message: John, I get the impression that there was a lot I was doing wrong in the configuring of the kernel before compiling it. Most of the problems though centered around configuring for sound and Network. I'm not too clear on why yet. With Kernel 2.4.0-test9 the biggest troubles were with getting iptables and net filters to configure correctly. Never was able to get them working right. With kernel 2.3.4 I can't get the sound configured at all. Everything else works though including ipchains. I really wanna hear what this Turtle Beach sound card sounds like.
Re: [newbie] This is friggin stupid!
Larry...John...Lonny and others, I've done it! I managed to get Linux-2.4-test9 to compile and work! It's running at the moment and it took a few times round and round to get TCP/IP and PPP to work, but by God it's working. Now I'm curious to see if I can get this Turtle Beach sound card working on here which was the original reason I started on this adventure in the first place. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Thu, 19 Oct 2000 1:37pm ,John Rye spake passionately in a message: [EMAIL PROTECTED] wrote: Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory snip Did you download the matching kernal-headers? I had something similar when I attempted my first kernal compile on 2.2.16 from a tarball. Cheers
Re: [newbie] This is friggin stupid!
Hi Larry, As to which install I'm running. I'm running the expert-developer-got-everything-including-the-sink-and-my-wifes-purse install. The really annoying this is that the files that is says it can't find are ones that "are" there and are in the src dir's that come with the kernel. They "are" part of the kernel source code. I'm not sure which compiler it is as far as version goes. And I didn't compile Quanta. I downloaded the RPM and installed that way, however I've never had any troubles comiling and instaling applications. Only kernels. This one is about to be demoted, however, to a lowly, bowl-cleaning private last class if things don't soon straighten out. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Wed, 18 Oct 2000 4:27pm ,Larry Marshall spake passionately in a message: Is there a compilable kernel anywhere on this planet that will not bail What compiler are you using Mark? You recommended that I download Quanta and I did. The compile blew up telling me that I don't have iostream (that's how I realized that I don't have the basic C++ library). I've noticed that these were added to 2.95-2 (I think that's the one). I'm assuming you had no such compile problems so I wonder why. In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory Looks to me that this is the beginning of the fall. The question is why you don't have that. I just checked it and I've got it from a standard 7.1 developer install. You aren't using 2.96 are you? It's available, RedHat's included it in their v7.0, but it won't compile the supplied kernel code. cp loop.o nbd.o rd.o /lib/modules/2.4.0-test9/kernel/drivers/block/ cp: loop.o: No such file or directory cp: nbd.o: No such file or directory cp: rd.o: No such file or directory So where are they? Have they been compiled or did their compile fail too? Wish I could help but I haven't played with rebuilding the Linux kernel. Cheers --- Larry
Re: [newbie] This is friggin stupid!
Hi Lonny, Attached to this message are the results of the search for the "errno.h" file -- I did try to paste them into this message, but that wasn't happening. Thank you though for taking the time. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Wed, 18 Oct 2000 2:47pm ,[EMAIL PROTECTED] spake passionately in a...: Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory make: *** [scripts/split-include] Error 1 make -C kernel modules_install make[1]: Entering directory `/usr/src/linux-2.4.0-test9/kernel' make[1]: Nothing to be done for `modules_install'. make[1]: Leaving directory `/usr/src/linux-2.4.0-test9/kernel' make -C drivers modules_install make[1]: Entering directory `/usr/src/linux-2.4.0-test9/drivers' make -C acpi modules_install make[2]: Entering directory `/usr/src/linux-2.4.0-test9/drivers/acpi' make[2]: Nothing to be done for `modules_install'. make[2]: Leaving directory `/usr/src/linux-2.4.0-test9/drivers/acpi' make -C block modules_install make[2]: Entering directory `/usr/src/linux-2.4.0-test9/drivers/block' mkdir -p /lib/modules/2.4.0-test9/kernel/drivers/block/ cp loop.o nbd.o rd.o /lib/modules/2.4.0-test9/kernel/drivers/block/ cp: loop.o: No such file or directory cp: nbd.o: No such file or directory cp: rd.o: No such file or directory make[2]: *** [_modinst__] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.0-test9/drivers/block' make[1]: *** [_modinst_block] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.0-test9/drivers' make: *** [_modinst_drivers] Error 2 [root@epix mdw1982]# find / -name errno.h /mnt/win_c/tcwin/include/errno.h find: /proc/6/fd: Permission denied /usr/include/bits/errno.h /usr/include/errno.h /usr/include/sys/errno.h /usr/src/linux-2.2.16/include/asm-i386/errno.h /usr/src/linux-2.2.16/include/linux/errno.h /usr/src/linux-2.2.17/include/linux/errno.h /usr/src/linux-2.2.17/include/asm-i386/errno.h /usr/src/linux-2.2.17/include/asm-mips/errno.h /usr/src/linux-2.2.17/include/asm-alpha/errno.h /usr/src/linux-2.2.17/include/asm-m68k/errno.h /usr/src/linux-2.2.17/include/asm-sparc/errno.h /usr/src/linux-2.2.17/include/asm-ppc/errno.h /usr/src/linux-2.2.17/include/asm-sparc64/errno.h /usr/src/linux-2.2.17/include/asm-arm/errno.h /usr/src/linux-2.2.17/include/asm-s390/errno.h /usr/i586-glibc20-linux/include/errno.h /usr/i586-glibc20-linux/include/linux/errno.h /usr/i586-glibc20-linux/include/sys/errno.h
Re: [newbie] This is friggin stupid!
John, I was under the assumption that when you download any tarball that everything you need to compile the program, other than the standard C, and C++ libraries are included with the rest of the source code. Otherwise I would have grabbed the RPM. I didn't get the RPM because I wanted just to recompile to allow for a different sound card and installing a kernel from an RPM can get a little messy. Whereas booting a kernel that has been compiled is much cleaner and offers far more control over it and the system. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Thu, 19 Oct 2000 1:37pm ,John Rye spake passionately in a message: [EMAIL PROTECTED] wrote: Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory snip Did you download the matching kernal-headers? I had something similar when I attempted my first kernal compile on 2.2.16 from a tarball. Cheers
Re: [newbie] This is friggin stupid!
Mark Weaver wrote: John, I was under the assumption that when you download any tarball that everything you need to compile the program, other than the standard C, and C++ libraries are included with the rest of the source code. Otherwise I would have grabbed the RPM. I didn't get the RPM because I wanted just to recompile to allow for a different sound card and installing a kernel from an RPM can get a little messy. Whereas booting a kernel that has been compiled is much cleaner and offers far more control over it and the system. -- Mark /* I never worry about the to-jams. * Once I've stuck my foot in my mouth * it's already too late...just make sure * you chew them thoroughly before swallowing! */ Registered Linux user #182496 * Pine 4.21 * On Thu, 19 Oct 2000 1:37pm ,John Rye spake passionately in a message: [EMAIL PROTECTED] wrote: Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory snip Did you download the matching kernal-headers? I had something similar when I attempted my first kernal compile on 2.2.16 from a tarball. Cheers I agree that all should be there in the tarball as well, I don't remember which files the complier couldn't locate nor which files had the 'funny' missing character errors, as I said earlier I hunted thru the files referenced but couldn't see where the error was coming from. Bearing mind that it's more than 10 years since I did any C programming, it probably something very obvious to someone else. I think that what got to me most was the errors appeared to be random from one run to the next. I was attempting 2.2.17 - just wouldn't go so pulled 2.2.16 down and tried that. For what ever reason - it worked!! Sorry mate - I don't have an answer, Maybe you need to throw this one into the expert list? Cheers -- ICQ# 89345394 Mailto: [EMAIL PROTECTED] "The number of UNIX installations has grown to 10, with more expected" (The UNIX Programmer's Manual, 2nd Edition, June 1972.)
Re: [newbie] This is friggin stupid!
Is there a compilable kernel anywhere on this planet that will not bail What compiler are you using Mark? You recommended that I download Quanta and I did. The compile blew up telling me that I don't have iostream (that's how I realized that I don't have the basic C++ library). I've noticed that these were added to 2.95-2 (I think that's the one). I'm assuming you had no such compile problems so I wonder why. In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory Looks to me that this is the beginning of the fall. The question is why you don't have that. I just checked it and I've got it from a standard 7.1 developer install. You aren't using 2.96 are you? It's available, RedHat's included it in their v7.0, but it won't compile the supplied kernel code. cp loop.o nbd.o rd.o /lib/modules/2.4.0-test9/kernel/drivers/block/ cp: loop.o: No such file or directory cp: nbd.o: No such file or directory cp: rd.o: No such file or directory So where are they? Have they been compiled or did their compile fail too? Wish I could help but I haven't played with rebuilding the Linux kernel. Cheers --- Larry
Re: [newbie] This is friggin stupid!
Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory make: *** [scripts/split-include] Error 1 make -C kernel modules_install make[1]: Entering directory `/usr/src/linux-2.4.0-test9/kernel' make[1]: Nothing to be done for `modules_install'. make[1]: Leaving directory `/usr/src/linux-2.4.0-test9/kernel' make -C drivers modules_install make[1]: Entering directory `/usr/src/linux-2.4.0-test9/drivers' make -C acpi modules_install make[2]: Entering directory `/usr/src/linux-2.4.0-test9/drivers/acpi' make[2]: Nothing to be done for `modules_install'. make[2]: Leaving directory `/usr/src/linux-2.4.0-test9/drivers/acpi' make -C block modules_install make[2]: Entering directory `/usr/src/linux-2.4.0-test9/drivers/block' mkdir -p /lib/modules/2.4.0-test9/kernel/drivers/block/ cp loop.o nbd.o rd.o /lib/modules/2.4.0-test9/kernel/drivers/block/ cp: loop.o: No such file or directory cp: nbd.o: No such file or directory cp: rd.o: No such file or directory make[2]: *** [_modinst__] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.0-test9/drivers/block' make[1]: *** [_modinst_block] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.0-test9/drivers' make: *** [_modinst_drivers] Error 2
Re: [newbie] This is friggin stupid!
[EMAIL PROTECTED] wrote: Is there a compilable kernel anywhere on this planet that will not bail on your with a ridiculous error making it impossible to update or recompile your kernel in any manner? Below is the result of my latest attempt to configure and compile a linux kernel. This one is 2.4.0-test9. Frankly I'm beginning to think its a lost stinkin cause. sincerely fed up and frustrated, Mark Ummmok first you are going to have to do some digging to find out what you need for the header/include files you are missing OR if you have them ... check to see where the current tree (for the compile) is looking for them. Can you send the output from a find / -name errno.h none of what you have posted is *post* compilation and it looks like it couldn't create the .o files to link in in order to continue. Compiling isn't always as easy as "./configure, make, make install" ;-) or make make bzImage make dep make modules etc etc, trouble shoot this first by figuring out where the missing includes are or if you have them "usr/include/bits/errno.h:25: linux/errno.h: No such file or directory" (you may have to look in the Makefile(s) to see what the root dir is in order to find out "where" it thinks linux/errno.h is or what linux actually is pointing to ... its usually a sym link to the CURRENT kernel source ls -l should be pretty easy to work from there =o) -Lonny + In file included from /usr/include/errno.h:36, from scripts/split-include.c:26: /usr/include/bits/errno.h:25: linux/errno.h: No such file or directory snip Did you download the matching kernal-headers? I had something similar when I attempted my first kernal compile on 2.2.16 from a tarball. Cheers -- ICQ# 89345394 Mailto: [EMAIL PROTECTED] "The number of UNIX installations has grown to 10, with more expected" (The UNIX Programmer's Manual, 2nd Edition, June 1972.)
