| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 |
| From: | mdavidsaver via Core-talk <core-talk at aps.anl.gov> |
| To: | mp+394327 at code.launchpad.net |
| Date: | Mon, 23 Nov 2020 19:53:59 -0000 |
> I tried the simply minded (early morning) test of removing the two #undef lines. Turns out I have a quick answer for this. Some ~emulated environments don't fully support the PI futex() operations. (eg. rr-project.org) In these cases pthread_mutex_init() fails with ENOTSUP. It seems like the right approach is to probe, as is done in osdThread.c, to see if PI mutex is available. -- https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/394327 Your team EPICS Core Developers is subscribed to branch epics-base:7.0.