Custom Query (245 matches)

Hi/2.

Currently swab() in unistd.h was commented out. Is there any special reason ?

In compliance posix, it would be better to enable swab().

Hi/2.

Currently, os2safe.h should be included manually. This is meaningful if a program intend to use a high memory. But some libraries does not consider a high memory at first.

So when enabled -Zhigh-memory in one program, it causes many problem when linking against non-high-memory-enabled libraries, especially without including os2safe.h.

However, if os2safe.h is included by default, it is possible to avoid this problem. The libraries without considering a high-memory, can be linked with a high memory enabled programs or libraries.

In addition, even tough os2safe.h is included without -Zhigh-mem, it has no side effects at all, but a little overhead to copy between the source and the buffer.

A configure script is dieing with G:/usr/include/sys/process.h:72: error: conflicting types for 'system' G:/usr/include/stdlib.h:121: note: previous declaration of 'system' was here and sure enough sys/process.h uses 72 int system (__const__ char *); and stdlib.h uses 121 int system(const char *);

not sure which is correct or if this is gcc 4.4.6 being pedantic but they should be reconciled or guarded