crosstool-ng/samples/moxie-unknown-elf/crosstool.config

CT_CONFIG_VERSION="3"
CT_EXPERIMENTAL=y
CT_ARCH_MOXIE=y
CT_DEBUG_GDB=y
CT_GDB_CROSS_SIM=y
# CT_GDB_CROSS_PYTHON is not set
CT_COMP_LIBS_LIBELF=y
CT_DTC_VERBOSE=y
Update the samples to v3 Signed-off-by: Alexey Neyman <stilor@att.net> 2019-03-09 19:42:34 -08:00			`CT_CONFIG_VERSION="3"`
Add moxie architecture and a moxie-unknown-elf target (which is what #1088 apparently wanted). Signed-off-by: Alexey Neyman <stilor@att.net> 2018-11-19 23:34:48 -08:00			`CT_EXPERIMENTAL=y`
			`CT_ARCH_MOXIE=y`
			`CT_DEBUG_GDB=y`
			`CT_GDB_CROSS_SIM=y`
			`# CT_GDB_CROSS_PYTHON is not set`
Add moxiebox as a choice for libc This required some rework of the libc selection, as moxiebox is a layer on top of another libc - newlib. Also, moxiebox'es host VM (`sandbox`) needs a libcrypto on the host. We will not have it if we're cross-compiling a canadian cross. Fortunately, all moxiebox needs from libcrypto is SHA256, and it already includes a standalone implementation of SHA256 in its runtime. Provide a little wrapper that allows moxiebox use that implementation for the host binary, too. Also, automate collecting/printing the list of all packages in a given category (e.g. LIBC or COMP_TOOLS), generate a list of all Kconfig symbols for a given category. Signed-off-by: Alexey Neyman <stilor@att.net> 2018-11-23 22:14:07 -08:00			`CT_COMP_LIBS_LIBELF=y`
Add moxie architecture and a moxie-unknown-elf target (which is what #1088 apparently wanted). Signed-off-by: Alexey Neyman <stilor@att.net> 2018-11-19 23:34:48 -08:00			`CT_DTC_VERBOSE=y`