On Mar 18, 2016 4:38 AM, "Burton, Ross" <ross.bur...@intel.com> wrote: > > > On 18 March 2016 at 00:22, Khem Raj <raj.k...@gmail.com> wrote: >>> >>> Which is interesting as building apr-native (so the site files don't get used) for x86-64 gives: >>> >>> apr_cv_process_shared_works=yes >>> >>> Can we not go around disabling stuff when it actually does work? >> >> >> No it really doesnt work. its running a configure time test on your build host ( which I assume is x86_64 mostly now >> a days) and then deciding that process shared mutexes work, which is not correct. >> >> If we think that it should work on x86_64 then lets cache the value to ‘yes’ but not leave it >> at the mercy of configure. > > > That was my point: the patch was to add works=no to x86-64 target builds, but if I run the same test on x86-64 hardware directly then the result is works=yes.
Actually it depends on libc implementation of process shared mutexes. So glibc for most arches should set it yes. Musl doesnt have it. So that should be no mostly > > Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
