QA Notice: Files built without respecting LDFLAGS have been detected Please include the following list of files in your report: /usr/bin/irw /usr/bin/ircat /usr/bin/irpty /usr/bin/mode2 /usr/bin/lircrcd /usr/bin/irexec /usr/bin/irsend /usr/bin/irrecord /usr/bin/irxevent /usr/bin/xmode2 /usr/lib/liblirc_client.so.0.2.1 /usr/sbin/lircd /usr/sbin/lircmd
Which version?
Well, the above is with the latest app-misc/lirc-0.8.6-r2 (no point to report similar bugs against old ones) but all versions fail in this respect pretty likely.
Build system of lirc is perfectly sane and respects LDFLAGS. It's linux-mod.eclass that's causing this. default src_compile look like that: emake ... LDFLAGS="$(get_abi_LDFLAGS)" ... I don't know whether it's intended behaviour. I see two ways of fixing it: 1. change linux-mod.eclass 2. use handcrafted src_compile instead of default linux-mod_src_compile CCing kernel-misc to consider 1.
sounds like LDFLAGS="$(get_abi_LDFLAGS)" should be LDFLAGS="${LDFLAGS} $(get_abi_LDFLAGS)" instead in the eclass
Considering that this affects any ebuild using default src_compile from linux-mod.eclass and actually installs anything beyond kernel modules, fixing this in ebuilds doesn't make sense.
Actually yes it does, because most of lirc shouldn't be build from linux-mod.eclass but on its own. Fixed in lirc-0.9.0-r1 Also, this is essentially a duplicate of bug 160134 , since the reason for that bug was that LDFLAGS were being overridden by linux-mod.eclass also.
