On Wed, 15 Jul 2020, Joseph Myers wrote:
> 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@';};
Ah, OK. Looks like we should be able to add a
@extra_target_cet_configure_flags@, funnel that to the target_modules
and keep CET disabled by default in the modules configury.
Similarly (if HJ is correct) we'd need to add
@extra_{host,build}_cet_configure_flags@ for the purpose of lto-plugin
which only has a host module (and for bootstrap host == build, so it's
shared there but we still have separate libiberties for host/build...)
Richard.
