EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20232024  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  <20232024 
<== Date ==> <== Thread ==>

Subject: Re: IOC using Sequencer Module Attempting to use libCom.so.3.18.1
From: "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>
To: "Srinivas, Dhruv" <srinivas1 at llnl.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Cc: "Wang, Andrew" <wang126 at llnl.gov>
Date: Tue, 18 Jul 2023 17:07:10 +0000
On 7/18/23 11:03 AM, Srinivas, Dhruv via Tech-talk wrote:
Additionally, looking at the error messages I’m getting, it seems that the IOC isn’t properly building the .st files into the .c files. When I run it, I receive a few error messages that are as follows:  

 

/filepathTosnc/snc: error while loading shared libraries: libCom.so.3.18.1: cannot open shared object file: No such file or directory

make[3]: *** No rule to make target ‘someFile.o', needed by IOCName.  Stop.

It looks like you have a problem when the build system tries to run the snc compiler, it needs a shared library which it can't find. Assuming "/filepathTosnc/snc" above isn't a literal quote from the error output, what does running "ldd /filepathTosnc/snc" (editing the path as necessary) produce? It probably shows a similar problem with finding that library.

If you configure your EPICS Base builds with LINKER_USE_RPATH=NO you are responsible for ensuring that the correct shared libraries can be found by any programs that need those EPICS shared libraries, in this case by sequencer state notation compiler. This kind of error that you're seeing is a direct result of a mis-match between the version needed by the snc executable and the version(s) available.

 

I believe I know why I’m receiving these errors. I have libCom.so.3.22.1 on my machine, so I think that the sequencer isn’t properly building the .st files.

The snc compiler that your build above is running above was built with a version of Base that provided libCom.so.3.18.1. You have to either rebuild that snc binary or install the older libCom.so alongside the new one where it will find it.

- Andrew
-- 
Complexity is free, it's Simplicity that takes work.

Replies:
RE: IOC using Sequencer Module Attempting to use libCom.so.3.18.1 Srinivas, Dhruv via Tech-talk
References:
IOC using Sequencer Module Attempting to use libCom.so.3.18.1 Srinivas, Dhruv via Tech-talk

Navigate by Date:
Prev: Re: PHAS and PINI Johnson, Andrew N. via Tech-talk
Next: RE: IOC using Sequencer Module Attempting to use libCom.so.3.18.1 Mark Rivers 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  <20232024 
Navigate by Thread:
Prev: RE: IOC using Sequencer Module Attempting to use libCom.so.3.18.1 Mark Rivers via Tech-talk
Next: RE: IOC using Sequencer Module Attempting to use libCom.so.3.18.1 Srinivas, Dhruv 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  <20232024 
ANJ, 18 Jul 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·