On Wed, 15 Jul 2020, Richard Biener wrote: > But note one of the issues is that when not cross-compiling we're > using a single libiberty for target and host objects (likewise
There shouldn't be a target libiberty, since commit 8499116aa30a46993deff5acf73985df6b16fb8b (re PR regression/47836 (Some Cross Compiler can't build target-libiberty or target-zlib), Wed Jun 22 19:40:45 2011 +0000). If something is causing target libiberty to be built, that's a bug that should be fixed. > That said, giving configury an idea whether it configures for > the host, the target or the build would be required here - Joseph, > is there an existing mechanism for example libiberty can use > here? Makefile.def has some settings specific to host or build, e.g. build_modules= { module= libcpp; extra_configure_flags='--disable-nls am_cv_func_iconv=no';}; or host_modules= { module= libiberty; bootstrap=true; extra_configure_flags='@extra_host_libiberty_configure_flags@';}; -- Joseph S. Myers jos...@codesourcery.com