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.

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>

ccache's configure tries to do a runtime test to
determine hw_cv_func_snprintf_c99 and hw_cv_func_vsnprintf_c99
which wont work in OE.

c99 versions of these functions are provided on all
supported libc implementations in OE-Core

Signed-off-by: Khem Raj <raj.khem@gmail.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.

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

If you profile gettext do_configure you notice it has some "sleep 1"
type events occurring. This patch ensures we cache the right values to
avoid those pointless delays there and in any other configure scripts
using the same macros.

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

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>

If cross-compiling, apr's configure script assumes that pid_t is
64-bit which is wrong - it appears that 32-bit is a safe assumption
for Linux no matter what the architecture, so use that instead by
default.

This fixes Apache writing garbage to its pid file when built using apr
produced from this recipe.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

Rebased these patches to the newer code
	modified:   python-native/nohostlibs.patch
	modified:   python/01-use-proper-tools-for-cross-build.patch
	modified:   python/06-avoid_usr_lib_termcap_path_in_linking.patch
	modified:   python/06-ctypes-libffi-fix-configure.patch
	modified:   python/multilib.patch

Deleted these patches are the are now upstream
	deleted:    python/02-remove-test-for-cross.patch
	deleted:    python/security_issue_2254_fix.patch

Added this patch to python-native
	new file:   python-native/multilib.patch

Updated site config file for python
	modified:   ../../site/common-linux : add ac_cv_have_long_long_format for python
	avoid this error in python:
	Include/pyport.h:243:13: error: #error "This platform's pyconfig.h needs to define PY_FORMAT_LONG_LONG"

Updated default python version
	modified:   ../../conf/distro/include/default-versions.inc

Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>

Change in site files is needed since in cross
build envrionment the test to check for
gl_cv_func_fstatat_zero_flag is a runtime test

Signed-off-by: Khem Raj <raj.khem@gmail.com>

Signed-off-by: Tom Rini <tom_rini@mentor.com>

This comes from oe.dev which had this set for arm-linux only.

Signed-off-by: Tom Rini <tom_rini@mentor.com>