Use of GLibc code in other programs.

[Jeff Bailey <jbailey@nisa.net>]

It seems traditional (Oleo, Textutils, to observe 2 off hand) to include 
the code from Glibc in with source code for some functions in case the 
target system doesn't provide them, or may have broken varieties of them 
(eg. getline and malloc).  Most code, however, doesn't seem to come 
across easily, because it is written with the glibc-types of uint32, etc 
and builtins like weak_alias already defined.

Is it desirable to make this easier?  I'm thinking of a simple header 
file which typedefs and defines all of the different items, and then 
do an #ifndef __GLIBC__ to include the new header file.

Would you accept patches to that effect?  I'm not going to go through the 
whole library and do it, but the dozen or so that I regularily have to 
butcher into shape I'll do and write a FAQ entry for others to do it if 
they happen to need something weird.  If yes, is there any precedance for 
what the include file should be called or where it should be stored?  I 
would like it to be include/libc-defs.h

Tks,
Jeff Bailey