mirror of
https://git.musl-libc.org/git/musl
synced 2025-01-10 08:42:02 +03:00
0b6b43ed3f
unfortunately traditional i386 practice was to use "long" rather than "int" for wchar_t, despite the latter being much more natural and logical. we followed this practice, but it seems some compilers (clang and maybe certain gcc builds or others too..?) have switched to using int, resulting in spurious pointer type mismatches when L"..." wide strings are used. the best solution I could find is to use the compiler's definition of wchar_t if it exists, and otherwise fallback to the traditional definition. there's no point in duplicating this approach on 64-bit archs, as their only 32-bit type is int. |
||
---|---|---|
arch | ||
crt | ||
dist | ||
include | ||
lib | ||
src | ||
tools | ||
COPYING | ||
COPYRIGHT | ||
INSTALL | ||
Makefile | ||
README | ||
WHATSNEW |
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.etalabs.net/musl/ For installation instructions, see the INSTALL file. Please refer to the COPYRIGHT file for details on the copyright status of code included in musl, and the COPYING file for the license (LGPL) under which the library as a whole is distributed. Greetings libc hackers! This package is an _alpha_ release of musl, intended for the curious and the adventurous. While it can be used to build a complete small Linux system (musl is self-hosted on the system I use to develop it), at this point doing so requires a lot of manual effort. Nonetheless, I hope low-level Linux enthusiasts will try out building some compact static binaries with musl using the provided gcc wrapper (which allows you to link programs with musl on a "standard" glibc Linux system), find whatever embarassing bugs I've let slip through, and provide feedback on issues encountered building various software against musl. 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 trying out musl. Cheers, Rich Felker / dalias