🚀 go-pugleaf

Even after getting the most excellent gcc 2.x installed and fixincludes
executed, one occasionally finds that
there are certain /usr/include headers which are "suboptimal" in regards
to their prototyping, and sometimes even their ANSI C compatibility (wait.h
and it's unsigned short bit fields for instance, or the missing prototypes
for many of the stdio routines for example).

Has anyone out there tackled this problem?  I would love to discuss your
solutions - particularly elegant ones which do not require FSF to have
to make changes but yet remove many of the warnings due to the various
'damaged' headers.

Thanks for any email on this topic - perhaps there is a mailing list for
this topic in and of itself?  Or perhaps some of you will be at the Sun
User's Group next week and we can connect?
-- 
:s Great net resources sought...
:s Larry W. Virden                 INET: lvirden@cas.org
:s Personal: 674 Falls Place,   Reynoldsburg, OH 43068-1614
The task of an educator should be to irrigate the desert not clear the forest.