[Bug 1932033] Re: base EPICS compilation misses convertRelease.pl

[mdavidsaver via Core-talk <core-talk at aps.anl.gov>]

Testing INSTALL_LOCATION with the current 7.0 branch HEAD appears to
succeed, though I do see the message you mention.  So I guess this is a
nuisance message.

$ git clone --depth 1 https://github.com/epics-base/epics-base.git
$ make -C epics-base INSTALL_LOCATION=$PWD/inst -sj8
Can't open perl script ".": Is a directory
Can't open perl script "..": Is a directory
Can't open perl script "../..": Is a directory
Can't open perl script "../..": Is a directory
Can't open perl script "..": Is a directory
Can't open perl script "../..": Is a directory
Can't open perl script "../../..": Is a directory
...
$ ls inst/bin/linux-x86_64/
acctst               caput               dbdToRecordtypeH.pl  iocLogServer       munch.pl
...


** Changed in: epics-base
       Status: New => Triaged

** Changed in: epics-base
   Importance: Undecided => Low

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