This is an auto-filled bug because dev-cpp/glibmm does not respect CFLAGS. The issue was originally discovered on arm64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info. NOTE: To reproduce this issue you may want to set CFLAGS="${CFLAGS} -frecord-gcc-switches".
Created attachment 635914 [details] build.log build log and emerge --info
I don't know what's going on here, but it works fine for me. Note that the bug report talks about CFLAGS not being respected, but that's correct - CXXFLAGS are to be respected, not CFLAGS, so the reproducer here is wrong. That said, it works fine for me, I suspect some older incarnation of meson.eclass or your custom CXX was messing this up, as seen in the logs: WARNING: Env var CXX seems to point to the cross compiler. This is probably wrong, it should always point to the native compiler. WARNING: Env var AR seems to point to the cross compiler. This is probably wrong, it should always point to the native compiler. WARNING: Env var CXX seems to point to the cross compiler. This is probably wrong, it should always point to the native compiler. C++ compiler for the host machine: aarch64-unknown-linux-gnu-g++ (gcc 9.3.0 "aarch64-unknown-linux-gnu-g++ (Gentoo 9.3.0 p2) 9.3.0") C++ linker for the host machine: aarch64-unknown-linux-gnu-g++ GNU ld.bfd 2.34 WARNING: Env var AR seems to point to the cross compiler. This is probably wrong, it should always point to the native compiler.
