linux/poky.git/meta/site, branch uninative-1.9

site/risc-v: Cache common variables to build libIDL

2018-03-25T08:40:42+00:00

These variables force runtime tests during configure they are already cached for other architectures (From OE-Core rev: 7a0e456d9dcfe9d9d9a0dbd24a6083c8d40516ff) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

site/riscv: Shunt the realloc configure test for startup-notification

2018-03-15T13:27:19+00:00

(From OE-Core rev: c1d22fe95ea132275237854681c938d9238579cf) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

site/common-linux: coreutils: get the uptime program to work

2018-02-16T18:05:40+00:00

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

site/*-linux: don't cache ac_cv_sizeof_bool

2018-01-14T09:11:57+00:00

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

site/common: Allow ac_cv_path_SED to be overridden

2018-01-04T12:57:43+00:00

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

site: consolidate ac_cv_func_mmap_fixed_mapped definitions

2017-12-10T22:45:18+00:00

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

site/microblaze-linux: Add MicroBlaze linux site info

2017-11-21T13:06:12+00:00

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

site: Add riscv32 and riscv64

2017-11-05T22:33:21+00:00

(From OE-Core rev: ee3ec248700669fe9b8b589e4a513918949a26e3) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

siteinfo: nios2-linux - remove wrong mutex info

2017-10-07T22:20:40+00:00

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

site/ix86-common: Drop ac_cv_sizeof_ino_t as it can be incorrect with large file support

2017-08-15T23:03:15+00:00

Depending on whether large file support is enabled, the size of ino_t can be 4 or 8 on 32 bit x86. Drop the value from the site cache and allow the system to vary it depending on configuration. Very few other arches actually set this so its likely obsolete and doesn't need to be hardcoded anymore. Also drop the 64 bit and x32 variants since autodetection of this value appears to work fine and this avoids any confusion or sizing errors depending on large file support. (From OE-Core rev: 31ae16003cac6c8cf587c98d0c58e9f21690cb40) Signed-off-by: Richard Purdie