@vcunat We ran into a problem that seems to have the same solution that you implemented in chntpw: fix #11474, build with multiple-output glibc · NixOS/nixpkgs@d130116 · GitHub
or @dtzWill (Merge pull request #34645 from dtzWill/feature/musl · NixOS/nixpkgs@a267ae4 · GitHub)
Changing glibc into glibc.out seems to avoid certain -isystem setting logic in
- https://github.com/NixOS/nixpkgs/blob/577a220c1650ea8d1f0ed56c305235f92371b4fe/pkgs/build-support/cc-wrapper/cc-wrapper.sh#L134-L140
- https://github.com/NixOS/nixpkgs/blob/54c7a0f42287f63c2db8086a8ad46ac981364378/pkgs/build-support/cc-wrapper/add-flags.sh#L53
- https://github.com/NixOS/nixpkgs/blob/577a220c1650ea8d1f0ed56c305235f92371b4fe/pkgs/build-support/cc-wrapper/default.nix#L346-L363
Is there a rule or logic behind using glibc.out vs glibc or glibc.dev?
Possibly related: stdenv: principial linking problems when putting static and dynamic libraries into different directories · Issue #12085 · NixOS/nixpkgs · GitHub