EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: Base 7 modules/RELEASE*.local files
From: "Johnson, Andrew N. via Core-talk" <[email protected]>
To: "[email protected]" <[email protected]>
Date: Mon, 4 Nov 2019 17:41:41 +0000
Hi Mark,

On 11/2/19 8:10 AM, Mark Rivers via Core-talk wrote:

I just updated my base-7.0.3 to base-7.0.3.1 by doing the following:

 

git pull

git checkout R7.0.3.1

git submodule update

Renamed the directory from base-7.0.3 to base-7.0.3.1.

make realclean realuninstall

 

This fails because the modules/RELEASE*.local files still refer to the old directory base-7.0.3.  I had to delete those files manually.

 

I find this frustrating.  Is there a reason that those files cannot be removed with realclean or realuninstall?


They do get removed by 'make realclean', but you must run that command before you rename the directory. If you don't, you get this kind of error:
configure/CONFIG:17: /opt/epics/base-7.0.3/configure/CONFIG: No such file or directory
configure/RULES_TOP:2: /opt/epics/base-7.0.3/configure/RULES_TOP: No such file or directory
make[1]: *** No rule to make target `/opt/epics/base-7.0.3/configure/RULES_TOP'.  Stop.
make: *** [pvData.realclean] Error 2

GNUmake is trying to run a 'make realclean' inside the first submodule, which it has to do before doing removing the RELEASE.<host>.local file itself since all submodule builds need the value of $(EPICS_BASE) which gets set in that file. The submodule 'make' fails because the $(EPICS_BASE) value it gets from the old RELEASE.<host>.local file doesn't point to a valid installation of Base and it can't find a configure/CONFIG file there.

The only way this can work with the current build system is to clean out the old files before you rename the directory. We had a similar conversation about this issue about a year ago, and I gave you the same answer back then.

- Andrew
-- 
Complexity comes for free, Simplicity you have to work for.
References:
Base 7 modules/RELEASE*.local files Mark Rivers via Core-talk
Navigate by Date:
Prev: Re: Base 7 modules/RELEASE*.local files Mark Rivers via Core-talk
Next: Re: Architecture dependent dbd files Johnson, Andrew N. via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Base 7 modules/RELEASE*.local files Mark Rivers via Core-talk
Next: Architecture dependent dbd files Mark Rivers via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024 
ANJ, 04 Nov 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·