Thanks Han/Andrew for the insight, will just plan on using absolute paths then.
Adam
From: Tech-talk <tech-talk-bounces at aps.anl.gov>
On Behalf Of Andrew Johnson via Tech-talk
Sent: Tuesday, October 25, 2022 8:06 AM
To: tech-talk at aps.anl.gov
Subject: Re: IOC make failing on a new linux build, Perl checkrelease
Hi Adam,
On 10/25/22 2:12 AM, Manoussakis, Adamandios via Tech-talk wrote:
Took one of our IOCs and tried to run make on a new build, getting EPICS_BASE needs to be defined in release file but it is. This ioc will build on all of other linux machines but for some reason not this one.
Checked the release file and it’s defined, double checked to make sure HOME was echoing correctly in command prompt. Made sure that the path CDs into the directory as well.
EPICS_BASE=${HOME}/epics/base
If I write out the full path seems to compile fine but for some reason the env variable home is not making it into the release file. Feel like I am missing something obvious when we set up our other machines vs this new build.
The RELEASE file is not just read by GNUmake, we have our own parser and that explicitly does
not support the use of environment variables in RELEASE files, please use an absolute path. This was to ensure that settings that could have been added to the environment by hand can't affect your build (which you might not discover until months later
when it doesn't work).
Disabling the checkRelease tests like Han suggests removes the seat-belt protection which the EPICS build system provides, use that at your own risk.
- Andrew
--
Complexity comes for free, Simplicity you have to work for.
