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