crosstool-ng/config/arch/m68k.in

# m68k specific configuration file

## select ARCH_SUPPORTS_32
## select ARCH_DEFAULT_32
## select ARCH_DEFAULT_BE
## select ARCH_SUPPORTS_WITH_CPU
##
## help The m68k architecture
arch: add basic m68k support Signed-off-by: Remy Bohmer <linux@bohmer.net> [yann.morin.1998@anciens.enib.fr: use defaults for CT_TARGET_ARCH] Signed-off-by: "Yann E. MORIN <yann.morin.1998@anciens.enib.fr> 2010-01-29 22:23:59 +00:00			`# m68k specific configuration file`

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 ARCH_SUPPORTS_32`
			`## select ARCH_DEFAULT_32`
			`## select ARCH_DEFAULT_BE`
arch: rename the SUPPORT_XXX options First, 'SUPPORT' should be spelled 'SUPPORTS'. Second, 'SUPPORT_XXX' really means 'supports --with-xxx', so rename the affected options accordingly. Update the affected archs to match the new namings. Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 2011-11-29 23:25:22 +00:00			`## select ARCH_SUPPORTS_WITH_CPU`
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 The m68k architecture`