Penguin
Recent Changes

Differences between version 25 and predecessor to the previous major change of KernelNotes.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 25 Last edited on Sunday, May 28, 2006 12:36:44 pm by AristotlePagaltzis Revert
Older page: version 23 Last edited on Saturday, May 27, 2006 10:34:20 pm by AristotlePagaltzis Revert
@@ -1,60 +1,49 @@
-!!! Compile Problems  
+!!! Compiler Version  
  
-<pre>  
-__In file included from ide-cd.c:318:__  
-__ide-cd.h:440: error: long, short, signed or unsigned used invalidly for `slot_tablelen'__  
-</pre>  
-  
-This occurs if you're using a more recent compiler than the kernel can be compiled for, for example [GCC] 3 .x to compile a kernel ( kernels only work with < [GCC] 3) . If you want to use eg . <tt>gcc- 2.95</tt>, try:  
-  
-<verbatim>  
-make CC=gcc-2 .95 bzImage  
-</verbatim>  
-  
-In <tt>/usr/src/linux/ README</tt> (at least for kernel versions 2 .4 .x and below) you will find the following snippet : 
+The [Kernel] can be sensitive to the version of [GCC] in use. F.ex . 2.4 and early 2.6 kernels did not work with [GCC] 3.x . Versions 2.4 .x and below contain the following snippet in <tt>README</tt>, f .ex .: 
  
  <verbatim> 
  COMPILING the kernel: 
  
  - Make sure you have gcc 2.95.3 available. gcc 2.91.66 (egcs-1.1.2) may 
  also work but is not as safe, and *gcc 2.7.2.3 is no longer supported*. 
  </verbatim> 
  
-But of course you always read the compile instructions for software you download, right? :) 
+OTOH kernels since about 2.6.15 require [GCC] 3.x. Read the file to find the versions of compilers and other tools you need. Make sure to check the <tt>README</tt> and <tt>Documentation/Changes</tt> files to find out which version you need. Of course you always read the compile instructions for software you download, right? :) 
  
-!! Linking fails with bootsplash compiled into your kernel 
+To compile a kernel with a specific compiler, you can say eg. <tt>make CC=gcc-2.95 bzImage</tt> to make the <tt>bzImage</tt> target using the <tt>gcc-2.95</tt> compiler.  
  
-<verbatim>  
- LD .tmp_vmlinux1  
-drivers/built-in.o(.text+0xa898a): In function `splash_getraw':  
-: undefined reference to `con2fb_map'  
-drivers/built-in.o(.text+0xa918c): In function `splash_verbose':  
-: undefined reference to `con2fb_map'  
-drivers/built-in.o(.text+0xa9670): In function `splash_status':  
-: undefined reference to `con2fb_map'  
-drivers/built-in.o(.text+0xa97a4): In function `splash_read_proc':  
-: undefined reference to `con2fb_map'  
-drivers/built-in.o(.text+0xa997d): In function `splash_write_proc':  
-: undefined reference to `con2fb_map'  
-make: *** [.tmp_vmlinux1] Error 1  
-</verbatim>  
+!!! Linking fails with bootsplash compiled into your kernel  
  
-You need to have framebuffer console support compiled in. It can't be a module!  
+Compiling aborts with the following message:  
  
-Set <tt >CONFIG _FRAMEBUFFER _CONSOLE=y< /tt> in the <tt> .config </tt >.  
+ <verbatim >  
+ LD .tmp _vmlinux1  
+ drivers/built-in.o(.text+0xa898a): In function `splash _getraw':  
+ : undefined reference to `con2fb_map'  
+ drivers /built- in.o(.text+0xa918c): In function `splash_verbose':  
+ : undefined reference to `con2fb_map'  
+ drivers/built-in.o(.text+0xa9670): In function `splash_status':  
+ : undefined reference to `con2fb_map'  
+ drivers/built-in.o(.text+0xa97a4): In function `splash_read_proc':  
+ : undefined reference to `con2fb_map'  
+ drivers/built-in.o(.text+0xa997d): In function `splash_write_proc':  
+ : undefined reference to `con2fb_map'  
+ make: *** [.tmp_vmlinux1] Error 1  
+ </verbatim > 
  
-!!! Version 2 .6 series LinuxKernel notes  
+You need to have framebuffer console support compiled in. It can't be a module ! Set <tt>CONFIG_FRAMEBUFFER_CONSOLE=y</tt> in the <tt>.config</tt> . 
  
-!! ModuleInitTools 
+! !! ModuleInitTools 
  
 Starting with 2.5.51, modules have a different format. The extension has also changed from <tt>.o</tt> to <tt>.ko</tt>, for kernel object. To work with modules, you need a completely rewritten set of module tools (modprobe(8), insmod(8), lsmod(8)), collectively called <tt>module-init-tools</tt>. They can coexist with the 2.4.x-specific tools. __Note, however__ that <tt>module-init-tools</tt> no longer reads <tt>modules.conf</tt> and instead uses a new file called modprobe.conf(5) which has a different syntax. <tt>man 5 modprobe.conf</tt> will be your friend here. It's possible to set <tt>modprobe.conf</tt> to handle modules for both 2.4.x and 2.5.x kernels, which is pretty cool if you're a dual-booter. 
  
-!! Nvidia and 2.6 notes  
+!!! nVidia and on LinuxKernel 2.6 
  
-[NVIDIA drivers|http://www.nvidia.com/linux] version 1.-6106 and up support all 2.4 and 2.6 kernels, including kernels with the new 2.6 option for 4k stacks. 
+[nVidia drivers|http://www.nvidia.com/linux] version 1.-6106 and up support all 2.4 and 2.6 kernels, including kernels with the new 2.6 option for 4k stacks. 
  
-!! Other Misc 2.6 Notes 
+! !! Other Misc 2.6 Notes 
  
 In the 2.4 series, you could read <tt>/usr/src/linux-''version''/Documentation/Configure.help</tt> to see all the help for the entries you'd see in <tt>make ''foo''config</tt>. In 2.6, this has moved to individual <tt>Kconfig</tt> files in each sub-directory of the source tree. 
  
 !!! See also