If I follow these instructions for setting up a clean mpl-dev conda environment on Ubuntu 24.04 LTS, the editable install fails to import with an error similar to the one reported in #28357. Adding --config-settings=setup-args="-Db_lto=false" to the pip install command worked for me. The question is, should we add documentation about using setting (that I still have no clue what it did), as a troubleshooting step, or would it make more sense to have the meson code somehow detect the correct setting for LTO and avoid the problem all together?
See #29852 (comment) I don't know why conda-forge sets the non-standard GCC_AR instead of AR, but quite frankly, I don't use conda and which of the several compiler-related feedstocks to report it to is just too confusing to figure out.
There are three options, in increasing order of difficulty, but also in increasing order of desirability:
Add a note somewhere in the docs about this.
Revert the change to install compilers from conda-forge and instead depend on system compilers once again.
Figure out how / where to report to get conda-forge compilers to set AR correctly instead of a non-standard environment variable, or convince Meson devs they should use the non-standard variable.
Activity
QuLogic commented on Jan 14, 2026
See #29852 (comment) I don't know why conda-forge sets the non-standard GCC_AR instead of AR, but quite frankly, I don't use conda and which of the several compiler-related feedstocks to report it to is just too confusing to figure out.
melissawm commented on Jan 14, 2026
I had the same issue on Manjaro. This may need a note in the dev docs?
QuLogic commented on Jan 16, 2026
There are three options, in increasing order of difficulty, but also in increasing order of desirability:
rcomer commented on Oct 5, 2026
This appears to have been fixed somewhere #29852 (comment)