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>
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>
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>
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>
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>
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>
Working with the meta-ros project we detected that the ROS nodes didn't launch properly
the reason was that by default apr_cv_mutex_recursive in apr is set to no and this leads
to the APRENOTIMPL return value of apr_thread_mutex_create in thread_mutex.c when
APR_THREAD_MUTEX_NESTED is requested via flags.
Added CACHED_CONFIGUREVARS += "apr_cv_mutex_recursive=yes" to sources/openembedded-core/meta/recipes-support/apr/apr_1.4.6.bb
to fix this issue. It has also been removed the mention of this variable in
meta/site/powerpc32-linux.
(From OE-Core rev: 20b9151f877978c086dcc8cbae7e0d9c9e89a45d)
Signed-off-by: Víctor Mayoral Vilches <v.mayoralv@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When compiling apr for no-powerpc arch, the flag ac_cv_o_nonblock_inherited
is always set to yes in cross compiling environment. This flag is intended to
think the socket, returned from accept(), inherit file status flags such as
O_NONBLOCK from the listening socket, but socket never inherits file status
from the listening socket on Linux (more information to man accept).
This is Linux-wide behaviour, so move it from meta/site/powerpc32-linux
to site/common-linux.
If ac_cv_o_nonblock_inherited is set to yes on Linux, clients can not access the
same ip address(URL) with Apache web server via http(port 80) and https(port443)
without redirection
(From OE-Core rev: f31a7ed3463e169dc93f36cc0bbe084d3f99772a)
Signed-off-by: Roy.Li <rongqing.li@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.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>
We were just setting this to the assumed default. If anything, this
belongs in the libc files if we must set it.
(From OE-Core rev: ae054a823909c5ebf03fec962844a213dc3fb8e1)
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>
Note that we had a number of unused and ignored settings wrt mutex
support. These have been dropped as they weren't being used and
implied some odd things to boot. This is also a partial resync with
oe.dev which had some, but not all of these changes.
(From OE-Core rev: 7cc52fca921259e331a34263d8113e29b9e0dee9)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Part of re-syncing with oe.dev, move samba_cv_HAVE_IFACE_* to common-linux
(From OE-Core rev: bf1e4b1f4952d2dd8e4acd6babb96b3c65999df0)
Signed-off-by: Tom Rini <tom_rini@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pulled common options that are needed for powerpc64-linux to build
out of powerpc32-linux and put them into powerpc-linux.
(From OE-Core rev: d5a42bb0382243d12388a0e0b18461c58d12c60e)
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
powerpc-common was really Linux PPC32 specific. So move all the options
in it to powerpc32-linux and we can refactor out common bits shared
between into powerpc-linux and powerpc-common.
(From OE-Core rev: 6ba64ae1030c879021f0ee0789bee4f8d3c135c0)
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
