At 08:23 AM 26/10/95 PST, Mark Klein wrote:
>>The gcc compiler requires the purchase of the HP C compiler in order to
>>get the libraries required to link to executable.
>
>Actually, the POSIX Developer's Kit is the more appropriate product. I
>don't know whether the libraries come without it. Someone with 5.0 and
>without the POSIX Developer's Kit care to comment about whether or not
>/lib is populated?
>
 
I recall finding one or two libraries in POSIX namespaces before getting the
PDK.  Nothing particularly useful (perhaps the curses lib).
 
When you talk about needing HP libs though, are you referring to compile
libraries (RLs) or runtime libaries (XL)?
 
It strikes me as a bit funny that you if you bind the RL routines to a
program, you can freely distribute it without reference to HP, but that you
can't distribute them otherwise.  I wonder what clause that is in the license?
 
In any case, I suspect you are talking about the need for routines like
malloc(), fopen(), getcwd().  Exactly how many are there that are not
covered by gnu sources?  I would expect many routines like the string ones
like strlen() and character, isalpha(), to be already covered (unless you
want to make MBCS versions :)   I know many shareware programs include their
own replacement routines for things like malloc() and strchr() to make them
more efficient.
 
So what is the scope of the need?
----
Jim "seMPEr" Wowchuk
Vanguard Computer Services     Internet:    [log in to unmask]
 _--_|\                        Compu$erve:  100036,106
/      \                       Post:        PO Box 18, North Ryde, NSW 2113
\.--.__/ <---Sydney NSW        Phone:       +61 (2) 888-9688
      v      Australia         Fax:         +61 (2) 888-3056