summaryrefslogtreecommitdiff
path: root/include/glob.h
AgeCommit message (Collapse)AuthorFilesLines
2019-08-06glob: implement GLOB_TILDE and GLOB_TILDE_CHECKIsmael Luceno1-0/+3
2014-09-05fix macros for LFS *64_t types in sys/stat.h, sys/types.h, glob.hSzabolcs Nagy1-0/+1
there is no blksize64_t (blksize_t is always long) but there are fsblkcnt64_t and fsfilcnt64_t types in sys/stat.h and sys/types.h. and glob.h missed glob64_t.
2012-09-07default features: make musl usable without feature test macrosRich Felker1-5/+1
the old behavior of exposing nothing except plain ISO C can be obtained by defining __STRICT_ANSI__ or using a compiler option (such as -std=c99) that predefines it. the new default featureset is POSIX with XSI plus _BSD_SOURCE. any explicit feature test macros will inhibit the default. installation docs have also been updated to reflect this change.
2012-09-06use restrict everywhere it's required by c99 and/or posix 2008Rich Felker1-1/+7
to deal with the fact that the public headers may be used with pre-c99 compilers, __restrict is used in place of restrict, and defined appropriately for any supported compiler. we also avoid the form [restrict] since older versions of gcc rejected it due to a bug in the original c99 standard, and instead use the form *restrict.
2012-06-04_GNU_SOURCE is supposed to imply _LARGEFILE64_SOURCERich Felker1-1/+1
this is ugly and stupid, but now that the *64 symbol names exist, a lot of broken GNU software detects them in configure, then either breaks during build due to missing off64_t definition, or attempts to compile without function declarations/prototypes. "fixing" it here is easier than telling everyone to add yet another feature test macro to their builds.
2012-05-04add support for ugly *64 functions with _LARGEFILE64_SOURCERich Felker1-0/+5
musl does not support legacy 32-bit-off_t whatsoever. off_t is always 64 bit, and correct programs that use off_t and the standard functions will just work out of the box. (on glibc, they would require -D_FILE_OFFSET_BITS=64 to work.) however, some programs instead define _LARGEFILE64_SOURCE and use alternate versions of all the standard types and functions with "64" appended to their names. we do not want code to actually get linked against these functions (it's ugly and inconsistent), so macros are used instead of prototypes with weak aliases in the library itself. eventually the weak aliases may be added at the library level for the sake of using code that was originally built against glibc, but the macros will still be the desired solution in the headers.
2011-02-12initial check-in, version 0.5.0v0.5.0Rich Felker1-0/+41