[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
howtos:kernel:using_slackwares_kernel_build_scripts [2019/04/24 15:17 (UTC)] – Added the default setting of $OUTPUT and small changes. divehowtos:kernel:using_slackwares_kernel_build_scripts [2019/04/24 15:37 (UTC)] – dive
Line 31: Line 31:
 (A recipe dictates the arch of the package set.) (A recipe dictates the arch of the package set.)
  
-The Slackware kernel build scripts should be found in the k/ +The Slackware kernel build scripts can be found in the k/ source directory on 
-source directory on any mirror for Slackware -current. This +any mirror of Slackware -current. This contains the 64 and 32 bit generic and 
-contains the 64 and 32 bit generic and huge configs, and a +huge configs, and a kernel source tarball. The 14.2 source directories have a 
-kernel source tarball. The 14.2 source directories have a +different setup, but the scripts in -current can be used for 14.2.
-different setup, so this is aimed at using -current scripts.+
  
 There isn't a firmware build script in there so I won't be There isn't a firmware build script in there so I won't be
Line 47: Line 46:
   * Loop to the next package...   * Loop to the next package...
  
-At its simplest, you can mirror the k/ directory, export +At its simplest, you can mirror the k/ directoryand then run the build script. 
-OUTPUT in the environment, and then run the build script. +This will build and install a set of kernel packages, using the newest version 
-This will build and install a set of kernel packages, using +source archive found in the current directory. There is no need to manually set 
-the highest version source archive found in the current +the kernel version.
-directory. There is no need to manually set the kernel +
-version. If the version isn't what you expect, you may +
-need to remove the other files, leaving the one you need.+
  
-By exporting a few options the build routine can be changed, +By exporting a few variables the build routine can be changed, such as:
-such as:+
  
   * The local version (explanation below.)   * The local version (explanation below.)
Line 64: Line 59:
   * Whether the packages are installed on the build system.   * Whether the packages are installed on the build system.
  
-Some minor tweaking of the scripts is necessary if we change +Some minor tweaking of the scripts is necessary if we change the default build 
-the default build directory, and to stop the existing +directory, and we may not want to clobber the existing symlinks in /boot if we 
-symlinks in /boot from being clobbered.+are making a custom kernel.
  
 For this example I will build packages for linux-5.0.8, with For this example I will build packages for linux-5.0.8, with

Trace: • contributing

howtos:kernel:using_slackwares_kernel_build_scripts ()