| 1 |
Am 29.05.2012 23:37, schrieb Rafa Griman: |
| 2 |
> On Tue, May 29, 2012 at 11:09 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 3 |
>> On Tue, 29 May 2012 22:56:07 +0200 |
| 4 |
>> Rafa Griman <rafagriman@×××××.com> wrote: |
| 5 |
>> |
| 6 |
>>> Hi Vaeth :) |
| 7 |
>>> |
| 8 |
>>> On Tue, May 29, 2012 at 7:02 PM, Vaeth |
| 9 |
>>> <vaeth@××××××××××××××××××××××××.de> wrote: |
| 10 |
>>>> On Tue, 29 May 2012, Rafa Griman wrote: |
| 11 |
>>>>> |
| 12 |
>>>>> gawk: cmd. line:3: error: Unmatched [ or [^: /[^[:space:]]/ |
| 13 |
>>>> |
| 14 |
>>>> |
| 15 |
>>>> Your gawk is broken. This happens if you emerged gawk with |
| 16 |
>>>> current gcc and aggressive FLAGS like -DNDEBUG or -flto. |
| 17 |
>>>> Not sure whether it is a bug of gawk or gcc. |
| 18 |
>>> |
| 19 |
>>> |
| 20 |
>>> So it seems to be the CFLAGS :( As I said in my previous e-mail, I was |
| 21 |
>>> "experimenting" a bit with them ... I'll be more conservative ;) |
| 22 |
>> |
| 23 |
>> Well, on the one hand the flags don;t seem to be too bad overall, but |
| 24 |
>> on the other hand there's the golden rule of Gentoo: |
| 25 |
>> |
| 26 |
>> Don't stuff around with CFLAGS |
| 27 |
>> |
| 28 |
>> Why not? Well, there's the ricer phenomenon where changed CFLAGS |
| 29 |
>> worsen performance and stability but the user's own bias convinces |
| 30 |
>> him/her that it's actually vastly improved. |
| 31 |
> |
| 32 |
> |
| 33 |
> I know that rule and tried not to be too agressive but seems I was O:) |
| 34 |
> Since it's not my min machine, I was going to experiment (nothing |
| 35 |
> "scientific", just curiosity) trying different options on different |
| 36 |
> partitions and see how they work out. |
| 37 |
> |
| 38 |
|
| 39 |
Out of curiosity: What flags do you run now? Do you know which flag |
| 40 |
exactly caused the problem? They didn't seem too experimental though |
| 41 |
-fno-inline looked odd. |
| 42 |
|
| 43 |
Regards, |
| 44 |
Florian Philipp |
Archives