Hi Joseph, Thank you for the feedback.
You're absolutely right — the --with-multi-buildlist option introduces a user-visible, target-independent feature, and it deserves to be reviewed and documented separately from the MIPS-specific changes. I prepared a revised patch that: - Introduces only the --with-multi-buildlist option and its integration into the build system, - Includes full documentation in gcc/doc/install.texi explaining the purpose, usage, and expected format of the build list file, - Provides a detailed commit message describing the motivation, design rationale, and how the implementation aligns with that design. Following up on the target-independent patch, the second patch integrates --with-multi-buildlist into the MIPS multilib configuration. It introduces a unified multilib setup via t-mips-multi and uses external ml-* buildlist files to control which variants are built. This simplifies multilib management and enables vendor-specific customization without modifying GCC internals. Thanks again for the guidance. Thanks in advance for your review! Best regards, Aleksandar Rakić
