This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Docs for libiberty?
- To: <cygwin@sourceware.cygnus.com>
- Subject: Docs for libiberty?
- From: "Michael K. Elwood" <mkelwood@qsicorp.com>
- Date: Wed, 24 Mar 1999 10:44:04 -0700
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Sender: cygwin-owner@sourceware.cygnus.com
>> BTW: Why is libiberty called libiberty
>
>It's a play on words, sort of. In Unix, library "foo" has file
>"libfoo.a" and uses "-lfoo" to link, so with libiberty, you end up
>typing "-liberty" on your command lines all the time. The idea was to
>liberate the programmer from the deficiencies of the OS-supplied
>library by fixing or supplying whatever the OS lacked, like strdup,
>which isn't available in Ultrix, and memcmp, which isn't available in
>SunOS.
This brings up a question I have long wanted to ask: Is there documentation
somewhere for the more obscure GNU libraries such as libiberty and libgloss
(aside from the source)? i.e. What functions do they include, etc.
Best regards,
MKE
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com