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: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set
From: "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov>
To: Dirk Zimoch <dirk.zimoch at psi.ch>
Cc: EPICS core-talk <core-talk at aps.anl.gov>
Date: Mon, 20 Apr 2020 15:16:50 +0000
On Apr 20, 2020, at 2:18 AM, Zimoch Dirk (PSI) <dirk.zimoch at psi.ch> wrote:

I will commit this if you confirm it fixes the problem.
 
I can confirm that with works with and without INSTALL_LOCATION.

Thanks, the fix is now included on the 3.15 branch.


I think we should add using INSTALL_LOCATION to the automated tests so that we can detect this type of problem early.

We just need someone to write the appropriate test in a platform-independent way. I recommend doing it as a Perl script, naming it .plt (see Snippets.plt file for a model).


BTW: Why are the perl scripts installed to bin/$EPICS_HOST_ARCH anyway, even though they are platform independent?
Installing both, the perl programs and the perl modules to the same directory ($EPICS_BASE/bin/perl ? $EPICS_BASE/perl ?)  would make searching for them easier.  Of course that requires to extend PATH a bit.

Unix platforms have always used a common directory for executables, the language that programs are written in should be an implementation detail. Run ‘file /usr/bin/*’ on your favorite Linux distribution and you might be surprised the language by some programs are written in. We started out naming our Perl scripts .pl but that isn’t essential and we might decide to change them.

Also, we now have one Python program shipped with 7.0, would you want us to have to add more build rules to install into another bin subdirectory? That would also require to extend your PATH again just to run that one program (most Base installations won’t need it so we haven’t added Python as a prerequisite).

- Andrew

-- 
Complexity comes for free, simplicity you have to work for.

References:
Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Zimoch Dirk (PSI) via Core-talk
AW: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Zimoch Dirk (PSI) via Core-talk
AW: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Zimoch Dirk (PSI) via Core-talk
AW: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Zimoch Dirk (PSI) via Core-talk
AW: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Zimoch Dirk (PSI) via Core-talk
Re: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Johnson, Andrew N. via Core-talk
AW: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Zimoch Dirk (PSI) via Core-talk
Navigate by Date:
Prev: AW: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Zimoch Dirk (PSI) via Core-talk
Next: tapfiles double-colon rule 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: AW: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set Zimoch Dirk (PSI) via Core-talk
Next: Re: Problem compiling EPICS 7 commit 85d1982 when INSTALL_LOCATION is set 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 
ANJ, 20 Apr 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·