i've noticed glib and gtk+ strip CFLAGS set in make.conf without even warning, which causes trouble on builds where flags like -mregparm=3 and -mpreffered-stack-boundary are used (not to mention reduced fun of tweaking them) i suggest either merely fixing it (afaik glib and gtk don't use asm code like mplayer, which is difficult to link with custom CFLAGS code, so stripping CFLAGS seem to be mere bug) and/or providing warning/USE flags like 'custom-cflags' Reproducible: Always Steps to Reproduce: 1.set your own CFLAGS in make.conf 2.emerge glib 3.watch logs :) Actual Results: CFLAGS get stripped. only -march seem to be preserved Expected Results: warning should be issued (that glib/gtk found 'unsupported' CFLAGS and continuing compilation will cause all apps linked with it to become unstable) and/or custom USE flag should be present to allow user set his/her own CFLAGS in first place
There's absolutely no need to *warn* anyone about dericing their crazy flags to something sane that doesn't break compile. Ricing is not supported.
Add to /etc/portage/bashrc: ALLOWED_FLAGS=$(for FLAGA in ${CFLAGS} ${CXXFLAGS} ${ASFLAGS} ; do echo -n "${FLAGA%%=*} " ; done) (Wszystko w jednej linii.)
