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: 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: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Tue, 20 Apr 2021 20:43:48 +0000

Hello everyone,

 

I am trying to build the latest asyn (commit a2da087) against base-R7.0.4.1, but encountered the same error “No rule to make target 'ipSNCServer.o'” as reported on tech-talk:

https://epics.anl.gov/tech-talk/2007/msg01045.php

 

However, I do have SNCSEQ defined in asyn/configure/RELEASE:

SNCSEQ=/usr/lib/epics

EPICS_BASE=/usr/lib/epics

 

As you see, both EPICS_BASE and SNCSEQ point to the same path in my RELEASE. This is the historical tradition at NSLS-2: we install all EPICS stuff (base, support modules) in a flat directory “/usr/lib/epics”.

$ ls /usr/lib/epics/

bin  cfg  configure  db  dbd  include  lib  startup  templates

 

This has been working well for base-3.14.12, meaning I can build the latest asyn (commit a2da087) against base-3.14.12 with SNCSEQ=/usr/lib/epics. Now, this kind of directory structure seems to not work for base-R7.0.4.1. I do see some warnings when building asyn against base-R7.0.4.1:

/usr/lib/epics/configure/RULES_BUILD:575: Warning: Base configure/RULES_BUILD file included more than once. Does configure/RELEASE have multiple pointers to /usr/lib/epics?

 

If I make a change like this: SNCSEQ=/home/yhu/epics/seq-2-2-6 where I have built “seq” in my home directory, I can build the latest asyn (commit a2da087) against base-R7.0.4.1 successfully.

 

So, the problem seems related to “Does configure/RELEASE have multiple pointers to …”. A simple search on Google/Tech-Talk does not give me any hints to fix the problem. Any suggestions are welcomed!

 

Thanks,

Yong

 


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

Navigate by Date:
Prev: Re: How to use asyGenericPointerSyncIO interface? Mark Rivers via Tech-talk
Next: Re: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Hu, Yong 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: How to use asyGenericPointerSyncIO interface? Mark Rivers via Tech-talk
Next: Re: asyn: No rule to make target 'ipSNCServer.o'; Does configure/RELEASE have multiple pointers to ... Hu, Yong 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, 20 Apr 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·