linux/poky.git/meta/site/arm-common, branch master

The poky repository master branch is no longer being updated.

2025-11-07T13:31:53+00:00

You can either: a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs b) use the new bitbake-setup You can find information about either approach in our documentation: https://docs.yoctoproject.org/ Note that "poky" the distro setting is still available in meta-yocto as before and we continue to use and maintain that. Long live Poky! Some further information on the background of this change can be found in: https://lists.openembedded.org/g/openembedded-architecture/message/2179 Signed-off-by: Richard Purdie

site: move ac_cv_func_posix_getpwnam_r to libc files

2024-06-07T22:21:43+00:00

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 Signed-off-by: Richard Purdie

site: remove obsolete evolution-data-server entries

2024-06-07T22:21:43+00:00

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 Signed-off-by: Richard Purdie

site: move ac_cv_func_fnmatch_works to libc files

2024-06-07T22:21:42+00:00

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 Signed-off-by: Richard Purdie

site: remove glib site values

2023-02-19T07:47:53+00:00

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 Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

site: Drop caching libIDL_cv_long_long_format

2021-09-23T12:49:11+00:00

recipe for libidl has long been deleted (From OE-Core rev: 587d0b51b09cd426dc4b2b7646fa063d10ae4f2f) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

site: Remove sctp related configs

2020-01-16T22:33:09+00:00

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 Signed-off-by: Richard Purdie

site: Move rsync_cv_HAVE_C99_VSNPRINTF to common-linux

2016-07-20T09:28:47+00:00

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 Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

siteinfo: Move apr configure cache to common-linux

2016-03-20T23:12:31+00:00

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 Signed-off-by: Richard Purdie

siteinfo: account for 32 and 64 bit arm

2014-12-23T10:18:17+00:00

Pull wordsize related items from arm-common and put in arm-32. Leave them as they were. Copy arm-32 to arm-64 and comment out all variables. Re-define to correct values leaving items which do not appear to be used undefined. (From OE-Core rev: 99d43a1554b2daeb7aba3c4582ccec758e6ec4a5) Signed-off-by: Joe Slater Signed-off-by: Richard Purdie