newlib-cygwin/newlib/libc/machine/sh/acinclude.m4

if test "${machine_dir}" = "sh"; then
  AC_CACHE_CHECK([for SH5 (64-bit)], newlib_cv_sh64, [dnl
    AC_PREPROC_IFELSE([AC_LANG_PROGRAM(
[[#if !defined(__SH5__)
# error "not SH5"
#endif
]])], [newlib_cv_sh64=yes], [newlib_cv_sh64=no])])
fi

AM_CONDITIONAL(SH64, [test "$newlib_cv_sh64" = yes])
newlib: libc: merge machine/ configure scripts up a level The machine configure scripts are all effectively stub scripts that pass the higher level options to its own makefile. There were only three doing custom tests. The rest were all effectively the same as the libc/ configure script. So instead of recursively running configure in all of these subdirs, generate their makefiles from the top-level configure. For the few unique ones, deploy a pattern of including subdir logic via m4: m4_include([machine/nds32/acinclude.m4]) Some of the generated machine makefiles have a bunch of extra stuff added to them, but that's because they were inconsistent in their configure libtool calls. The top-level has it, so it exports some new vars to the ones that weren't already. 2022-01-23 00:23:28 -05:00			`if test "${machine_dir}" = "sh"; then`
newlib: add AC_CACHE_CHECK sugar around preprocessor checks This isn't strictly necessary, but it makes for much clearer logs as to what the target is doing, and provides cache vars for anyone who wants to force the test a different way, and it lets the build cache its own results when rerunning config.status. 2022-01-28 05:17:46 -05:00			`AC_CACHE_CHECK([for SH5 (64-bit)], newlib_cv_sh64, [dnl`
			`AC_PREPROC_IFELSE([AC_LANG_PROGRAM(`
newlib: libc: merge machine/ configure scripts up a level The machine configure scripts are all effectively stub scripts that pass the higher level options to its own makefile. There were only three doing custom tests. The rest were all effectively the same as the libc/ configure script. So instead of recursively running configure in all of these subdirs, generate their makefiles from the top-level configure. For the few unique ones, deploy a pattern of including subdir logic via m4: m4_include([machine/nds32/acinclude.m4]) Some of the generated machine makefiles have a bunch of extra stuff added to them, but that's because they were inconsistent in their configure libtool calls. The top-level has it, so it exports some new vars to the ones that weren't already. 2022-01-23 00:23:28 -05:00			`[[#if !defined(__SH5__)`
			`# error "not SH5"`
			`#endif`
newlib: add AC_CACHE_CHECK sugar around preprocessor checks This isn't strictly necessary, but it makes for much clearer logs as to what the target is doing, and provides cache vars for anyone who wants to force the test a different way, and it lets the build cache its own results when rerunning config.status. 2022-01-28 05:17:46 -05:00			`]])], [newlib_cv_sh64=yes], [newlib_cv_sh64=no])])`
newlib: libc: merge machine/ configure scripts up a level The machine configure scripts are all effectively stub scripts that pass the higher level options to its own makefile. There were only three doing custom tests. The rest were all effectively the same as the libc/ configure script. So instead of recursively running configure in all of these subdirs, generate their makefiles from the top-level configure. For the few unique ones, deploy a pattern of including subdir logic via m4: m4_include([machine/nds32/acinclude.m4]) Some of the generated machine makefiles have a bunch of extra stuff added to them, but that's because they were inconsistent in their configure libtool calls. The top-level has it, so it exports some new vars to the ones that weren't already. 2022-01-23 00:23:28 -05:00			`fi`

newlib: add AC_CACHE_CHECK sugar around preprocessor checks This isn't strictly necessary, but it makes for much clearer logs as to what the target is doing, and provides cache vars for anyone who wants to force the test a different way, and it lets the build cache its own results when rerunning config.status. 2022-01-28 05:17:46 -05:00			`AM_CONDITIONAL(SH64, [test "$newlib_cv_sh64" = yes])`