ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-21 13:47:48 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
d75c8c3b0f
crosstool-ng/config/kernel/linux.in

64 lines
1.7 KiB
Plaintext
Raw Normal View History

Add the full crosstool-NG sources to the new repository of its own. You might just say: 'Yeah! crosstool-NG's got its own repo!". Unfortunately, that's because the previous repo got damaged beyond repair and I had no backup. That means I'm putting backups in place in the afternoon. That also means we've lost history... :-(
2007-02-24 11:00:05 +00:00
# Linux kernel options
Add PRU cross tool target Add sample configuration for building cross toolchain for the TI PRU. PRU cores are present in many of the BeagleBone single board computers. More information about the PRU can be found in https://bbb.io/pru Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu>
2021-01-15 18:19:25 +00:00
## depends on !ARCH_AVR && !ARCH_MSP430 && !ARCH_MOXIE && !ARCH_PRU
config: fix recursive deps The latest kconfig stuff is more stringent when it comes to validating the dependency of the symbols. It is no longer possible to have a symbol depend on itself (such as our construct for arch/cc/libc/... was doing). Fix our generated-file infrastructure to avoid these situations when the new kconfig stuff will be merged (in a following changeset). Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-05-08 17:02:44 +00:00
## select KERNEL_SUPPORTS_SHARED_LIBS
Switch gen-kconfig to new framework Also: - Move companion_* to comp_* to match the kconfig symbols - Replace bootstrap with former gen-versions.sh - Fold *.in.2 into their respective first parts; this moves common options to the end - if it is undesirable, inclusion of *.in can be moved where *.in.2 used to be (but that will also move version selection after common options). - Retire addToolVersion.sh (may later replace with a more comprehensive script that tries to download the added tarballs, copy the patches and try to apply them, and create a version.desc). Signed-off-by: Alexey Neyman <stilor@att.net>
2017-07-05 02:19:42 +00:00
config: fix recursive deps The latest kconfig stuff is more stringent when it comes to validating the dependency of the symbols. It is no longer possible to have a symbol depend on itself (such as our construct for arch/cc/libc/... was doing). Fix our generated-file infrastructure to avoid these situations when the new kconfig stuff will be merged (in a following changeset). Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-05-08 17:02:44 +00:00
## help Build a toolchain targeting systems running Linux as a kernel.
kernel/linux: reorder stuff Yet another reordering... Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-05-09 17:26:54 +00:00
Add notes about obsoletion policy for kernel/glibc. Signed-off-by: Alexey Neyman <stilor@att.net>
2017-02-09 21:54:50 +00:00
# GLIBC and kernel are special when it comes to obsoletion. Users
# of crosstool-ng depend on the ability to build new toolchains matching
# the kernel/libc versions of a particular target system, and LTS releases
# are still using quite ancient versions. Please do not retire versions
# (including versions in between) until the EOL dates indicated below.
Convert the rest of packages to new framework Signed-off-by: Alexey Neyman <stilor@att.net>
2017-05-27 07:01:49 +00:00
# Such pinned versions are indicated in version.desc files with a comment.
config: Update kconfig for new CT_GetCustom This commit sort of unifies the kconfigs to handle custom files and directories. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-26 13:07:37 +00:00
config: Detect rsync presence at config time Linux kernel versions newer than 5.3 require rsync in order to export the UAPI headers. Commit f441a6bf ("linux: Add dependency on rsync for Linux >= 5.3") attempted to address this with a check that runs when crosstool-ng is built. That had the downside that if crosstool-ng was built and packaged on a machine that had rsync then run on a machine that didn't then the build would fail due to the missing rsync. Conversely if the first machine didn't have rsync installed when crosstool-ng was built then we would not offer newer kernel versions. We can address this by checking for rsync when the toolchain configuration is updated using some functionality in the newer Kconfig that we've updated to previously. Fixes #1940 Signed-off-by: Chris Packham <judge.packham@gmail.com>
2023-12-09 22:55:22 +00:00
config KERNEL_has_rsync
def_bool $(success,which rsync)
linux: Add dependency on rsync for Linux >= 5.3 As of Linux v5.3 rsync is used as part of the build process. Add Linux 5.3 as a milestone, configure detection of rsync and a dependency on rsync for Linux 5.3 and newer. Add a comment in so that users can tell why they can't select a newer version. Fixes #1628 Signed-off-by: Chris Packham <judge.packham@gmail.com>
2021-11-14 08:24:03 +00:00
config KERNEL_DEP_RSYNC
def_bool y
config: Detect rsync presence at config time Linux kernel versions newer than 5.3 require rsync in order to export the UAPI headers. Commit f441a6bf ("linux: Add dependency on rsync for Linux >= 5.3") attempted to address this with a check that runs when crosstool-ng is built. That had the downside that if crosstool-ng was built and packaged on a machine that had rsync then run on a machine that didn't then the build would fail due to the missing rsync. Conversely if the first machine didn't have rsync installed when crosstool-ng was built then we would not offer newer kernel versions. We can address this by checking for rsync when the toolchain configuration is updated using some functionality in the newer Kconfig that we've updated to previously. Fixes #1940 Signed-off-by: Chris Packham <judge.packham@gmail.com>
2023-12-09 22:55:22 +00:00
select LINUX_REQUIRE_older_than_5_3 if !KERNEL_has_rsync
linux: Add dependency on rsync for Linux >= 5.3 As of Linux v5.3 rsync is used as part of the build process. Add Linux 5.3 as a milestone, configure detection of rsync and a dependency on rsync for Linux 5.3 and newer. Add a comment in so that users can tell why they can't select a newer version. Fixes #1628 Signed-off-by: Chris Packham <judge.packham@gmail.com>
2021-11-14 08:24:03 +00:00
comment "Linux >=5.3 requires rsync"
config: Detect rsync presence at config time Linux kernel versions newer than 5.3 require rsync in order to export the UAPI headers. Commit f441a6bf ("linux: Add dependency on rsync for Linux >= 5.3") attempted to address this with a check that runs when crosstool-ng is built. That had the downside that if crosstool-ng was built and packaged on a machine that had rsync then run on a machine that didn't then the build would fail due to the missing rsync. Conversely if the first machine didn't have rsync installed when crosstool-ng was built then we would not offer newer kernel versions. We can address this by checking for rsync when the toolchain configuration is updated using some functionality in the newer Kconfig that we've updated to previously. Fixes #1940 Signed-off-by: Chris Packham <judge.packham@gmail.com>
2023-12-09 22:55:22 +00:00
depends on !KERNEL_has_rsync
linux: Add dependency on rsync for Linux >= 5.3 As of Linux v5.3 rsync is used as part of the build process. Add Linux 5.3 as a milestone, configure detection of rsync and a dependency on rsync for Linux 5.3 and newer. Add a comment in so that users can tell why they can't select a newer version. Fixes #1628 Signed-off-by: Chris Packham <judge.packham@gmail.com>
2021-11-14 08:24:03 +00:00
Switch gen-kconfig to new framework Also: - Move companion_* to comp_* to match the kconfig symbols - Replace bootstrap with former gen-versions.sh - Fold *.in.2 into their respective first parts; this moves common options to the end - if it is undesirable, inclusion of *.in can be moved where *.in.2 used to be (but that will also move version selection after common options). - Retire addToolVersion.sh (may later replace with a more comprehensive script that tries to download the added tarballs, copy the patches and try to apply them, and create a version.desc). Signed-off-by: Alexey Neyman <stilor@att.net>
2017-07-05 02:19:42 +00:00
choice
bool
prompt "Kernel verbosity:"
default KERNEL_LINUX_VERBOSITY_0
config KERNEL_LINUX_VERBOSITY_0
bool
prompt "Simplified"
help
Print simplified command lines.
config KERNEL_LINUX_VERBOSITY_1
bool
prompt "Full commands"
help
Print full command lines.
config KERNEL_LINUX_VERBOSITY_2
bool
prompt "Exec reasons"
help
Print the reasons why a make target is rebuild.
endchoice
config KERNEL_LINUX_VERBOSE_LEVEL
int
default 0 if KERNEL_LINUX_VERBOSITY_0
default 1 if KERNEL_LINUX_VERBOSITY_1
default 2 if KERNEL_LINUX_VERBOSITY_2
config KERNEL_LINUX_INSTALL_CHECK
bool
prompt "Check installed headers"
default y
linux: Add 5.17.5, bump LTS Add 5.17.5 Bump 5.16.9 -> 5.16.20 Bump 5.15.23 -> 5.15.37 Bump 5.10.100 -> 5.10.113 Bump 4.19.229 -> 4.19.241 Bump 4.14.266 -> 4.14.277 Bump 4.9.301 -> 4.9.312 Linux 5.5 made `make headers_check` a no-op and as of 5.17 it has been removed so add a milestone and use it as a dependency for KERNEL_LINUX_INSTALL_CHECK. Signed-off-by: Chris Packham <judge.packham@gmail.com>
2022-05-08 03:15:57 +00:00
depends on !LINUX_later_than_5_5
Switch gen-kconfig to new framework Also: - Move companion_* to comp_* to match the kconfig symbols - Replace bootstrap with former gen-versions.sh - Fold *.in.2 into their respective first parts; this moves common options to the end - if it is undesirable, inclusion of *.in can be moved where *.in.2 used to be (but that will also move version selection after common options). - Retire addToolVersion.sh (may later replace with a more comprehensive script that tries to download the added tarballs, copy the patches and try to apply them, and create a version.desc). Signed-off-by: Alexey Neyman <stilor@att.net>
2017-07-05 02:19:42 +00:00
help
If you are in doubt that installed headers are buggy, say 'Y'
here to have an extra check passed onto the headers.
Reference in New Issue Copy Permalink