-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/22/2012 08:44 PM, Diego Elio Pettenò wrote:
> Il 22/07/2012 14:38, Rick "Zero_Chaos" Farina ha scritto:
>> It would seem to me that we could get all these QA warning out of the
>> way very quickly by adding -frecord-gcc-switches to the *FLAGS in the
>> base profile (it appears to be platform agnostic but if I'm wrong we can
>> add it for supported arches).
>
> Ehm no that's not a good idea because it can actually cause problems.
> Some ebuilds do s/-O2/${CFLAGS} s/gcc/$(tc-getCC)/ (in this order) and
> then -frecord-gcc-switches will fail.
>
> Other packages call ld directly, and then -frecord-gcc-switches in
> LDFLAGS will fail...
>
Those are two very valid reasons why we can't add these to the profiles,
but do you have any suggestions on how we can get more than just
yourself running this QA?
Even something simply like detecting CFLAGS="-frecord-gcc-switches" set
but not FFLAGS and then teasing the user into fixing it would seem
worthwhile to me.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJQDYo6AAoJEKXdFCfdEflK7TkP/i3Fg5jyC00QQMNLh/RAf4O6
kZHlFaTNzAjaCJvdaZY10LEPpz4sOMLyGq+gE4dnugafUkoAj4Lv17pDy7Fat0RZ
7qGJcw2JK/lzX4G0djIb8DCX8zx1zlFBmODtOMQudJev8wdpOYA0WtNtLMHacWPp
h7+cEe3rUXZcHHH+9Pl5C1DBzZpHo8hG1JIW/Mg8p5JiCeXmGLNg8IeLC+lfKP3i
4wt7H9T+IAY/4oa1ihk+y46asnjhn8DkeAMtcsDow/ZB0iuqhfd5OCD0naUi/Yge
/Um7YN+mVQX2bMUa5tSqRLRA8GKrHoacGG7SL98VPCXEocBZ+LdoQgDsocRJ1D7n
t9ETEi5uHoGQ7CnnaH5UUq9wB/NddizQ+jg2rNyAnq0RobQLyfq9d0CwM5KjmHpx
q2dbiRtXZWhtDK8xDzogwZN0BChZgO04PgHnMwLrxqxCJ/tTb+KwjRKsUSFQErwn
kmq6/WmInFYKi1uCjyYIHmUVHjfGrlKc9Frbiu8Q/r+L4Jp9uGg/xYuZprxiiWZF
Y5XkYjWfdelDoFZ+TowpfMUcyQNjssbUK/Djf6xPnIlGiUtSEDQf0yJrnITmjHov
baWsHBnO6WEyvGwvXOyn5V3ZAbXj7rmipcFePa6WqxwhlwNbPFY9SVnffg5fdbdQ
gm+lUFpJnEg33LrKOvoM
=3iiT
-----END PGP SIGNATURE-----
