Experimental Physics and
Industrial Control System

Jerzy Tarasiuk via Core-talk <core-talk at aps.anl.gov> · Tue, 15 Jun 2021 21:22:42 -0000

Seems the "fix line" using $(TOP) worked when 'make' was called in
<base>configure/, but fails when entire EPICS base is to be compiled.

I compiled EPICS base 7.0.5 twice - with the "fix", and without it,
and examined: sizes of files in the installation directory - the only
different file size was "configure/CONFIG_SITE.local", so seems the
"fix" hasn't affect the outcome. Also, I examined strace logs and saw:
* exactly one succesful 'execve' invoking the "convertRelease.pl"
  via 'perl' when compiling without the "fix";
* 155 * 'execve' invoking the "convertRelease.pl" without an error,
  4 via 'perl' (all unfinished), 151 * directly (101 unfinished)
  when compiling with the "fix";
* the same number of different succesful open-s of "RELEASE*" files
  (however, there are differences in list of names used by these
  open-s); about 5% more succesful open-s with the "fix" (257/270);
* without "fix" no succesful open() of "RELEASE*" file from the
  process which succesfully did the only 'execve'; seems the process
  loaded the script as a library function and it was later used.

Conclusion: nothing indicates that the bug affects the outcome;
it seems to be quite probable that it is meaningless, as many files
are processed in both cases, however this assumption is not proven.

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1932033

Title:
  base EPICS compilation misses convertRelease.pl

Status in EPICS Base:
  Triaged

Bug description:
  Seems the convertRelease.pl is to be used by installation scripts, but
  it is not found.

  The problem occurs when the installation directory is different from the source directory
  (I tried it by adding a file configure/CONFIG_SITE.local containing INSTALL_LOCATION=path)
  and the only mark seen are messages on standard error like: Can't open perl script ".."

  The reason for the message is that the EPICS installation scripts cannot find some script
  needed and likely its job is not done, resulting in invalid EPICS installation (it doesn't
  stop the installation and can be easily overlooked, unless the standard error is logged).

  The message dosn't tell the script name - seems a variable which is to specify the name
  contains an empty string when it is used and a file of empty name is looked for in the
  parent directory, therefore the name ".." (and later "../..") is in the message.

  I found 2 workarounds for the problem:
  1. Before 'make' copy "src/tools" from source to installation directory (the copy has to be
     in "<installation-dir>/src/tools") - the installation looks for the "convertRelease.pl" 
     there instead in the "<source-dir>/src/tools".
  2. In the configure/CONFIG_SITE.local add a line "CONVERTRELEASE=<convertRelease.pl-path>";
     I found it also needed setting execute permission for the "convertRelease.pl".
  Unfortunately, I don't know the Perl language and I am unable to make a real fix.

  All this was tried on Linux Ubuntu 18.04 having installed GNU Make 4.1, 
  binutils, Perl v5.26.1, perl-modules, GCC/G++ 7.3.0, libreadline-dev.
  Also, I tried it on NI Linux Real-Time 6.0 with the same problem
  (I didn't try the workarounds on the NI Linux yet).

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1932033/+subscriptions

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System