| 1 |
On 06/26/2011 04:33 AM, Matt Turner wrote: |
| 2 |
>> Targets "stage1, "stage2" |
| 3 |
>> 1) key "CFLAGS" subarch defaults |
| 4 |
>> 2) key "CFLAGS" earlier /etc/make.conf |
| 5 |
>> 3) key "cflags" conf file |
| 6 |
>> 4) key "cflags" spec file |
| 7 |
|
| 8 |
I think I need to correct this one to: |
| 9 |
|
| 10 |
Targets "stage1, "stage2" |
| 11 |
1) key "CFLAGS" subarch defaults |
| 12 |
2) key "cflags" conf file |
| 13 |
3) key "cflags" spec file |
| 14 |
|
| 15 |
So no affect from /etc/make.conf in that case. The file is read but the |
| 16 |
code applying its settings is override in classes stage1_target and |
| 17 |
stage2_target (without calling the original code). |
| 18 |
|
| 19 |
|
| 20 |
>> Targets "stage3", "stage4", "generic_stage" |
| 21 |
>> 1) key "CFLAGS" subarch defaults |
| 22 |
>> 2) key "CFLAGS" earlier /etc/make.conf |
| 23 |
>> |
| 24 |
>> [..] |
| 25 |
> |
| 26 |
> [..] |
| 27 |
> |
| 28 |
> Are you saying that cflags specified in the spec file are totally |
| 29 |
> ignored for stage3 and stage4? That seems totally broken. |
| 30 |
|
| 31 |
That's my impression, yes. |
| 32 |
|
| 33 |
Best, |
| 34 |
|
| 35 |
|
| 36 |
|
| 37 |
Sebastian |
Archives