Hi,
I've been attempting to build a set of support modules by leaving the RELEASE files unchanged and only specifying what we need in RELEASE.local files.
So up until now I have only ever built asyn with a single dependency on base, and so my asyn RELEASE.local contains:
EPICS_BASE=/home/controls/common/base/main
However this fails because the standard asyn RELEASE file sets:
# SEQ is required for testIPServer
SNCSEQ=$(SUPPORT)/seq-2-2-5
And so the asyn build fails because that particular test expects SNCSEQ.
To fix that in my asyn RELEASE.local I can do:
SNCSEQ=
EPICS_BASE=/home/controls/common/base/main
But that causes problems on downstream builds that also use SNCSEQ due to CHECK_RELEASE.
I can fix that by doing this instead:
undefine SNCSEQ
EPICS_BASE=/home/controls/common/base/main
Although this causes errors like these when building asyn:
make[2]: Entering directory '/home/controls/common/asyn/main/iocBoot/ioctest'
perl -CSD /home/controls/common/base/main/bin/linux-x86_64/convertRelease.pl -t /home/controls/common/asyn/main envPaths
Use of uninitialized value $iocpath in substitution (s///) at /home/controls/common/base/main/bin/linux-x86_64/convertRelease.pl line 220.
Use of uninitialized value $path in -d at /home/controls/common/base/main/bin/linux-x86_64/convertRelease.pl line 221.
Do you know what's causing these errors? I suppose the script just isn't silently dealing with the 'undefine' syntax? However, it seems to complete fine, as the envPaths file is correct:
epicsEnvSet("IOC","ioctest")
epicsEnvSet("TOP","/home/controls/common/asyn/main")
epicsEnvSet("EPICS_BASE","/home/controls/common/base/main")
Cheers,
Matt
STS Integrated Control System Lead Engineer
Spallation Neutron Source
Oak Ridge National Lab
- Replies:
- Re: undefine variable in RELEASE.local Johnson, Andrew N. via Tech-talk
- Navigate by Date:
- Prev:
RE: Measurement Computing USB-1608G_2AO support Mark L Rivers via Tech-talk
- Next:
Control System Engineer position at ALS in LBNL Miroslaw Dach 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
<2021>
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: [EXTERNAL] Data Browser (phoebus) auto data fetching from an Archiver Appliance BENEDETTI Florian via Tech-talk
- Next:
Re: undefine variable in RELEASE.local 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
<2021>
2022
2023
2024
|