summaryrefslogtreecommitdiffstats
path: root/meta/site/common-musl
AgeCommit message (Collapse)Author
2020-07-22site: Make sys_siglist default to noKhem Raj
glibc 2.32 has deprecated sys_siglist [1] since no is default for musl as well, therefore elevate it to common site file for all [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=b1ccfc061feee9ce616444ded8e1cd5acf9fa97f Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have working mktime()André Draszik
This coreutils (gnulib) test tests for various bugs that only exist in ancient versions. It defaults to assuming buggy behaviour with its own implementation when cross-compiling. musl and recent glibc (2.29) are not affected. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: strtod() works in glibc / muslAndré Draszik
autoconf has a test for strtod(), which assumes non-working when cross-compiling, but it does work in both musl and recent glibc. coreutils (gnulib) does some additional tests on top of that, but assumes working glibc when >= 2.8 when cross compiling. It doesn't know about musl where the additional tests also work, though. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: set nanosleep() behaviour for glibc / muslAndré Draszik
As per coreutils' (gnulib's) autotools test, nanosleep() misbehaves on glibc (2.29), and works fine on musl. During cross-compile, recent coreutils assume brokenness when compiling for linux, which pessimises musl. Set the correct result for musl, and for coherency reasons, also specify the result for glibc. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have working utimes()André Draszik
This coreutils / gnulib autoconf test is for a broken glibc implementation of utimes from 2003-07-12 to 2003-09-17. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have working getgroups()André Draszik
recent coreutils (gnulib) assume yes when cross-compiling for gnu (glibc), but don't know about musl. For coherence, just set the result to yes for both. Note that the old coreutils (from meta-gplv2) doesn't assume anything and instead that recipe hard-codes to yes. So behaviour with yocto when using meta-gplv2 is actually better than when using the latest version (when using musl). This patch rectifies this shortcoming. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: set getcwd() test result for abort()-bug for glibc / muslAndré Draszik
This coreutils (gnulib) test checks for an abort() that existed in glibc before 2.4.90-10 (in 2006) in certain conditions. Neither libraries exhibit this problem today. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: set getcwd() behaviour for long paths for glibc / muslAndré Draszik
In glibc, getcwd() handles long file names properly, on musl, getcwd() only works up to PATH_MAX directory depths. Configuring the autotools (gnulib) test result here allows coreutils to compile more optimised code for both platforms, rather than being pessimistic and re-implementing everything itself. The difference in behaviour is because both do the kernel getcwd syscall (which only supports up to PATH_MAX), but glibc implements fallbacks for longer paths, while musl doesn't. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have glibc compatible getcwd()André Draszik
I.e. allocate memory for the pointer returned when the first argument is NULL. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have glibc compatible calloc()André Draszik
calloc (N, S) returns non-NULL when N*S is zero, and returns NULL when N*S overflows. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have working mkstemp()André Draszik
their mkstemp() passes all tests from the gnulib m4 macro gl_FUNC_MKSTEMP. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl has working memcmp()André Draszik
I.e. a memcmp() that is 8bit clean (like glibc). Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-09site: consolidate ac_cv_func_mmap_fixed_mapped definitionsRoss Burton
This is the cache variable used by AC_FUNC_MMAP, which is possibly one of the worst autoconf macros to exist. Apart from being a runtime test which silently claims that mmap() is broken when cross-compiling, this is basically to verify that mmap() actually works, because SVR4.0 (released 1988) was broken. Thirty years later, everyone has a working mmap(). common-glibc already has an assignment, so add a corresponding assignment to common-musl and remove it from the machine-specific files. Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-05-30siteinfo, insane: Recognize musl specific tripletsKhem Raj
We will use '-musl' to identify musl based systems this patch lays the foundation for recognising those and map them to internal variable representations Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>