Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Thu, 2 May 2013 06:11:06 -0500 (CDT)

Hi Scott,

Please read this tech-talk thread to see why the line you want removed was added:
    http://www.aps.anl.gov/epics/tech-talk/2012/msg01804.php

Could you use the INSTALL_LOCATION Makefile variable to set the canonical installation path in your CONFIG_SITE file? If the build machine can write via either path then that might solve the problem. If not there may be other ways to get around this if you can explain a little more about your setup and process.

- Andrew

-- 
Sent from my iPad

On May 1, 2013, at 10:29 PM, Scott Higgins <[email protected]> wrote:

> 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
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System