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>
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>
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>
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>
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>
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>
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>
With the commit afa9f769d62034d4443dfe929422d1d591adf709 some nios2 builds
(uboot, core-image-minimal, etc) were broken due to db trying to use ARM instructions
in mutexes. The reason was db "configure" used the cached entry from nios2-linux
(which was incorrect). So the remedy was to remove the incorrect cached entry
and let db "configure" figure out which is the proper mutex to use.
(From OE-Core rev: c17c6ba906425d4035b8e044c8bd8bd68c47ef74)
Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we do not cache is then configure in distcc will try
to compute it using AC_TRY_RUN which will give some result
on x86-64 host when target is x86-64 but it generally is wrong
for cross compilation. We therefore cache it for all linux
targets.
This issue is highlighted by clang when compiling distcc
where it figures that its cross compiling and therefore triggers
it to include its own implementation of snprintf() which does
not go well with clang, gcc compiles it fine thats why we
never saw the problem thus far.
(From OE-Core rev: e940dfcb5ad4017e5fe616c583253439603656db)
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>
The size of off_t depends on whether large file support is enabled through
preprocessor flags, so we can't cache this.
(From OE-Core rev: 25bd4e9483a7d2c16a460b4f363e91b5b943bb58)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There are variables which are used in all target specific
sitefiles. Move it to common-linux, so it can be effective
for all targets. Usually they will vary based upon libc
e.g. musl does not have process shared mutexes so apr_cv_process_shared_works
should be no for it. For glibc though it should be yes but
existing behaviour is to use 'no' so its left as it is.
(From OE-Core rev: 2c5135f2106842e1b5ef880a08dbd4e50c9e0d04)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
