[ALSA and Kernel] No version.h in mantel's kernel tarball?
Hello, Last night I went through the procedure of updating my kernel at home with mantel's kernel (no Internet connection available there, I downloaded the kernel here at work and took it home on a Zip). I made several test backups of my old kernel and I'm still able to boot my old kernel, as well as the new. Everything went perfect except mk_initrd (mk_initrd -k "vmlinuz-2.4.16" -i "initrd-2.4.16" -s auto does not work, even without the -s auto, until you cp vmlinuz vmlinuz-2.3.-16. I'm not sure if that's correct or not). Anyway... the reason I went through the upgrade (in addition to the learning experience) was so that I could compile the newest ALSA. oh, I should mention that after installing kernel RPMs I cd'd to /usr/src and untared mantel's source tar.bz2, and ran ln -s <whatever the dir name was> linux. i.e. ls /usr/src/linux now shows the contents for the untared mantel 2.4.16 source, like it should. However upon trying to run configure on ALSA, I get an error (I meant to bring the error message but I forgot it, sorry) saying that /usr/src/linux/include/linux/version.h is not found. I carefully looked in the directory it named and while there were a lot of other .h files in there, there was indeed no version.h . Can anyone explain this? I don't know what version.h is but it sounds major, I'm surprised it's not in the tarball. Do I need to make it somehow? ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
Hello,
Last night I went through the procedure of updating my kernel at home with mantel's kernel (no Internet connection available there, I downloaded the kernel here at work and took it home on a Zip).
I made several test backups of my old kernel and I'm still able to boot my old kernel, as well as
12/12/01 4:51:15 PM, JW <jw@centraltexasit.com> wrote: the new. Everything went perfect except mk_initrd (mk_initrd -k "vmlinuz-2.4.16" -i "initrd-2.4.16" - s auto does not work, even without the -s auto, until you cp vmlinuz vmlinuz-2.3.-16. I'm not sure if that's correct or not).
Anyway... the reason I went through the upgrade (in addition to the learning experience) was so
that I could compile the newest ALSA. oh, I should mention that after installing kernel RPMs I cd'd to /usr/src and untared mantel's source tar.bz2, and ran ln -s <whatever the dir name was> linux. i.e. ls /usr/src/linux now shows the contents for the untared mantel 2.4.16 source, like it should.
However upon trying to run configure on ALSA, I get an error (I meant to bring the error message
but I forgot it, sorry) saying that /usr/src/linux/include/linux/version.h is not found.
I carefully looked in the directory it named and while there were a lot of other .h files in there,
there was indeed no version.h .
Can anyone explain this? I don't know what version.h is but it sounds major, I'm surprised it's not
in the tarball.
Do I need to make it somehow?
---------------------------------------------------- Jonathan Wilson System Administrator
Try doing 'make dep' in /usr/src/linux beforehand. Tim Harrell <tim.harrell@ntlworld.com>
At 05:01 PM 12/12/2001 +0000, you wrote:
12/12/01 4:51:15 PM, JW <jw@centraltexasit.com> wrote:
Hello, However upon trying to run configure on ALSA, I get an error (I meant to bring the error message but I forgot it, sorry) saying that /usr/src/linux/include/linux/version.h is not found.
I carefully looked in the directory it named and while there were a lot of other .h files in there, there was indeed no version.h .
Can anyone explain this? I don't know what version.h is but it sounds major, I'm surprised it's not in the tarball.
Do I need to make it somehow?
---------------------------------------------------- Jonathan Wilson System Administrator
Try doing 'make dep' in /usr/src/linux beforehand.
Even though I did _not_ compile a new kernel (I used the binary RPM)?
Tim Harrell <tim.harrell@ntlworld.com>
---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
12/12/01 5:07:06 PM, JW <jw@centraltexasit.com> wrote:
At 05:01 PM 12/12/2001 +0000, you wrote:
12/12/01 4:51:15 PM, JW <jw@centraltexasit.com> wrote:
Hello, However upon trying to run configure on ALSA, I get an error (I meant to bring the error message but I forgot it, sorry) saying that /usr/src/linux/include/linux/version.h is not found.
I carefully looked in the directory it named and while there were a lot of other .h files in there, there was indeed no version.h .
Can anyone explain this? I don't know what version.h is but it sounds major, I'm surprised it's not in the tarball.
Do I need to make it somehow?
---------------------------------------------------- Jonathan Wilson System Administrator
Try doing 'make dep' in /usr/src/linux beforehand.
Even though I did _not_ compile a new kernel (I used the binary RPM)?
Yes. I had the same problem with modversions.h when I wanted to compile the nvidia drivers (before I'd ever compiled any kernel stuff and dealt solely with RPMs). The modversions.h was needed by the nvidia makefile but it only got created once I'd run a make modules in the source tree. You have a fresh source area so there's a good chance the same situation applies. Why not try it? You won't break anything! Tim Harrell <tim.harrell@ntlworld.com>
JW wrote:
At 05:01 PM 12/12/2001 +0000, you wrote:
12/12/01 4:51:15 PM, JW <jw@centraltexasit.com> wrote:
Hello, However upon trying to run configure on ALSA, I get an error (I meant to bring the error message but I forgot it, sorry) saying that /usr/src/linux/include/linux/version.h is not found.
I carefully looked in the directory it named and while there were a lot of other .h files in there, there was indeed no version.h .
Can anyone explain this? I don't know what version.h is but it sounds major, I'm surprised it's not in the tarball.
Do I need to make it somehow?
---------------------------------------------------- Jonathan Wilson System Administrator
Try doing 'make dep' in /usr/src/linux beforehand.
Even though I did _not_ compile a new kernel (I used the binary RPM)?
To successfully compile and install alsa you MUST have the kernel sources installed for the kernel you are RUNNING. Which means you must do a make dep in the kernel source tree. You should completly build and boot your kernel before you try to compile/install alsa. Regards Mark
At 02:21 PM 12/12/2001 -0500, you wrote:
JW wrote: To successfully compile and install alsa you MUST have the kernel sources installed for the kernel you are RUNNING. Which means you must do a make dep in the kernel source tree. You should completly build and boot your kernel before you try to compile/install alsa.
The kernel was installed, the sources untarred but make dep was NOT run, and I had rebooted. Compiling alsa did not work (make failed); more on that in a future message. Are you saying before I compile ALSA I'll have to reboot _after_ running make dep ?
Regards Mark
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
JW wrote:
At 02:21 PM 12/12/2001 -0500, you wrote:
JW wrote: To successfully compile and install alsa you MUST have the kernel sources installed for the kernel you are RUNNING. Which means you must do a make dep in the kernel source tree. You should completly build and boot your kernel before you try to compile/install alsa.
The kernel was installed, the sources untarred but make dep was NOT run, and I had rebooted. Compiling alsa did not work (make failed); more on that in a future message. Are you saying before I compile ALSA I'll have to reboot _after_ running make dep ?
If all you do is a make dep then the kernel you are running is NOT from the kernel sources you have installed. It MIGHT work but I personally would go through whole kernel build and install process then reboot. If all you do is make dep there is no need to reboot as all that does is setup your kernel source tree for a compile. When you build alsa it is going to expect a link from /lib/modules/"uname -r"/build to the actual kernel sources of the kernel YOU ARE CURRENTLY running. If you don't go ahead and build/install/boot that kernel before you build/install alsa your looking for trouble. Regards -- Mark Hounschell dmarkh@cfl.rr.com
On Wednesday 12 December 2001 23.32, Mark Hounschell wrote:
If all you do is a make dep then the kernel you are running is NOT from the kernel sources
But the sources in mantel's dir is the sources used to build the kernel in the rpm. I've always managed with make mrproper make cloneconfig #needed, since some module makefiles get info on how the kernel is configured from the .config make dep //Anders
On Wednesday 12 December 2001 17.51, JW wrote:
should mention that after installing kernel RPMs I cd'd to /usr/src and untared mantel's source tar.bz2, and ran ln -s <whatever the dir name was>
If you installed the kernel rpm, version.h is in /boot/vmlinuz.version.h, just as the "error message" says. mv /boot/vmlinuz.version.h /usr/src/linux/include/linux/version.h is all you need to do version.h is a small file (three lines) that holds the version info of the kernel. regards Anders
participants (5)
-
Anders Johansson -
JW -
Mark Hounschell -
Mark Hounschell -
Tim Harrell