crosstool-ng/config/libc/moxiebox.in
Chris Packham 557b9d4f8d gcc: Build static libgcc in core_pass1
Per https://github.com/crosstool-ng/crosstool-ng/issues/808 build static
libgcc in the first pass which lets us skip the second one.  Building
mingw-w64 requires header files in order to build C++ support so mingw
builds core pass 2. This could probably be cleaned up by splitting
libc_start_files into a separate libc_header step. But for now having
core 2 for mingw-w64 and core 1 for the other libcs will have to do.

Anything that previously selected CC_CORE_PASSES_NEEDED now selects
CC_CORE_PASS_1_NEEDED. The same goes for CC_CORE_PASS_2_NEEDED with the
exception of mingw-w64.

Fixes #808
Fixes #217

Signed-off-by: Chris Packham <judge.packham@gmail.com>
2022-01-12 21:02:38 +13:00

27 lines
902 B
Plaintext

# moxiebox options
# Moxie is distributed in non-bootstrapped form, so we really need
# autoconfig and automake.
## depends on ARCH_MOXIE
## depends on ARCH_LE
## depends on BARE_METAL
## select LIBC_NEWLIB_SHOW
## select LIBC_SUPPORT_THREADS_NONE
## select COMP_TOOLS_AUTOCONF if !CONFIGURE_has_autoconf_2_65_or_newer || !CONFIGURE_has_autoreconf_2_64_or_newer
## select COMP_TOOLS_AUTOMAKE if !CONFIGURE_has_automake_1_15_or_newer
## select CC_CORE_PASS_1_NEEDED
## select LIBELF_NEEDED
##
## help Secure execution runtime for Moxie architecture.
config MOXIEBOX_SHORT_TUPLE
bool "Use 'moxiebox-' as target tuple"
select OMIT_TARGET_ARCH
select OMIT_TARGET_VENDOR
select TARGET_SKIP_CONFIG_SUB
help
Moxiebox refers to the tools configured for 'moxie-unknown-moxiebox-' by
a short, 'moxiebox-' prefix. Though non-canonical, it seems to be officially
endorsed.