| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Issues building statically linked IOC |
| From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Érico Nogueira Rolim <erico.rolim at lnls.br> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Mon, 17 Oct 2022 13:49:04 -0700 |
On 10/17/22 11:08, Érico Nogueira Rolim via Tech-talk wrote:
Did I miss something about building a static IOC? Having to mess around in the epics-base files doesn't seem ideal... To cover all my bases, I also tried doing this on epics-base 7.0.7, which required the same steps to spit out a static executable.
The developers of glibc try to discourage completely static linking as some parts of libc.so will implicitly try to load plugin libraries for things like user account database and hostname lookup. There are also some hardcoded paths which distro libraries may have changed. https://stackoverflow.com/questions/57476533/why-is-statically-linking-glibc-discouraged (the first google result for "glibc static linking") Of course, there are some cases where this may not practically be avoided. Such as you describe where (I assume) you don't have access to the toolchain which was used to build the system libraries. In such a case I guess you will have to hope for the best!