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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: IOC make failing on a new linux build, Perl checkrelease |
From: | Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov> |
To: | tech-talk at aps.anl.gov |
Date: | Tue, 25 Oct 2022 11:05:41 -0400 |
Hi Adam, On 10/25/22 2:12 AM, Manoussakis,
Adamandios via Tech-talk wrote:
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).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. 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. |