Go to file
Rich Felker 7603c5f127 support mix of IPv4 and v6 nameservers in resolv.conf
a v6 socket will only be used if there is at least one v6 nameserver
address. if the kernel lacks v6 support, the code will fall back to
using a v4 socket and requests to v6 servers will silently fail. when
using a v6 socket, v4 addresses are converted to v4-mapped form and
setsockopt is used to ensure that the v6 socket can accept both v4 and
v6 traffic (this is on-by-default on Linux but the default is
configurable in /proc and so it needs to be set explicitly on the
socket level). this scheme avoids increasing resource usage during
lookups and allows the existing network io loop to be used without
modification.

previously, nameservers whose address family did not match the address
family of the first-listed nameserver were simply ignored. prior to
recent __ipparse fixes, they were not ignored but erroneously parsed.
2013-11-30 13:33:29 -05:00
arch add O_TMPFILE flag, new in linux 3.11 2013-11-23 23:47:48 +00:00
crt add function types to arm crt assembly 2013-08-15 14:52:27 -04:00
dist add another example option to dist/config.mak 2012-04-24 16:49:11 -04:00
include increase TTY_NAME_MAX limit to 32 2013-11-29 12:45:09 -05:00
lib new solution for empty lib dir (old one had some problems) 2011-02-17 17:12:52 -05:00
src support mix of IPv4 and v6 nameservers in resolv.conf 2013-11-30 13:33:29 -05:00
tools replace system's install command with a shell script 2013-08-17 22:21:11 -04:00
.gitignore new gcc wrapper, entirely specfile based 2012-04-22 14:32:49 -04:00
configure remove -Wcast-align from --enable-warnings 2013-08-28 05:08:16 -04:00
COPYRIGHT add arm-optimized memcpy implementation from bionic libc 2013-08-14 03:06:21 -04:00
INSTALL fix some documentation typos 2013-08-22 22:40:30 -04:00
Makefile fix regression in creation of ldso symlink 2013-08-31 11:36:56 -04:00
README update documentation 2012-10-26 20:14:19 -04:00
WHATSNEW release notes for 0.9.14 2013-09-23 17:00:53 -04:00

musl libc - a new standard library to power a new generation of
Linux-based devices. musl is lightweight, fast, simple, free, and
strives to be correct in the sense of standards-conformance and
safety.

musl is an alternative to glibc, eglibc, uClibc, dietlibc, and klibc.
For reasons why one might prefer musl, please see the FAQ and libc
comparison chart on the project website,

    http://www.musl-libc.org/

For installation instructions, see the INSTALL file.

Please refer to the COPYRIGHT file for details on the copyright and
license status of code included in musl (standard MIT license).



Greetings!

The 0.9.x release series for musl features interface coverage for all
interfaces defined in ISO C99 and POSIX 2008 base, along with a number
of non-standardized interfaces for compatibility with Linux, BSD, and
glibc functionality. As the release series progresses, we are
gradually adding support for incomplete functionality in existing
interfaces, additional functions that are deemed to be important due
to their use in real-world software, and support for new library and
language features in C11 such as thread-local storage, which is now
supported on all targets. In addition, support for additional target
cpu architectures is being added.

The number of packages build successfully against musl - either
out-of-the-box or with minor patches to address portability errors -
has exceeded 5000 and is steadily growing. In addition to application
compatibility testing, unit testing has been conducted using three
separate test frameworks and numerous additional standalone test cases
to verify the correctness of the implementation.

Included with this package is a gcc wrapper script (musl-gcc) which
allows you to build musl-linked programs using an existing gcc 3.x or
4.x toolchain on the host. There are also now at several mini
distributions (in the form of build scripts) which provide a
self-hosting musl-based toolchain and system root. These are much
better options than the wrapper script if you wish to use dynamic
linking or build packages with many library dependencies. See the musl
website for details.

The musl project is actively seeking contributors, mostly in the areas
of porting, testing, and application compatibility improvement. For
bug reports, support requests, or to get involved in development,
please visit #musl on Freenode IRC or subscribe to the musl mailing
list by sending a blank email to musl-subscribe AT lists DOT openwall
DOT com.

Thank you for using musl.

Cheers,

Rich Felker / dalias