We do not want bash to use internal code for getcwd() because
it can fail in certain filesystem types. Trust that the function
in glibc is not "broken".
(From OE-Core rev: 72539c68e4a6ef1497af3f707107c3a69ab37bbd)
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
util-macros 1.18 will look in the autoconf cache for this value so instead of
using overrides in xorg-lib-common, use the per-libc site cache.
Alert readers may notice that the site file claims that glibc returns NULL from
malloc(), when the previous change (e628c8aba0189de30de2833882b9999ff3b6547a)
claimed that it didn't. The previous change was incorrect, whilst malloc(0)
returns a valid pointer, realloc(p,0) does in fact return NULL, so the Xlib
wrapper functions are needed.
(From OE-Core rev: ecbf3f81f6d2929921e57066c2dd327d41d8e286)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* instead of disabling the configure test and set it always true
use the site files to set it true for glibc/eglibc and false
for uclibc
* remove the patch
' tested only for uclibc
* bump PR
(From OE-Core rev: 812342e44e9e361a0fa93cfcfe65cf4dd6f2fb57)
Signed-off-by: Henning Heinold <heinold@inf.fu-berlin.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The coreutils configure script is unable determine how to get free
space from the Operating System when cross-compiling.
This changes caches the result of the "statfs2_bsize" test for the
coreutils configure script.
Both glibc and uclibc defines statfs as a two-argument function
and uses a struct statfs containing a f_bsize field. That's why
the fu_cv_sys_stat_statfs2_bsize variable has to be defined for
both libcs.
(From OE-Core rev: fa1eb21933a880aa20e4ca87574753b1ec272c3b)
Signed-off-by: Julian Pidancet <julian.pidancet@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Providing va_copy / __va_copy come down to the libc. va_val_copy
comes down to the architecture. Unfortunately it's assumed true
if not set, so we need to make sure to set this to false for
x86_64 where it is not true.
(From OE-Core rev: a54a803ed89969c2416bfa9d911fe4cf558e2391)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a libc feature, move there. Drop the ipsec-tools specific
test as ipsec-tools (a) assumes fine on cross-compile and (b) doesn't
support buggy getaddrinfo now.
(From OE-Core rev: bca50524921a870bf774e23973a834f20701f146)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Not in oe-core nor meta-oe and based on oe.dev, possibly incomplete.
(From OE-Core rev: dc678e674ba9c56feb150bf06829a44fbe4e2b5a)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These functions are determined by the C library so move them to common-glibc
and common-uclibc
(From OE-Core rev: 9226635ab28b5ca44ec04931d27c5c3313d56e61)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These are tests for glibc behavior which we have enabled in uclibc.
Note that if we ever disable MALLOC_GLIBC_COMPAT the uclibc tests
will need to be changed (but I believe this would also entail massive
patching to the rest of userspace so this should be unlikely).
(From OE-Core rev: cab512d7ee50fb55b9412c0e1a52a589de09e0a7)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Joe Slater
Ross Burton
Henning Heinold
Julian Pidancet
Tom Rini
Richard Purdie
Richard Purdie
Marcin Juszkiewicz
Ross Burton