| 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: | SHRLIB_VESION Variable |
| From: | Abdalla Ahmad via Tech-talk <tech-talk at aps.anl.gov> |
| To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Sun, 28 Aug 2022 07:20:51 +0000 |
|
Hi How much is it important to set the SHRLIB_VERSION when building support modules? I know it is set by default to the base version when building EPICS base but it seems it is optional when building any support modules. I did this test in
our RPM setup, I had all support modules built using asyn 4.41 and I deployed an RPM for asyn 4.42, doing “yum install stream-device” failed because it explicitly asked for asyn 4.41 “libasyn.so.4.41”. I unset the variable in the base and removed it in the
support modules, it did update asyn and installed any module that uses asyn, but I am wondering how much this would affect compatibility and dependencies between modules. Thanks, Abdalla |