This is an auto-filed bug because dev-ruby/rbpdf-font does not respect CFLAGS/LDFLAGS. The issue was originally discovered on amd64, 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" and LDFLAGS="${LDFLAGS} -Wl,--defsym=__gentoo_check_ldflags__=0". If this is not something about c/c++ context you may want to set also FFLAGS and FCFLAGS or just see this bug as an hint to hide the QA warning where is not possible to respect CFLAGS/LDFLAGS.
Created attachment 640306 [details] build.log build log and emerge --info
ci has reproduced this issue with version 1.19.1 - Updating summary.
ci has reproduced this issue with version 1.19.1-r1 - Updating summary.
This should be fixed by the following commit: commit f02edc97cad6e965ddf85db2af4b978c732f13ab Author: Hans de Graaff <graaff@gentoo.org> Date: Fri Nov 19 11:01:15 2021 +0100 eclass/ruby-fakegem.eclass: fix CFLAGS and LDFLAGS for extensions Set the CFLAGS and LDFLAGS for extensions using the mkmf options during configuration. This ensures that the flags are correctly set in the Makefile and we don't need to second-guess any further actions of extensions themselves, leading to breakage that is hard to work around.
