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  <20172018  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  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: synApps and external sequencer installation
From: Luca Cavalli <[email protected]>
To: "[email protected]" <[email protected]>
Date: Thu, 2 Feb 2017 09:00:01 +0000
Dear all,

I have a IOC using synApps 5.8 (for the "transform" record) and sequencer 2.2.4.
I cloned my IOC from XXX reference IOC in synApps as suggested by documentation.
If I set SNCSEQ variable pointing to my sequencer 2.2.4 installation on top of
my IOC RELEASE file, it gets ignored and my state machines are compiled with the
sequencer included in synApps (2.2.1). If I set SNCSEQ at the bottom of RELEASE,
this error message is printed and compilation stops:

make[2]: Entering directory
'/home/lcavalli/Documents/Progetti/[...]/StateMachineExec/configure/O.linux-
x86_64'
perl /opt/epics/base/bin/linux-x86_64/convertRelease.pl checkRelease

Definition of SNCSEQ conflicts with SUPPORT support.
In this application a RELEASE file defines
        SNCSEQ = /opt/epics/modules/seq-2.2.4
but SUPPORT at /opt/epics/support defines
        SNCSEQ = /opt/epics/support/seq-2-2-1
Definition of SNCSEQ conflicts with SSCAN support.
In this application a RELEASE file defines
        SNCSEQ = /opt/epics/modules/seq-2.2.4
but SSCAN at /opt/epics/support/sscan-2-10-1 defines
        SNCSEQ = /opt/epics/support/seq-2-2-1
Definition of SNCSEQ conflicts with CALC support.
In this application a RELEASE file defines
        SNCSEQ = /opt/epics/modules/seq-2.2.4
but CALC at /opt/epics/support/calc-3-4-2-1 defines
        SNCSEQ = /opt/epics/support/seq-2-2-1
Definition of SNCSEQ conflicts with ASYN support.
In this application a RELEASE file defines
        SNCSEQ = /opt/epics/modules/seq-2.2.4
but ASYN at /opt/epics/support/asyn-4-26 defines
        SNCSEQ = /opt/epics/support/seq-2-2-1
Definition of SNCSEQ conflicts with XXX support.
In this application a RELEASE file defines
        SNCSEQ = /opt/epics/modules/seq-2.2.4
but XXX at /opt/epics/support/xxx-5-8-3 defines
        SNCSEQ = /opt/epics/support/seq-2-2-1

/opt/epics/base/configure/RULES_BUILD:171: recipe for target 'checkRelease'
failed
make[2]: *** [checkRelease] Error 1
make[2]: Leaving directory
'/home/lcavalli/Documents/Progetti/[...]/StateMachineExec/configure/O.linux-
x86_64'
/opt/epics/base/configure/RULES_ARCHS:64: recipe for target 'install.linux-
x86_64' failed
make[1]: *** [install.linux-x86_64] Error 2
make[1]: Leaving directory
'/home/lcavalli/Documents/Progetti/[...]/StateMachineExec/configure'
/opt/epics/base/configure/RULES_DIRS:87: recipe for target 'configure.install'
failed
make: *** [configure.install] Error 2
[lcavalli@cavalli StateMachineExec]$

Setting SNCSEQ in my src/Makefile works, but is it the correct approach?
Is it possible to make synApps (and its sequencer installation used internally)
and an external sequencer installation coexist?


Thanks for your help,

Luca


________________________________

<< Le informazioni contenute in questo messaggio di posta elettronica e relativi allegati sono riservate e confidenziali e ne è vietata la diffusione in qualunque modo eseguita. Qualora Lei non fosse la persona a cui il presente messaggio è destinato, La invitiamo ad eliminarlo e a darcene gentile comunicazione. Quanto precede ai fini del rispetto delle Legge 675/96 e del Decreto Legislativo 30/06/2003 n.196, sulla tutela dei dati personali >>

<< This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your co-operation. Please contact our IT Helpdesk on +3902380481 or email [email protected] if you need assistance >>



Replies:
Re: synApps and external sequencer installation Benjamin Franksen
RE: synApps and external sequencer installation Mark Rivers

Navigate by Date:
Prev: Announcing the Transient Recorder Framework ambroz . bizjak
Next: Re: synApps and external sequencer installation Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Announcing the Transient Recorder Framework ambroz . bizjak
Next: Re: synApps and external sequencer installation Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·