Gnu C Library On

Node:Yes-or-No Questions, Previous:Formatting Numbers, Up:Locales

• Gnu C Library Reference
• Gnu C Tutorial
• Gnu C Library On Windows
• Glibc

Yes-or-No Questions

Installation: How to install the GNU C library. Maintenance: How to enhance and port the GNU C Library. Contributors: Who wrote what parts of the GNU C library. Free Manuals: Free Software Needs Free Documentation. Copying: The GNU Lesser General Public License says how you can copy and share the GNU C Library. The GNU C Library provides several header files, each of which contains the type and macro definitions and variable and function declarations for a group of related facilities. This means that your programs may need to include several header files, depending on exactly which facilities you are using. The GNU C Library version 2.34 is now available. Item posted by Carlos O'Donell on Mon 02 Aug 2021 03:57:01 AM UTC. The GNU C Library The GNU C Library version 2.34 is now available. The GNU C Library is used as the C library in the GNU system and in GNU/Linux systems, as well as many other systems that use Linux as the kernel. The GNU C Library Manual I. Status Implementation Status C 1998/2003 Implementation Status Implementation Specific Behavior C 2011 Implementation Specific Behavior C 2014 C 2017 Implementation Specific Behavior C 2020 C TR1 Implementation Specific Behavior C TR 24733 C IS 29124 Implementation Specific Behavior.

Some non GUI programs ask a yes-or-no question. If the messages (especially the questions) are translated into foreign languages, be sure that you localize the answers too. It would be very bad habit to ask a question in one language and request the answer in another, often English.

The GNU C library contains rpmatch to give applications easy access to the corresponding locale definitions.

This function would normally be used like this:

Note that the loop continues until an read error is detected or until a definitive (positive or negative) answer is read.

Go to the first, previous, next, last section, table of contents.

How to Install the GNU C Library

Installation of the GNU C library is relatively simple, but usuallyrequires several GNU tools to be installed already.(see section Recommended Tools to Install the GNU C Library, below.)

To configure the GNU C library for your system, run the shell script`configure' with sh. Use an argument which is theconventional GNU name for your system configuration--for example,`sparc-sun-sunos4.1', for a Sun 4 running SunOS 4.1.See section `Installing GNU CC' in Using and Porting GNU CC, for a full description of standard GNU configurationnames. If you omit the configuration name, `configure' will try toguess one for you by inspecting the system it is running on. It may ormay not be able to come up with a guess, and the its guess might bewrong. `configure' will tell you the canonical name of the chosenconfiguration before proceeding.

Here are some options that you should specify (if appropriate) whenyou run configure:

Use this option if you plan to use GNU ld to link programs withthe GNU C Library. (We strongly recommend that you do.) This optionenables use of features that exist only in GNU ld; so if youconfigure for GNU ld you must use GNU ldevery timeyou link with the GNU C Library, and when building it.

`--with-gnu-as'

Use this option if you plan to use the GNU assembler, gas, whenbuilding the GNU C Library. On some systems, the library may not buildproperly if you do not use gas.

`--with-gnu-binutils'

This option implies both `--with-gnu-ld' and `--with-gnu-as'.On systems where GNU tools are the system tools, there is no need tospecify this option. These include GNU, GNU/Linux, and free BSD systems.

`--without-fp'

`--nfp'

Use this option if your computer lacks hardware floating-point support.

`--prefix=directory'

Install machine-independent data files in subdirectories of`directory'. (You can also set this in `configparms';see below.)

`--exec-prefix=directory'

Install the library and other machine-dependent files in subdirectoriesof `directory'. (You can also set this in`configparms'; see below.)

`--enable-shared'

`--disable-shared'

Enable or disable building of an ELF shared library on systems thatsupport it. The default is to build the shared library on systems usingELF when the GNU binutils are available.

`--enable-profile'

`--disable-profile'

Enable or disable building of the profiled C library, `-lc_p'. Thedefault is to build the profiled library. You may wish to disable it ifyou don't plan to do profiling, because it doubles the build time ofcompiling just the unprofiled static library.

`--enable-omitfp'

Enable building a highly-optimized but possibly undebuggable static Clibrary. This causes the normal static and shared (if enabled) Clibraries to be compiled with maximal optimization, including the`-fomit-frame-pointer' switch that makes debugging impossible onmany machines, and without debugging information (which makes thebinaries substantially smaller). An additional static library iscompiled with no optimization and full debugging information, andinstalled as `-lc_g'.

The simplest way to run configure is to do it in the directorythat contains the library sources. This prepares to build the libraryin that very directory.

You can prepare to build the library in some other directory by goingto that other directory to run configure. In order to runconfigure, you will have to specify a directory for it, like this:

configure looks for the sources in whatever directory youspecified for finding configure itself. It does not matter wherein the file system the source and build directories are--as long as youspecify the source directory when you run configure, you will getthe proper results.

This feature lets you keep sources and binaries in differentdirectories, and that makes it easy to build the library for severaldifferent machines from the same set of sources. Simply create abuild directory for each target machine, and run configure inthat directory specifying the target machine's configuration name.

The library has a number of special-purpose configuration parameters.These are defined in the file `Makeconfig'; see the comments inthat file for the details.

But don't edit the file `Makeconfig' yourself--instead, create afile `configparms' in the directory where you are building thelibrary, and define in that file the parameters you want to specify.`configparms' should not be an edited copy of`Makeconfig'; specify only the parameters that you want tooverride. To see how to set these parameters, find the section of`Makeconfig' that says 'These are the configuration variables.'Then for each parameter that you want to change, copy the definitionfrom `Makeconfig' to your new `configparms' file, and changethe value as appropriate for your system.

It is easy to configure the GNU C library for cross-compilation bysetting a few variables in `configparms'. Set CC to thecross-compiler for the target you configured the library for; it isimportant to use this same CC value when runningconfigure, like this: `CC=target-gcc configuretarget'. Set BUILD_CC to the compiler to use for forprograms run on the build system as part of compiling the library. Youmay need to set AR and RANLIB to cross-compiling versionsof ar and ranlib if the native tools are not configured towork with object files for the target you configured for.

Some of the machine-dependent code for some machines uses extensions inthe GNU C compiler, so you may need to compile the library with GCC.(In fact, all of the existing complete ports require GCC.)

To build the library and related programs, type make. This willproduce a lot of output, some of which may look like errors frommake (but isn't). Look for error messages from makecontaining `***'. Those indicate that something is really wrong.

To build and run some test programs which exercise some of the libraryfacilities, type make check. This will produce several fileswith names like `program.out'.

To format the GNU C Library Reference Manual for printing, typemake dvi.

To install the library and its header files, and the Info files of themanual, type make install. This will build things if necessary,before installing them.

Recommended Tools to Install the GNU C Library

We recommend installing the following GNU tools before attempting tobuild the GNU C library:

• make 3.75You need the latest version of GNU make. Modifying the GNU CLibrary to work with other make programs would be so hard that werecommend you port GNU make instead. Really.We recommend version GNU make version 3.75 or later.
• GCC 2.7.2On most platforms, the GNU C library can only be compiled with the GNU Ccompiler. We recommend GCC version 2.7.2 or later; earlier versions mayhave problems.
• binutils 2.8Using the GNU binutils (assembler, linker, and related tools) ispreferable when possible, and they are required to build an ELF shared Clibrary. We recommend binutils version 2.8 or later; earlierversions are known to have problems or to not support all architectures.

Supported Configurations

The GNU C Library currently supports configurations that match thefollowing patterns:

Former releases of this library (version 1.09.1 and perhaps earlierversions) used to run on the following configurations:

Since no one has volunteered to test and fix the above configurations,these are not supported at the moment. It's expected that these don'twork anymore. Porting the library is not hard. If you are interestedin doing a port, please contact the glibc maintainers by sendingelectronic mail to <[email protected]>.

Each case of `ix86' can be `i386', `i486',`i586', or `i686'. All of those configurations produce alibrary that can run on any of these processors. The library will beoptimized for the specified processor, but will not use instructions notavailable on all of them.

While no other configurations are supported, there are handy aliases forthese few. (These aliases work in other GNU software as well.)

Reporting Bugs

There are probably bugs in the GNU C library. There are certainlyerrors and omissions in this manual. If you report them, they will getfixed. If you don't, no one will ever know about them and they willremain unfixed for all eternity, if not longer.

To report a bug, first you must find it. Hopefully, this will be thehard part. Once you've found a bug, make sure it's really a bug. Agood way to do this is to see if the GNU C library behaves the same waysome other C library does. If so, probably you are wrong and thelibraries are right (but not necessarily). If not, one of the librariesis probably wrong.

Once you're sure you've found a bug, try to narrow it down to thesmallest test case that reproduces the problem. In the case of a Clibrary, you really only need to narrow it down to one libraryfunction call, if possible. This should not be too difficult.

The final step when you have a simple test case is to report the bug.When reporting a bug, send your test case, the results you got, theresults you expected, what you think the problem might be (if you'vethought of anything), your system type, and the version of the GNU Clibrary which you are using. Also include the files`config.status' and `config.make' which are created by running`configure'; they will be in whatever directory was current whenyou ran `configure'.

If you think you have found some way in which the GNU C library does notconform to the ISO and POSIX standards (see section Standards and Portability), that is definitely a bug. Report it!

Send bug reports to the Internet address<[email protected]> or the UUCP path<mit-eddie!prep.ai.mit.edu!bug-glibc>. If you have other problemswith installation or use, please report those as well.

If you are not sure how a function should behave, and this manualdoesn't tell you, that's a bug in the manual. Report that too! If thefunction's behavior disagrees with the manual, then either the libraryor the manual has a bug, so report the disagreement. If you find anyerrors or omissions in this manual, please report them to the Internetaddress <[email protected]> or the UUCP path<mit-eddie!prep.ai.mit.edu!bug-glibc-manual>.

Adding New Functions

The process of building the library is driven by the makefiles, whichmake heavy use of special features of GNU make. The makefilesare very complex, and you probably don't want to try to understand them.But what they do is fairly straightforward, and only requires that youdefine a few variables in the right places.

The library sources are divided into subdirectories, grouped by topic.

The `string' subdirectory has all the string-manipulationfunctions, `math' has all the mathematical functions, etc.

Each subdirectory contains a simple makefile, called `Makefile',which defines a few make variables and then includes the globalmakefile `Rules' with a line like:

The basic variables that a subdirectory makefile defines are:

.This variable must be defined.

headers

The names of the header files in this section of the library,such as `stdio.h'.

routines

aux

The names of the modules (source files) in this section of the library.These should be simple names, such as `strlen' (rather thancomplete file names, such as `strlen.c'). Use routines formodules that define functions in the library, and aux forauxiliary modules containing things like data definitions. But thevalues of routines and aux are just concatenated, so therereally is no practical difference.

tests

The names of test programs for this section of the library. Theseshould be simple names, such as `tester' (rather than complete filenames, such as `tester.c'). `make tests' will build andrun all the test programs. If a test program needs input, put the testdata in a file called `test-program.input'; it will be given tothe test program on its standard input. If a test program wants to berun with arguments, put the arguments (all on a single line) in a filecalled `test-program.args'. Test programs should exit withzero status when the test passes, and nonzero status when the testindicates a bug in the library or error in building.

others

The names of 'other' programs associated with this section of thelibrary. These are programs which are not tests per se, but are othersmall programs included with the library. They are built by`make others'.

install-lib

install-data

install

Files to be installed by `make install'. Files listed in`install-lib' are installed in the directory specified by`libdir' in `configparms' or `Makeconfig'(see section How to Install the GNU C Library). Files listed in install-data areinstalled in the directory specified by `datadir' in`configparms' or `Makeconfig'. Files listed in installare installed in the directory specified by `bindir' in`configparms' or `Makeconfig'.

distribute

Other files from this subdirectory which should be put into adistribution tar file. You need not list here the makefile itself orthe source and header files listed in the other standard variables.Only define distribute if there are files used in an unusual waythat should go into the distribution.

generated

Files which are generated by `Makefile' in this subdirectory.These files will be removed by `make clean', and they willnever go into a distribution.

extra-objs

Extra object files which are built by `Makefile' in thissubdirectory. This should be a list of file names like `foo.o';the files will actually be found in whatever directory object files arebeing built in. These files will be removed by `make clean'.This variable is used for secondary object files needed to buildothers or tests.

Porting the GNU C Library

The GNU C library is written to be easily portable to a variety ofmachines and operating systems. Machine- and operating system-dependentfunctions are well separated to make it easy to add implementations fornew machines or operating systems. This section describes the layout ofthe library source tree and explains the mechanisms used to selectmachine-dependent code to use.

All the machine-dependent and operating system-dependent files in thelibrary are in the subdirectory `sysdeps' under the top-levellibrary source directory. This directory contains a hierarchy ofsubdirectories (see section Layout of the `sysdeps' Directory Hierarchy).

Each subdirectory of `sysdeps' contains source files for aparticular machine or operating system, or for a class of machine oroperating system (for example, systems by a particular vendor, or allmachines that use IEEE 754 floating-point format). A configurationspecifies an ordered list of these subdirectories. Each subdirectoryimplicitly appends its parent directory to the list. For example,specifying the list `unix/bsd/vax' is equivalent to specifying thelist `unix/bsd/vax unix/bsd unix'. A subdirectory can also specifythat it implies other subdirectories which are not directly above it inthe directory hierarchy. If the file `Implies' exists in asubdirectory, it lists other subdirectories of `sysdeps' which areappended to the list, appearing after the subdirectory containing the`Implies' file. Lines in an `Implies' file that begin with a`#' character are ignored as comments. For example,`unix/bsd/Implies' contains:

and `unix/Implies' contains:

So the final list is `unix/bsd/vax unix/bsd unix/inet unix posix'.

`sysdeps' has two 'special' subdirectories, called `generic'and `stub'. These two are always implicitly appended to the listof subdirectories (in that order), so you needn't put them in an`Implies' file, and you should not create any subdirectories underthem intended to be new specific categories. `generic' is forthings that can be implemented in machine-independent C, using onlyother machine-independent functions in the C library. `stub' isfor stub versions of functions which cannot be implemented on aparticular machine or operating system. The stub functions alwaysreturn an error, and set errno to ENOSYS (Function notimplemented). See section Error Reporting.

A source file is known to be system-dependent by its having a version in`generic' or `stub'; every generally-available function whoseimplementation is system-dependent in should have either a generic orstub implementation (there is no point in having both). Some rare functionsare only useful on specific systems and aren't defined at all on others;these do not appear anywhere in the system-independent source code or makefiles(including the `generic' and `stub' directories), only in thesystem-dependent `Makefile' in the specific system's subdirectory.

If you come across a file that is in one of the main source directories(`string', `stdio', etc.), and you want to write a machine- oroperating system-dependent version of it, move the file into`sysdeps/generic' and write your new implementation in theappropriate system-specific subdirectory. Note that if a file is to besystem-dependent, it must not appear in one of the main sourcedirectories.

There are a few special files that may exist in each subdirectory of`sysdeps':

A makefile for this machine or operating system, or class of machine oroperating system. This file is included by the library makefile`Makerules', which is used by the top-level makefile and thesubdirectory makefiles. It can change the variables set in theincluding makefile or add new rules. It can use GNU makeconditional directives based on the variable `subdir' (see above) toselect different sets of variables and rules for different sections ofthe library. It can also set the make variable`sysdep-routines', to specify extra modules to be included in thelibrary. You should use `sysdep-routines' rather than addingmodules to `routines' because the latter is used in determiningwhat to distribute for each subdirectory of the main source tree.Each makefile in a subdirectory in the ordered list of subdirectories tobe searched is included in order. Since several system-dependentmakefiles may be included, each should append to `sysdep-routines'rather than simply setting it:

`Subdirs'

This file contains the names of new whole subdirectories under thetop-level library source tree that should be included for this system.These subdirectories are treated just like the system-independentsubdirectories in the library source tree, such as `stdio' and`math'.Use this when there are completely new sets of functions and headerfiles that should go into the library for the system this subdirectoryof `sysdeps' implements. For example,`sysdeps/unix/inet/Subdirs' contains `inet'; the `inet'directory contains various network-oriented operations which only makesense to put in the library on systems that support the Internet.

`Dist'

This file contains the names of files (relative to the subdirectory of`sysdeps' in which it appears) which should be included in thedistribution. List any new files used by rules in the `Makefile'in the same directory, or header files used by the source files in thatdirectory. You don't need to list files that are implementations(either C or assembly source) of routines whose names are given in themachine-independent makefiles in the main source tree.

`configure'

This file is a shell script fragment to be run at configuration time.The top-level `configure' script uses the shell . command toread the `configure' file in each system-dependent directorychosen, in order. The `configure' files are often generated from`configure.in' files using Autoconf.A system-dependent `configure' script will usually add things tothe shell variables `DEFS' and `config_vars'; see thetop-level `configure' script for details. The script can check for`--with-package' options that were passed to thetop-level `configure'. For an option`--with-package=value'`configure' sets theshell variable `with_package' (with any dashes inpackage converted to underscores) to value; if the option isjust `--with-package' (no argument), then it sets`with_package' to `yes'.

`configure.in'

This file is an Autoconf input fragment to be processed into the file`configure' in this subdirectory. See section `Introduction' in Autoconf: Generating Automatic Configuration Scripts,for a description of Autoconf. You should write either `configure'or `configure.in', but not both. The first line of`configure.in' should invoke the m4 macro`GLIBC_PROVIDES'. This macro does several AC_PROVIDE callsfor Autoconf macros which are used by the top-level `configure'script; without this, those macros might be invoked again unnecessarilyby Autoconf.

That is the general system for how system-dependencies are isolated.The next section explains how to decide what directories in`sysdeps' to use. section Porting the GNU C Library to Unix Systems, has some tips on portingthe library to Unix variants.

Layout of the `sysdeps' Directory Hierarchy

Gnu C Library Reference

A GNU configuration name has three parts: the CPU type, themanufacturer's name, and the operating system. `configure' usesthese to pick the list of system-dependent directories to look for. Ifthe `--nfp' option is not passed to `configure', thedirectory `machine/fpu' is also used. The operating systemoften has a base operating system; for example, if the operatingsystem is `sunos4.1', the base operating system is `unix/bsd'.The algorithm used to pick the list of directories is simple:`configure' makes a list of the base operating system,manufacturer, CPU type, and operating system, in that order. It thenconcatenates all these together with slashes in between, to produce adirectory name; for example, the configuration `sparc-sun-sunos4.1'results in `unix/bsd/sun/sparc/sunos4.1'. `configure' thentries removing each element of the list in turn, so`unix/bsd/sparc' and `sun/sparc' are also tried, among others.Since the precise version number of the operating system is often notimportant, and it would be very inconvenient, for example, to haveidentical `sunos4.1.1' and `sunos4.1.2' directories,`configure' tries successively less specific operating system namesby removing trailing suffixes starting with a period.

As an example, here is the complete list of directories that would betried for the configuration `sparc-sun-sunos4.1' (without the`--nfp' option):

Different machine architectures are conventionally subdirectories at thetop level of the `sysdeps' directory tree. For example,`sysdeps/sparc' and `sysdeps/m68k'. These containfiles specific to those machine architectures, but not specific to anyparticular operating system. There might be subdirectories forspecializations of those architectures, such as`sysdeps/m68k/68020'. Code which is specific to thefloating-point coprocessor used with a particular machine should go in`sysdeps/machine/fpu'.

There are a few directories at the top level of the `sysdeps'hierarchy that are not for particular machine architectures.

`stub'

As described above (see section Porting the GNU C Library), these are the two subdirectoriesthat every configuration implicitly uses after all others.

`ieee754'

This directory is for code using the IEEE 754 floating-point format,where the C type float is IEEE 754 single-precision format, anddouble is IEEE 754 double-precision format. Usually thisdirectory is referred to in the `Implies' file in a machinearchitecture-specific directory, such as `m68k/Implies'.

`posix'

This directory contains implementations of things in the library interms of POSIX.1 functions. This includes some of the POSIX.1functions themselves. Of course, POSIX.1 cannot be completelyimplemented in terms of itself, so a configuration using just`posix' cannot be complete.

`unix'

This is the directory for Unix-like things. See section Porting the GNU C Library to Unix Systems.`unix' implies `posix'. There are some special-purposesubdirectories of `unix':

This directory is for things common to both BSD and System V release 4.Both `unix/bsd' and `unix/sysv/sysv4' imply `unix/common'.

`unix/inet'

This directory is for socket and related functions on Unix systems.The `inet' top-level subdirectory is enabled by `unix/inet/Subdirs'.`unix/common' implies `unix/inet'.

`mach'

This is the directory for things based on the Mach microkernel from CMU(including the GNU operating system). Other basic operating systems(VMS, for example) would have their own directories at the top level ofthe `sysdeps' hierarchy, parallel to `unix' and `mach'.

Porting the GNU C Library to Unix Systems

Most Unix systems are fundamentally very similar. There are variationsbetween different machines, and variations in what facilities areprovided by the kernel. But the interface to the operating systemfacilities is, for the most part, pretty uniform and simple.

The code for Unix systems is in the directory `unix', at the toplevel of the `sysdeps' hierarchy. This directory containssubdirectories (and subdirectory trees) for various Unix variants.

The functions which are system calls in most Unix systems areimplemented in assembly code in files in `sysdeps/unix'. Thesefiles are named with a suffix of `.S'; for example,`__open.S'. Files ending in `.S' are run through the Cpreprocessor before being fed to the assembler.

These files all use a set of macros that should be defined in`sysdep.h'. The `sysdep.h' file in `sysdeps/unix'partially defines them; a `sysdep.h' file in another directory mustfinish defining them for the particular machine and operating systemvariant. See `sysdeps/unix/sysdep.h' and the machine-specific`sysdep.h' implementations to see what these macros are and whatthey should do.

Gnu C Tutorial

The system-specific makefile for the `unix' directory (that is, thefile `sysdeps/unix/Makefile') gives rules to generate several filesfrom the Unix system you are building the library on (which is assumedto be the target system you are building the library for). Allthe generated files are put in the directory where the object files arekept; they should not affect the source tree itself. The filesgenerated are `ioctls.h', `errnos.h', `sys/param.h', and`errlist.c' (for the `stdio' section of the library).

Contributors to the GNU C Library

The GNU C library was written originally by Roland McGrath. Some partsof the library were contributed or worked on by other people.

Gnu C Library On Windows

• The getopt function and related code were written byRichard Stallman, David J. MacKenzie, and Roland McGrath.
• The merge sort function qsort was written by Michael J. Haertel.
• The quick sort function used as a fallback by qsort was writtenby Douglas C. Schmidt.
• The memory allocation functions malloc, realloc andfree and related code were written by Michael J. Haertel.
• Fast implementations of many of the string functions (memcpy,strlen, etc.) were written by .
• The `tar.h' header file was written by David J. MacKenzie.
• The port to the MIPS DECStation running Ultrix 4(mips-dec-ultrix4)was contributed by Brendan Kehoe and Ian Lance Taylor.
• The DES encryption function crypt and related functions werecontributed by Michael Glad.
• The ftw function was contributed by Ian Lance Taylor.
• The startup code to support SunOS shared libraries was contributed byTom Quinn.
• The mktime function was contributed by Paul Eggert.
• The port to the Sequent Symmetry running Dynix version 3(i386-sequent-bsd) was contributed by Jason Merrill.
• The timezone support code is derived from the public-domain timezonepackage by Arthur David Olson and his many contributors.
• The port to the DEC Alpha running OSF/1 (alpha-dec-osf1) wascontributed by Brendan Kehoe, using some code written by Roland McGrath.
• The port to SGI machines running Irix 4 (mips-sgi-irix4) wascontributed by Tom Quinn.
• The port of the Mach and Hurd code to the MIPS architecture(mips-anything-gnu) was contributed by Kazumoto Kojima.
• The floating-point printing function used by printf and friendsand the floating-point reading function used by scanf,strtod and friends were written by Ulrich Drepper. Themulti-precision integer functions used in those functions are taken fromGNU MP, which was contributed by .
• The internationalization support in the library, and the supportprograms locale and localedef, were written by UlrichDrepper. Ulrich Drepper adapted the support code for message catalogs(`libintl.h', etc.) from the GNU gettext package, which healso wrote. He also contributed the catgets support and theentire suite of multi-byte and wide-character support functions(`wctype.h', `wchar.h', etc.).
• The implementations of the `nsswitch.conf' mechanism and the filesand DNS backends for it were designed and written by Ulrich Drepper andRoland McGrath, based on a backend interface defined by Peter Eriksson.
• The port to Linux i386/ELF (i386-anything-linux) wascontributed by Ulrich Drepper, based in large part on work done inHongjiu Lu's Linux version of the GNU C Library.
• The port to Linux/m68k (m68k-anything-linux) wascontributed by Andreas Schwab.
• Richard Henderson contributed the ELF dynamic linking code and othersupport for the Alpha processor.
• David Mosberger-Tang contributed the port to Linux/Alpha(alpha-anything-linux).
• Stephen R. van den Berg contributed a highly-optimized strstr function.
• Ulrich Drepper contributed the hsearch and drand48families of functions; reentrant `..._r' versions of therandom family; System V shared memory and IPC support code; andseveral highly-optimized string functions for ix86 processors.
• The math functions are taken from fdlibm-5.1 by SunMicrosystems, as modified by J.T. Conklin, Ian Lance Taylor,Ulrich Drepper, Andreas Schwab, and Roland McGrath.
• The libio library used to implement stdio functions onsome platforms was written by Per Bothner and modified by Ulrich Drepper.
• The Internet-related code (most of the `inet' subdirectory) andseveral other miscellaneous functions and header files have beenincluded from 4.4 BSD with little or no modification.All code incorporated from 4.4 BSD is under the following copyright:

  Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:

  1. Redistributions of source code must retain the above copyrightnotice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyrightnotice, this list of conditions and the following disclaimer in thedocumentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this softwaremust display the following acknowledgement:

     This product includes software developed by the University ofCalifornia, Berkeley and its contributors.

  4. Neither the name of the University nor the names of its contributorsmay be used to endorse or promote products derived from this softwarewithout specific prior written permission.

  THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS 'AS IS' ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSEARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODSOR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAYOUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.

• The random number generation functions random, srandom,setstate and initstate, which are also the basis for therand and srand functions, were written by Earl T. Cohenfor the University of California at Berkeley and are copyrighted by theRegents of the University of California. They have undergone minorchanges to fit into the GNU C library and to fit the ISO C standard,but the functional code is Berkeley's.
• The Internet resolver code is taken directly from BIND 4.9.5, which isunder both the Berkeley copyright above and also:

  Portions Copyright © 1993 by Digital Equipment Corporation.

  Permission to use, copy, modify, and distribute this software for anypurpose with or without fee is hereby granted, provided that the abovecopyright notice and this permission notice appear in all copies, andthat the name of Digital Equipment Corporation not be used inadvertising or publicity pertaining to distribution of the document orsoftware without specific, written prior permission.

  THE SOFTWARE IS PROVIDED 'AS IS' AND DIGITAL EQUIPMENT CORP.DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALLIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALLDIGITAL EQUIPMENT CORPORATION BE LIABLE FOR ANY SPECIAL, DIRECT,INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTINGFROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTIONWITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

• The code to support Sun RPC is taken verbatim from Sun'sRPCSRC-4.0 distribution, and is covered by this copyright:

  Sun RPC is a product of Sun Microsystems, Inc. and is provided forunrestricted use provided that this legend is included on all tape mediaand as a part of the software program in whole or part. Users may copyor modify Sun RPC without charge, but are not authorized to license ordistribute it to anyone else except as part of a product or programdeveloped by the user.

  SUN RPC IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND INCLUDING THEWARRANTIES OF DESIGN, MERCHANTIBILITY AND FITNESS FOR A PARTICULARPURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE.

  Sun RPC is provided with no support and without any obligation on thepart of Sun Microsystems, Inc. to assist in its use, correction,modification or enhancement.

  SUN MICROSYSTEMS, INC. SHALL HAVE NO LIABILITY WITH RESPECT TO THEINFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY PATENTS BY SUN RPCOR ANY PART THEREOF.

  In no event will Sun Microsystems, Inc. be liable for any lost revenueor profits or other special, indirect and consequential damages, even ifSun has been advised of the possibility of such damages.

• Some of the support code for Mach is taken from Mach 3.0 by CMU,and is under the following copyright terms:

  Permission to use, copy, modify and distribute this software and itsdocumentation is hereby granted, provided that both the copyrightnotice and this permission notice appear in all copies of thesoftware, derivative works or modified versions, and any portionsthereof, and that both notices appear in supporting documentation.

  CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS 'AS IS'CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FORANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.

  Carnegie Mellon requests users of this software to return to

  or <[email protected]> any improvements orextensions that they make and grant Carnegie Mellon the rights toredistribute these changes.

Glibc

Go to the first, previous, next, last section, table of contents.