-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ivan Yosifov wrote: > > Then the only fail-safe way to do it is to print a big red warning and > pause for 10 seconds during ebuild emerge. Given the valgrind-3.0.0 > keywords ( -* ~amd64 ~ppc ~x86 ) I guess most people on those arches > have SSE anyway. AFAIK all amd64's have SSE, I don't know about ppc, and > I doubt anyone is running Gentoo on i686. You should expect a few bugs > about it though. >
I have Gentoo installed on a couple of machines without sse. They both have Pentium 2 processors. Although I won't be running valgrind on those machines (desktops for my grand parents) there could be someone else who does. I started thinking that one possible solution would be to have some kind of a subprofile system for different kind of processors. Of course it is a bit of an overkill for just one package but there could be other uses like setting the default CFLAGS and turning on the right use flags for those processors. With these profiles >=valgrind-3.0.0 could be by default in package.mask and unmasked only on the profiles that can use it. Regards, Petteri Räty (Betelgeuse) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC9eBJcxLzpIGCsLQRAsGnAJ9YwpC3C3YkATUmZWMAdgqAkYOuwwCeIm0D 5D2e0E3NZkCCR23gCBnsUew= =zNnV -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
