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  <20212022  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  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ...
From: "Hu, Yong via Tech-talk" <tech-talk at aps.anl.gov>
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: EPICS Tech-Talk <tech-talk at aps.anl.gov>
Date: Wed, 21 Apr 2021 14:56:33 +0000

Thank you, Mark! It works with empty values. I do not see asyn is trying to build “testIPServerApp” any more.

SUPPORT=

IPAC=

SNCSEQ=

 

 

On 4/21/21, 10:35 AM, "Mark Rivers" <rivers at cars.uchicago.edu> wrote:

 

Hi Yong,

 

  • So, my questions: do we really need the following 3 lines in asyn/configure/RELEASE?
  • SUPPORT=/corvette/home/epics/devel
  • IPAC=$(SUPPORT)/ipac-2-15
  • SNCSEQ=$(SUPPORT)/seq-2-2-5

 

Actually asyn configure/RELEASE has explanatory comments before each of those lines:

 

#  IPAC is only necessary if support for Greensprings IP488 is required

#  IPAC release V2-7 or later is required.

IPAC=$(SUPPORT)/ipac-2-15

 

# SEQ is required for testIPServer

SNCSEQ=$(SUPPORT)/seq-2-2-5

 

## For sCalcout support in asynOctet - applications include asynCalc.dbd

#CALC=$(SUPPORT)/calc-3-7-3

 

# If CALC was built with SSCAN support then SSCAN must be defined for testEpicsApp

#SSCAN=$(SUPPORT)/sscan-2-11-3

 

#  EPICS_BASE 3.14.6 or later is required

EPICS_BASE=/corvette/usr/local/epics-devel/base-7.0.4

 

I believe you can achieve what you want without editing RELEASE by putting these lines in RELEASE.local

 

SUPPORT=

IPAC=

SNCSEQ=

 

I think that should work because RELEASE.local is read after RELEASE, and so you will replace those 3 definitions.  I have not tested it, so please try it.

 

Mark

 


References:
asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Hu, Yong via Tech-talk
Re: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Hu, Yong via Tech-talk
RE: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Mark Rivers via Tech-talk
Re: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Hu, Yong via Tech-talk
RE: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Mark Rivers via Tech-talk

Navigate by Date:
Prev: RPM packages for EPICS Hu, Yong via Tech-talk
Next: Re: RPM packages for EPICS Johnson, Andrew N. 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  <20212022  2023  2024 
Navigate by Thread:
Prev: RE: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Mark Rivers via Tech-talk
Next: Re: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Johnson, Andrew N. 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  <20212022  2023  2024 
ANJ, 21 Apr 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·