From: Andrew Pinski <[email protected]> Date: Sun, 04 Jan 2026 23:17:28 -0800
> I am not a fan of this; especially how this interacts with > --enable-target-optspace or with MULTILIB_OSDIRNAMES or with > MULTIARCH_* support. Yeah, it should probably conflict with --enable-target-optspace as mixing those two doesn't make sense. I can fix that. I'll go investigate how to manage MULTILIB_OSDIRNAMES in a reasonable way; obviously my testing has been with just the Zephyr and Debian setups. > Is there a reason why --enable-target-optspace can't be used with > zephyr? Do they want the option to allow for both -Os and -O2 target > libraries in the same toolchain? Yes. Right now, in Debian, I build two sets of libraries installed in different paths and use a specfile fragment to select between them. For Zephyr, the libraries were only built with -Os and users needing -O2 were forced to built the necessary libraries separately. This is a particular problem with libstdc++ as that is very hard to build outside of the toolchain build (I submitted a patch to Zephyr to enable that, but it still hasn't been merged). I'm happy to investigate other alternatives to this brute-force approach, and will go poke at the issues you've already identified. -- -keith
signature.asc
Description: PGP signature
