1 |
On 10/8/06, Lionel Bouton <lionel-dev@××××××.name> wrote: |
2 |
> Here's a draft of a paragraph discussing CFLAGS-related problems. This |
3 |
> is the result of a discussion I started on gentoo-dev. Thanks to all |
4 |
> devs who gave feedback this should bring some food for thought to GWN |
5 |
> readers. |
6 |
|
7 |
Hi Lionel, |
8 |
|
9 |
Thanks for writing this up, great job. Nitpicking spelling and |
10 |
grammar points to follow ;) |
11 |
|
12 |
> configurability that are hallmarks of the <uri |
13 |
> link=http://www.gentoo.org/main/en/about.xml> Gentoo experience</uri>. |
14 |
|
15 |
Extra space before "Gentoo" here. |
16 |
|
17 |
> for most users. There's usually very little benefit, high risks and much |
18 |
> time spent on frustating tuning that could be enjoyed doing far more |
19 |
> interesting things. |
20 |
> </warn> |
21 |
|
22 |
"frustating" should be "frustrating" |
23 |
|
24 |
> <p>Example of this are :</p> |
25 |
|
26 |
Should be plural: "Examples" |
27 |
|
28 |
> <li><c>-fforce-addr</c> and <c>-fweb</c> break regularly on x86 with |
29 |
> video libraries or graphic processing apps which use hand-optimised ASM. |
30 |
> <c>-fweb</c> may be safe on amd64 but like above no guarantees</li> |
31 |
|
32 |
"optimised" should be "optimized" |
33 |
|
34 |
> For example <c>-ffast-math</c> is added by the xmame/xmess ebuilds on |
35 |
> most architectures even tho you SHOULD NOT put it in your CFLAGS.</li> |
36 |
|
37 |
"tho" should be "though" |
38 |
-- |
39 |
gentoo-dev@g.o mailing list |