| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Alec Warner wrote: |
| 5 |
> |
| 6 |
> Except you need a way for them to turn it off, and you do not currently |
| 7 |
> provide one. We can set default flags all we want, but I don't see |
| 8 |
> filtering 'bad' flags as necessarily our problem. If you want to say: |
| 9 |
> |
| 10 |
> "Hey we have had issues with people filing bogus bug reports with CFLAGS |
| 11 |
> that are completely inappropriate, so by default we check the sanity of |
| 12 |
> your CFLAGS, this is how you turn those checks off." then I'd be ok with it. |
| 13 |
> |
| 14 |
> Most of the Ricers won't read it, and maybe you can print a warning that |
| 15 |
> CFLAG checking is disabled. |
| 16 |
> |
| 17 |
> However leaving it on all the time merely imposes penalties on the power |
| 18 |
> users who wish to use your profile. Your profile is a tool that should |
| 19 |
> be useful to all classes of users. |
| 20 |
> |
| 21 |
|
| 22 |
The only flags that are actually removed are the _invalid_ flags. These are the |
| 23 |
flags that gcc does not accept, and will error out on. The "bad" flags, IE the |
| 24 |
ones that the developers consider to be broken, but that are accepted by gcc are |
| 25 |
not filtered, the profile simply prints a warning and pauses for 5 seconds to |
| 26 |
encourage users to read the warning, it does not automatically filter any flags |
| 27 |
that the compiler accepts. |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.4.2.2 (GNU/Linux) |
| 30 |
|
| 31 |
iD8DBQFEPw20Wt/XSf2CZdkRAotCAJ9pRFXAbPine5qYbycGXoeDWyy+DACaA84z |
| 32 |
KZ43edqxiv30vniE2e2wxlc= |
| 33 |
=0vEQ |
| 34 |
-----END PGP SIGNATURE----- |
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives