I noticed a typo while looking at the file. It doesn't change a value but
worth fixing since I spotted it.
(From OE-Core rev: 84b407ca5542a6fa828c4b0c62ff60964db73901)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As with the other ac_cv_func_posix_* functions, this is specific to the
libc and not the architecture.
(From OE-Core rev: 2e190f4e443d6c6e44c3f775ff74e8d14e880a59)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Copy-pasting has resulted in a ac_cv_uint -> ac_cv_unit typo spreading
across the mips* site files, fix this.
(From OE-Core rev: 2b50faa9e7c3fea8480d608c4ef8c24837c7f52a)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The check for working abstract sockets was removed from dbus in 2017[1]
and dbus-glib in 2014[2].
[1] 6a6521746b
[2] e4a163431f
(From OE-Core rev: bb9d25a90287efa13b3ae4ca6edbbe319c597491)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
evolution-data-server hasn't used autoconf since 2016 (from 3.23.1), so
remove the now redundant entries for it.
(From OE-Core rev: e0f31024b4455d116fd00d84a6e046067ae4ff1d)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These assignments are libc-specific not architecture specific, so are
already set in the glibc and musl site files.
(From OE-Core rev: ad54be28c075fab7097f0deb00c11487a4b926db)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ac_cv_func_fnmatch_works (as set by AC_FUNC_FNMATCH) checks if the libc
has a POSIX-compliant fnmatch() implementation. This isn't architecture
specific, so move the definition to common-glibc and common-musl after
verifying the correct result.
(From OE-Core rev: b81ae7affa25eaad016c3ed347a9c4fef0bfee45)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
at-spi2-core is built with Meson now, so these values are not needed.
(From OE-Core rev: 319249ea639991d4d0a5f34be171d0ce7b44da0c)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable is used on some packages e.g. gpgme/libimobiledevice [1]
but with new autoconf, its better to let autconf detect it than cache it
here
[1] https://github.com/gpg/gpgme/blob/master/configure.ac#L659-L670
(From OE-Core rev: 1747608dfb1b2c8c4a40f819177d22f2bbae85df)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GLib 1.x is incredibly obsolete and GLib 2.x is built using Meson
not autotools, so we can remove the GLib entries from the site files.
Also fix a few copy/paste typos where glib_ was used incorrectly, for example:
ac_cv_sizeof_ptrdiff_t=${glib_cv_sizeof_ptrdiff_t=4}
The glib_cv_ should be ac_cv_.
(From OE-Core rev: 69e757e6bef8b1037e2f23121774af1d5f6c96df)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
off_t is always 64bit on musl regardless of 32bit or 64bit
architectures. autoconf has AC_SYS_LARGEFILE to detect correct off_t
size but it only work with glibc since it defines feature macros
_FILE_OFFSET_BITS=64 and _LARGEFILE_SOURCE but these macros are
not used on musl headers.
(From OE-Core rev: 09b3e8417d362b75f3b43a5a97b47700f97bf643)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Newer version of musl does not expose LFS64 interfaces, therefore
caching this is not right thing to do across both glibc and musl
moreover we will enable largefile support on glibc too therefore caching
it here is redundant.
(From OE-Core rev: ae427b04b5259136aae46f9254445251499c12e8)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes bash using its own broken getcwd() during cross compiling
The configure script assumes that your getcwd() function is broken.
Which then makes bash use it's own getcwd() implementation, which
doesn't work if the path to the current directory
contains bind mounts in its paths. This shows up as:
Fixes errors on musl images like
shell-init: error retrieving current directory: getcwd: cannot access parent directories: Bad file descriptor
(From OE-Core rev: 2137f68f6e84b669b5aba8f12237f164f710dba2)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There is a key difference between glibc and musl when it comes to
ppc/ppc64 and that is that musl does not support 128-bit long IBM doubles format
it only supports 128-bit long double IEEE format on ppc64 alone.
this change ensures that we account for this change, so far we have been
doing it a bit wrong for ppc/musl case.
(From OE-Core rev: 28cb148c1375ba242addba80b0f68e06d2a4d874)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libc_cv_ppc_machine and no longer exists in glibc
others are detected correctly in configure. They
perhaps made sense in past when the toolchain build has several
bootstrap stages
(From OE-Core rev: ba418f93fc586bb708fdfade4195f7f3be2e273f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
recipe for libidl has long been deleted
(From OE-Core rev: 587d0b51b09cd426dc4b2b7646fa063d10ae4f2f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The standard macros from gettext for iconv include problematic tests which
we've been patching out adhoc. Stop doing this and set results in the site
files instead which is simpler, more maintainable and peforms better too
as an added bonus.
(From OE-Core rev: 5a3bfdc4af18302cf0e3ea5802fdfefaa7235657)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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
(From OE-Core rev: 7c19f30849e9a73a7497d8e6c4719a2e57017086)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
They are preventing autotools from checking netinet/sctp.h existence
successfuly which in turn makes configure.ac files with lines similar to
this to fail, even if DEPENDS="lksctp-tools" and netinet/sctp.h is
clearly available under recipe-sysroot/:
AC_CHECK_HEADERS(netinet/sctp.h,,AC_MSG_ERROR(netinet/sctp.h not found))
This is the case for new libosmo-netif versionsi (meta-telephony branch
laforge/nightly), which expects netinet/sctp.h to be available if default
flag --enable-libsctp is used.
Without this patch, do_configure will fail unless following line is used
in the recipe:
CACHED_CONFIGUREVARS += "${@bb.utils.contains('PACKAGECONFIG', 'libsctp', 'ac_cv_header_netinet_sctp_h=yes', '',d)}"
So removing ac_cv_header_netinet_sctp_h would be enough, but I couldn't
find any good information on why the other 2 variables were set in site
config files, hence no good reason to keep them.
(From OE-Core rev: 6a641e744507c8c17fa3d7273cb2e5b512ca0242)
Signed-off-by: Pau Espin Pedrol <pespin@sysmocom.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: 65d38cc1ce5a106c4c2e5068b8440eb6e5a2b33e)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: c8429f707d9ac785f295492470ec8b9ff56c043b)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: 4522648758dc59f5ece736a0c1c0e95dcc7dafd1)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This coreutils / gnulib autoconf test is for a broken glibc
implementation of utimes from 2003-07-12 to 2003-09-17.
(From OE-Core rev: a60ca6048cc3a4fef862b128a842c70ac0cd2253)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
to set the file to the current time
(From OE-Core rev: 530e01e79e9674d0049b183dc23491eb886b066b)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: 692fe85264e599eb659456bd2eebf5f12a1cd30f)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: 506c3b5adaa2fdffa051d83fb99efc00e432156b)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: 525e33cf99983ee4bc3cf1822364123551aa7c83)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I.e. allocate memory for the pointer returned when the first
argument is NULL.
(From OE-Core rev: fe148da36af2dc086e05e2ebc1c088f1b5485de2)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I.e. shared text that is being executed.
(From OE-Core rev: 1370742d20aaa1a17f3e242ea9bb54df944b6416)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
calloc (N, S) returns non-NULL when N*S is zero,
and returns NULL when N*S overflows.
(From OE-Core rev: ba2bc4b6529013a303dd67abe944ceb619e7466c)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
their mkstemp() passes all tests from the gnulib m4 macro
gl_FUNC_MKSTEMP.
(From OE-Core rev: 2b0905d25fa295fc868bf6df1da89283b9dc1f45)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I.e. a memcmp() that is 8bit clean (like glibc).
(From OE-Core rev: d938ca1b8bc715047d771907c6ea4a1c9aa6594f)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I.e. a chown() that works when given -1 as uid / gid
(From OE-Core rev: 226b8b2b1b565ef019b442ad3bf1f5d86704e1d2)
Signed-off-by: André Draszik <git@andred.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed when powerpc64:
$ bitbake <image> -ctestsdk
[snip]
checking whether printf supports %p... configure: error: cannot run test program while cross compiling
See `config.log' for more details.
test_cvs (oeqa.sdk.buildcvs.BuildCvsTest) ... FAIL
[snip]
The cvs_cv_func_printf_ptr is already in powerpc32-linux.
(From OE-Core rev: cbba73baf94cd0ee99d010abab79140cd5e4b99e)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
These variables force runtime tests during configure
they are already cached for other architectures
(From OE-Core rev: 7a0e456d9dcfe9d9d9a0dbd24a6083c8d40516ff)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
coreutils configure script needs to know whether /proc/uptime is
available, but this is not possible in a cross-compilation
context. This leads to an uptime program that fails to work on the
target, as it has been compiled without /proc/uptime reading support.
This commit fixes that by telling coreutils at configure time that
/proc/uptime will be available on the target (which seems to be a
reasonable assumption on Linux systems).
This commit is made with great inspiration from Thomas Petazzoni's
patch to buildroot to fix the same issue.
(From OE-Core rev: 199b661c0699eb31df5bc73f2e3dce6a2db4585d)
Signed-off-by: Sean Nyekjaer <sean.nyekjaer@prevas.dk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The value was hardcoded from the time it couldn't be computed, which
is no longer the case. After C99 'bool' is only defined if stdbool.h
is included, it's implementation defined and not required to be 1, so
caching it doesn't make sense and certain recipes whoose code test
ac_cv_sizeof_bool fail to build.
(From OE-Core rev: 15af2d527d582ef181d6b9c042844aa89f991f0b)
Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are tools in the wild where we need this to be a full path, even
if that doesn't make sense in most other cases due to libtool issues.
Allow those cases to override the default value as currently its near
impossible to do so.
(From OE-Core rev: 65652f419a4c8578121f1f67d43f23ce4eae5a37)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
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.
(From OE-Core rev: 93dd7c87cef4fd9c22a09857fb55218c8be87b5b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add linux site info for the MicroBlaze architecture. This is based on
the site info from meta-xilinx and additional options based on config
options that other *-linux architecture site info files define.
(From OE-Core rev: def626a46efdeeaf867a27464aed463d265d777c)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
