RE: IOC using Sequencer Module Attempting to use libCom.so.3.18.1

["Srinivas, Dhruv via Tech-talk" <tech-talk at aps.anl.gov>]

Unfortunately, that hasn't worked for me. I've cleaned then remade the various dependencies in use, as well as cleaned and remade my epics code itself. However I'm still receiving the same error message.

-----Original Message-----
From: Michael Davidsaver <mdavidsaver at gmail.com> 
Sent: Tuesday, July 18, 2023 9:22 AM
To: Srinivas, Dhruv <srinivas1 at llnl.gov>
Cc: Wang, Andrew <wang126 at llnl.gov>; tech-talk at aps.anl.gov
Subject: Re: IOC using Sequencer Module Attempting to use libCom.so.3.18.1

On 7/18/23 09:03, Srinivas, Dhruv via Tech-talk wrote:
> To whom it may concern,
> 
> I’ve been having some unexpected issues when trying to make an IOC 
> that uses EPICS-seq (sequencer version 2.2.9). From what I’ve been 
> able to determine, I am adding the .st files to the Makefile in the 
> src directory correctly. In that they’re being added in the following 
> format: IOCName_SRCS += someFile.st
> 
> I have also verified that I’m adding the seq and pv libraries as 
> follows: IOCName_LIBS += seq pv
> 
> 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.
> 
> 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. Additionally, if I manually compile the .st files into .c files, and adjust the Makefile, I am able to build the IOC. I was wondering if someone knew why this was the case, as well as what could be done to allow it to build properly using .st files directly.

You need to clean and rebuild (at least) SEQSNC.

A likely scenario is that epics-base, and perhaps other modules, were updated without rebuilding all dependent modules.


> Sincerely,
> 
> Dhruv Srinivas
> 
> srinivas1 at llnl.gov <mailto:srinivas1 at llnl.gov>
>