On 04/16/2013 04:53 PM, Neil Bothwick wrote: > On Tue, 16 Apr 2013 13:18:51 -0500, Paul Hartman wrote: > >>> It's unfortunate there's no tool to perform as revdep-rebuild, >>> except checking that, e.g. a package was built with the current >>> CHOST or CFLAGS set. The fact that I can run 'emerge --info >>> $atomname' to get the build environment for a given $atomname >>> tells me the system has enough information that this is >>> possible. I simply don't know the finer details of where all >>> this information lurks. But if I had such a tool, it would be of >>> immense use to me while installing new systems; no need to >>> emerge -e @world... >> >> Check out /var/db/pkg/$CATEGORY/$PKGNAME/ -- there are text files >> containing CFLAGS, CHOST and many others. You or someone like you >> should be able to hack together a simple script to look for >> differences. :) > > % source /etc/portage/make.conf % for f in /var/db/pkg/*/*/CFLAGS [[ > $(cat $f) == $CFLAGS ]] || echo $f > > It does give quite a few hits though, because ebuilds can strip out > flags.
ebuilds should not generally be stripping out flags. Certainly there are occasional and valid cases, but they're pretty rare. Heck, last time I reported a bug where a flag was causing a build failure (since the package was using a compiler different from the system compiler), I was told it wasn't the packaging system's job to deal with that kind of bug. > Of course, that in itself may be an indication that you have > over-ricered your CFLAGS ;-) Or you might simply know what you're doing. http://en.gentoo-wiki.com/wiki/Hardware_CFLAGS#Determining_available_processor_features Highly valuable if you're going to use distcc.
signature.asc
Description: OpenPGP digital signature
