| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Don't use epics-base with WSL 1 (Re: SoftIoc with Warning: Unable to clear IP_MULTICAST_ALL on Ubunto on WSL) |
| From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "J. Lewis Muir" <jlmuir at imca-cat.org> |
| Cc: | Carsten Winkler <carsten.winkler at helmholtz-berlin.de>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Wed, 29 Nov 2023 10:19:33 -0800 |
On 11/28/23 08:37, J. Lewis Muir wrote:
On 11/24, Michael Davidsaver via Tech-talk wrote:Both PVA and CA protocols depend on less common features of TCP/IP stacks which behave slightly differently on Linux vs. Windows vs. BSD. Over the years, we have identified a set of workarounds for these "quirks". Of course this depend on being able to identify which TCP/IP stack implementation is actually *running*. A build time check is not sufficient. With WSL 1, I was not able to find a reliable way to identify that this "Linux" host actually has Windows IP stack quirks. The opposite situation exists with WINE where a "Windows" host actually has Linux IP stack quirks. Unlike WSL 1, this situation can be detected at runtime.If a certain property can't be detected at run time but needs to be, how about providing a way to set the property at run time since the user will know what it should be set to?
Personally, I don't think WSL1 is worth my effort at this point. However, as I have said. EPICS is what contributors make it.