summaryrefslogtreecommitdiff
path: root/packages/python/python-fuse_cvs.bb
diff options
context:
space:
mode:
Diffstat (limited to 'packages/python/python-fuse_cvs.bb')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3 (git 2.25.1) at 2026-06-13 20:36:06 +0000
Ross Burton <ross.burton@intel.com> 2018-02-16site/common-linux: coreutils: get the uptime program to workSean Nyekjaer1 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. Signed-off-by: Sean Nyekjaer <sean.nyekjaer@prevas.dk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2018-01-13site/*-linux: don't cache ac_cv_sizeof_boolIoan-Adrian Ratiu3 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. Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 2018-01-04site/common: Allow ac_cv_path_SED to be overriddenRichard Purdie1 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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2017-12-09site: consolidate ac_cv_func_mmap_fixed_mapped definitionsRoss Burton5 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. Signed-off-by: Ross Burton <ross.burton@intel.com> 2017-11-21site/microblaze-linux: Add MicroBlaze linux site infoNathan Rossi1 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. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 2017-11-05site: Add riscv32 and riscv64Khem Raj2 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 2017-10-06siteinfo: nios2-linux - remove wrong mutex infoJuro Bystricky1 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. Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 2017-08-16site/ix86-common: Drop ac_cv_sizeof_ino_t as it can be incorrect with large ↵Richard Purdie3 file support 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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2017-06-16meta: Remove further uclibc remnants (inc. patches and site files)Richard Purdie8 Some of these are clearly dead, e.g. one binutils patch reverts the effects of the earlier one. This also removes the uclibc site files. We now have mechanisms to allow these to be extended from another layer should someone ever wish to do that. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>