I have a question about the behavior of the fullPathName.pl script in
EPICS version R3.14.12.3.J0 compared
to previous EPICS versions.
I noticed in building EPICS and applications with version R3.14.12.3.J0
that the shared library paths
get resolved to absolute paths instead of paths that have previously
contained symbolic links. I tracked this
new behavior down to a single line of code in the perl module
"/epics/R3.14.12.3.J0/lib/perl/EPICS/Path.pm".
The line of code added is listed below.
"$abs = abs_path($abs) if -e $abs;"
We maintain the same directory paths using symbolic links between our
development and operational file servers.
If the paths to shared libraries are different the code running on the
operational servers fails to find the shared libraries.
Really wish there was a flag to select between the old and new behavior
rather than editing "Path.pm".
What's the best way to resolve this issue?
Thanks in advance,
Scott Higgins
Jefferson Lab
- Replies:
- Re: Change in behavior of the fullPathName.pl Andrew Johnson
- Navigate by Date:
- Prev:
Thread Handle Leak: EPICS Base on Windows giles.knap
- Next:
areaDetector driver for Princeton Instruments PICAM cameras? Mark Rivers
- 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: Thread Handle Leak: EPICS Base on Windows Andrew Johnson
- Next:
Re: Change in behavior of the fullPathName.pl Andrew Johnson
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·