On Mon, 30 Jul 2018, John Ericson wrote: > I understand this building them separately is not supported, but am > nevertheless hoping the patch can nevertheless be upstreamed on the grounds > that this generally cleans up the build system in accordance with the > principle that "feature foo" variables need not be written and should not be > read when feature foo is disabled. libgcc's configure script, for example, has
On the contrary, I think an important principle here is that non-multilib and multilib builds follow the same code paths as far as possible, with the multilib variables just set to trivial values (modulo osdirname) in the case of a non-multilib build - a non-multilib build should be building libraries exactly the same, with the same logic and the same variable settings, as the default multilib in a multilib build. -- Joseph S. Myers jos...@codesourcery.com
