summaryrefslogtreecommitdiffstats
path: root/recipes-extended/mc/mc_4.7.5.2.bb
diff options
context:
space:
mode:
authorAndre' Draszik <git@andred.net>2020-01-08 21:06:57 +0000
committerRoss Burton <ross.burton@intel.com>2020-01-09 23:57:41 +0000
commitd5db235310067251c66d3e2e160dea68f9b362b4 (patch)
treeae74dcb35be5917f9aff0137acf0feda0e0642d9 /recipes-extended/mc/mc_4.7.5.2.bb
parent0f2176364f0faaab18f098aa24925c3ba9ef30df (diff)
downloadmeta-gplv2-d5db235310067251c66d3e2e160dea68f9b362b4.tar.gz
diffutils: use malloc() and realloc() from libc as-is
diffutils' version of autoconf tries to run a test program to determine if malloc() and realloc() behave like in glibc, i.e. returning non-NULL when given 0 as size. Running a test program doesn't work when cross- compiling, so it defaults to assuming different behaviour and compiles wrappers around malloc() & realloc(). Given they behave the same in musl (these days), and given uClibc isn't supported anymore, we can specify the test-result, and avoid having to use diffutil's replacement functions. jm_cv_func_working_malloc and jm_cv_func_working_realloc are similar to ac_cv_func_malloc_0_nonnull and ac_cv_func_realloc_0_nonnull, which oe-core sets in the site configuration in meta/site/, except that the former two are the flags for the older version of autoconf used by this package. Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'recipes-extended/mc/mc_4.7.5.2.bb')
0 files changed, 0 insertions, 0 deletions