Talk:Kernel/Arch Build System
- I am doing this now and 2 dependencies have shown up that are not documented, bc and xmlto. Or maybe these used to be installed with base-devel but no longer are.
- At the time of this writing,
PKGBUILD::makedepends. Kernel/Arch Build System#Compiling suggests to use
makepkg -s, and states
, , and other required packages, are mentioned at
-sparameter will download any additional dependencies used by recent kernels such as xml and docs.
- Regid (talk) 10:12, 19 December 2019 (UTC)
- If somebody want to keep stock kernel beside custom one, shouldn't be the "provides" array uncommented, and changed to
provides=('kernel26' 'linux') ? --4javier 05:27, 10 January 2012 (EST)
- should I also uncomment these parts in package_linux-headers() and not only in package_linux()? --Onny 11:08, 8 March 2012 (EST)
- this page does not mention that every changed .config-file has a new md5sum which should be added into the PKGBUILD --Onny 11:24, 8 March 2012 (EST)
Rename linux.install instruction ambiguous
This is ambiguous: "Depending on the PKGBUILD you may have to also rename linux.install to match the modified pkgbase." An example of what to change it to based on some hypothetical value of pkgbase would be helpful.
90-linux.hook, and perhaps a few other files, have a
%PACKAGEBASE%directive that will be filled in automatically if
PKGBUILDis edited to have:
% grep '^.\?pkgbase' PKGBUILD #pkgbase=linux # Build stock -ARCH kernel pkgbase=linux-custom # Build kernel with a different name
- linux-custom is just an example string. All this is mentioned at Kernel/Arch_Build_System#Modifying_the_PKGBUILD. I guess one is not expected to rename
linux.installto match the modified pkgbase if he followed that suggestion. Regid (talk) 15:31, 23 February 2019 (UTC)