J
jacob navia
Hi
Going on with the porting of lcc-win64 to lcc-linux-64 I have discovered
that most system headers in /usr/include need a compiler with at least
the following #defines prdefined:
__USE_XOPEN_EXTENDED=1
__gnuc_va_list=va_list
__i386__=1
If you do not have those symbols you wont be able to compile any header.
Since stdio.h and all headers use the non portable headers definitions
in /usr/include/bits /usr/include/asm it is imperative to predefine
those symbols.
Question: Is there somewhere a list of those needed symbols? I have
found those by trial and error and it costs a lot of effort to figure
out what is going wrong each time.
Another problem of this situation is that I need to provide (as I did
under windows) my own headers, but I do not know where to put them since
accessing /usr/include would need root access.
Since there are quite a lot of linux gurus around here, maybe some of
them has this list?
Going on with the porting of lcc-win64 to lcc-linux-64 I have discovered
that most system headers in /usr/include need a compiler with at least
the following #defines prdefined:
__USE_XOPEN_EXTENDED=1
__gnuc_va_list=va_list
__i386__=1
If you do not have those symbols you wont be able to compile any header.
Since stdio.h and all headers use the non portable headers definitions
in /usr/include/bits /usr/include/asm it is imperative to predefine
those symbols.
Question: Is there somewhere a list of those needed symbols? I have
found those by trial and error and it costs a lot of effort to figure
out what is going wrong each time.
Another problem of this situation is that I need to provide (as I did
under windows) my own headers, but I do not know where to put them since
accessing /usr/include would need root access.
Since there are quite a lot of linux gurus around here, maybe some of
them has this list?