Dear EPICS experts,
I'm confused with libca.so (Channel Access) dependency on readline:
.../base-3.15.9% ldd lib/linux-x86_64/libca.so.3.15.9
linux-vdso.so.1 => (0x00007ffedfcf0000)
libCom.so.3.15.9 => /tmp/x/base-3.15.9/lib/linux-x86_64/libCom.so.3.15.9 (0x00007fcd4fd3e000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fcd4faf5000)
libreadline.so.6 => /lib64/libreadline.so.6 (0x00007fcd4f8af000)
^^^^^^^^^^^^^^^^
librt.so.1 => /lib64/librt.so.1 (0x00007fcd4f6a7000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fcd4f4a2000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fcd4f199000)
libm.so.6 => /lib64/libm.so.6 (0x00007fcd4ee97000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fcd4ec80000)
libc.so.6 => /lib64/libc.so.6 (0x00007fcd4e8bf000)
/lib64/ld-linux-x86-64.so.2 (0x00007fcd5021d000)
libtinfo.so.5 => /lib64/libtinfo.so.5 (0x00007fcd4e695000)
The same applies to libcas.so (Portable Channel Access):
.../base-3.15.9% ldd lib/linux-x86_64/libcas.so.3.15.9
linux-vdso.so.1 => (0x00007fff46ff3000)
libca.so.3.15.9 => /tmp/x/base-3.15.9/lib/linux-x86_64/libca.so.3.15.9 (0x00007f133ec63000)
libgdd.so.3.15.9 => /tmp/x/base-3.15.9/lib/linux-x86_64/libgdd.so.3.15.9 (0x00007f133ea2e000)
libCom.so.3.15.9 => /tmp/x/base-3.15.9/lib/linux-x86_64/libCom.so.3.15.9 (0x00007f133e7ba000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f133e572000)
libreadline.so.6 => /lib64/libreadline.so.6 (0x00007f133e32b000)
^^^^^^^^^^^^^^^^
librt.so.1 => /lib64/librt.so.1 (0x00007f133e123000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f133df1f000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f133dc15000)
libm.so.6 => /lib64/libm.so.6 (0x00007f133d913000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f133d6fd000)
libc.so.6 => /lib64/libc.so.6 (0x00007f133d33b000)
/lib64/ld-linux-x86-64.so.2 (0x00007f133f112000)
libtinfo.so.5 => /lib64/libtinfo.so.5 (0x00007f133d111000)
Why do *network communication* libraries depend on commandline editing
library?
Is this really required or is it a known bug?
Interestingly, 7.0.7 is free of this problem:
.../base-7.0.7% ldd ./lib/linux-x86_64/libca.so.4.14.2
linux-vdso.so.1 => (0x00007ffe3e124000)
libCom.so.3.22.0 => /tmp/x/base-7.0.7/lib/linux-x86_64/libCom.so.3.22.0 (0x00007f0268bd2000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0268989000)
librt.so.1 => /lib64/librt.so.1 (0x00007f0268781000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f026857d000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f0268273000)
libm.so.6 => /lib64/libm.so.6 (0x00007f0267f71000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f0267d5b000)
libc.so.6 => /lib64/libc.so.6 (0x00007f0267999000)
/lib64/ld-linux-x86-64.so.2 (0x00007f02690b1000)
P.S. Yes, I'm aware of a "COMMANDLINE_LIBRARY=EPICS" flag (which took some
time to figure out :D), but the question remains -- why any commandline
editing is needed for network communication libraries at all?
With best regards,
Dmitry
- Replies:
- Re: Why does libca.so depend on libreadline.so? Michael Davidsaver via Tech-talk
- Navigate by Date:
- Prev:
Re: Epics Archiver Online Status Question [SEC=OFFICIAL] Manoussakis, Adamandios via Tech-talk
- Next:
Job Opportunity at the Canadian Light Source Gillian Black via Tech-talk
- 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
- Navigate by Thread:
- Prev:
Re: timestampField not retrieved using CA provider for pvac::ClientChannel Bisegni, Claudio via Tech-talk
- Next:
Re: Why does libca.so depend on libreadline.so? Michael Davidsaver via Tech-talk
- 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
|