^ —————. —.— . . —.— . . .————— . .
——— | | | | | | || | | | |
—(o)— | | | | | | | | | |———— '————|
——————— | | | | | | | || | |
————————— —————' —'— ' —'— ' ' '————— '
home manual roadmap issues status papers download
- Timestamp:
-
01/14/2020 11:48:01 AM (5 years ago)
- Author:
-
mornfall
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
initial
|
v1
|
|
1 | | I think there's a fundamental misunderstanding what DiOS is and how it works. DiOS provides its own headers: how macros like __x86_64__ are used in system headers has no effect on 'divine cc' or 'dioscc'. If you want to use system headers, you want to use 'divcc' instead. Both approaches have their downsides. |
| 1 | I think there's a fundamental misunderstanding what DiOS is and how it works. DiOS provides its own headers: how macros like `__x86_64__` are used in system headers has no effect on 'divine cc' or 'dioscc'. If you want to use system headers, you want to use 'divcc' instead. Both approaches have their downsides. |