Mail Archives: djgpp-workers/2000/06/05/14:20:07
"Mark E." wrote:
>
> > Sorry for too guick and hot-tempered reply.
>
> No need to be sorry. Actually, I didn't detect an angry response, so I never
> even had a chance to be offended.
> > Looks like the only solution is to conditionally #include <sys/djtypes.h> in
> > gcc headers and then do just like in our headers - a solution suggested by Eli
> > weeks ago.
>
> Fine by me. If they don't go for that, we'll have to change our headers. So
> let's all hope they go for it.
I did some additional experimenting - added DJGPP file level sentinels
to GCC headers and now I see that it does not fully fix the problem -
there are conflicts between the same things defined in different headers.
------
In file included from ../../gcc/tsystem.h:52,
from ../../gcc/libgcc2.c:37:
d:/djgpp/include/stdio.h:35: warning: redefinition of `va_list'
include/stdarg.h:112: warning: `va_list' previously declared here
d:/djgpp/include/stdio.h:38: warning: redefinition of `size_t'
include/stddef.h:200: warning: `size_t' previously declared here
In file included from ../../gcc/tsystem.h:69,
from ../../gcc/libgcc2.c:37:
d:/djgpp/include/stdlib.h:39: warning: redefinition of `wchar_t'
include/stddef.h:288: warning: `wchar_t' previously declared here
-----
So we need to add indvidual guards. One solution is to add __dj_size_t
trickery to GCC headers. But IMHO the only way to get such patch into
GCC is to fool GCC maintainers :), because they want to see *their*
definitions, and not to pull *our* ones from <sys/djtypes.h>, what this
patch would do.
I'm afraid to make the conclusion that DJGPP headers should reuse GCC
sentinel system. This would be an internal change, so FAQs should
remain minimized. I could take responsibility for making this change
and ensure the absence of problems.
Laurynas
- Raw text -