Re: EPICS base-3.14.12.5 installation error

[Alex George <alexjgeorge636@gmail.com>]

Hi Freddie,

After running the command, it produced the same error as when running the original “perl ../../../bin/windows-x64/registerRecordDeviceDriver.pl” of No such file or directory opening file at ../../../bin/windows-x64/registerRecordDeviceDriver.pl line 28

My next step is to try a past version of ActiveState Perl

Alex

On Wed, Jun 24, 2015 at 12:34 PM, <freddie.akeroyd@stfc.ac.uk> wrote:

Hi Alex,

 

If I understand correctly, you were able to type “perl ../../../bin/windows-x64/registerRecordDeviceDriver.pl” in the softIoc\O.windows-x64 directory and it fail with an error at line 28 in that perl script, but if you type “make” in the softIoc directory it fails with “can’t open perl script  ../../../bin/windows-x64/registerRecordDeviceDriver.pl” ? This would suggest that there is something about the way that make is invoking perl that is causing a problem as perl is then unable to start executing registerRecordDeviceDriver.pl even though you have separately shown that it is possible to do this outside of make. Can you try running the full line that make is using just to confirm this – in softIoc\O.windows-x64   type

    perl ../../../bin/windows-x64/registerRecordDeviceDriver.pl ../O.Common/softIoc.dbd softIoc_registerRecordDeviceDriver C:/epics/base-3.14.12.5 > softIoc.tmp

 

If that produces no errors, I start to wonder if make is somehow invoking the command from the wrong current directory?

 

Regards,

 

Freddie

 

 

From: Mark Rivers [mailto:rivers@cars.uchicago.edu]
Sent: 24 June 2015 15:52
To: 'Alex George'; Akeroyd, Freddie (STFC,RAL,ISIS)
Cc: EPICS tech-talk
Subject: RE: EPICS base-3.14.12.5 installation error

 

I had a strange problem with building Windows on 3.14.12.4.  In my case I was building on a remote Linux file server.  It was working fine, and then stopped working.  I don’t remember the error, but it may have been similar to what you are seeing.  I was able to solve it by simply reinstalling EPICS base.

 

Have you tried that on your problematic machine?  Completely remove the EPICS base installation and install it again.

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Alex George
Sent: Wednesday, June 24, 2015 9:23 AM
To: freddie.akeroyd@stfc.ac.uk
Cc: EPICS tech-talk
Subject: Re: EPICS base-3.14.12.5 installation error

 

Hi Freddie and Andrew,

 

I apologize for the delayed response.

 

Freddie:

I've actually tried that command with the same error occurring at line 28: open(INP,"$file") or die "$! opening file";

 

I've compiled successfully on another machine in the lab with the exact set up without any errors; more so I've attempted to hard code the file path in the line 28 $file variable to no success (hard coding worked on the successful machine).

 

Andrew:

- I've tried the latest versions of Strawberry Perl and ActiveState, both x64, both running into the same error.

- The permissions on both of the files are the same but as before only the one runs

 

 

Clutching straws,

Alex

 

 

On Tue, Jun 23, 2015 at 12:04 PM, <freddie.akeroyd@stfc.ac.uk> wrote:

Hi Andrew,

We are using Strawberry Perl 5.12.3.0

    C:\Instrument\Apps\EPICS\base\3-14-12-4\src\softIoc>perl -v

    This is perl 5, version 12, subversion 3 (v5.12.3) built for MSWin32-x64-multi-thread

The permissions on  makeIncludeDbd.pl  should be the same as those on  registerRecordDeviceDriver.pl  and his perl is able to run makeIncludeDbd.pl - maybe worth Alex just comparing them to be sure.
The filename "registerRecordDeviceDriver.pl" is longer than "makeIncludeDbd.pl " though, maybe we have hit a path length limit is that version of ActiveState perl?

When I start running "process monitor", you can tell I'm clutching straws too :-)

Freddie

-----Original Message-----
From: Andrew Johnson [mailto:anj@aps.anl.gov]
Sent: 23 June 2015 16:43
To: Akeroyd, Freddie (STFC,RAL,ISIS); alexjgeorge636@gmail.com
Cc: tech-talk@aps.anl.gov
Subject: Re: EPICS base-3.14.12.5 installation error

Hi Freddie,

Whose version of Perl are you using? I use Strawberry Perl here, although our Jenkins build server does have the ActiveState version installed. I'm wondering if there might be something different in the way that the ActiveState Perl that Alex is using has been built, such that it doesn't understand file permissions in quite the same way.

Clutching at straws here...

- Andrew


On 06/23/2015 10:35 AM, freddie.akeroyd@stfc.ac.uk wrote:
> Hi,
>
> I have similar permissions to Alex on my installation and epics builds OK - my windows domain account is explicitly in the BUILTIN\Administrators group, but will also be in BUILTIN\Users (which include "domain users"). I'm guessing Alex is too a local administrator on his computer?
>
> Alex, what happens if you try and run these things outside of make:
>
>     cd C:\epics\base-3.14.12.5\src\softIoc\O.windows-x64
>
>    type ..\..\..\bin\windows-x64\registerRecordDeviceDriver.pl
>
>    perl ..\..\..\bin\windows-x64\registerRecordDeviceDriver.pl
>
>    perl ../../../bin/windows-x64/registerRecordDeviceDriver.pl
>
> For both perl commands you should get something like "No such file or directory opening file at ../../../bin/windows-x64-debug/registerRecordDeviceDriver.pl line 28"
>
> It is rather strange that your build is able to execute:
>
>     perl ../../../bin/windows-x64/makeIncludeDbd.pl base.dbd
> dlload.dbd system.dbd softIocInclude.dbd
>
> but not
>
>     perl ../../../bin/windows-x64/registerRecordDeviceDriver.pl
> ../O.Common/softIoc.dbd softIoc_registerRecordDeviceDriver
> C:/epics/base-3.14.12.5 > softIoc.tmp
>
> It is possible to open files on windows and deny other processes read access even if the file permissions would otherwise grant such access. This would cause a "sharing violation", but these can get reported as "file not found" by some tools. Clutching at straws here, is there any possibility of another process/tool being involved and causing problems?
>
> There are useful windows diagnostic tools at https://technet.microsoft.com/en-us/sysinternals/default - i've used "handle" (to list all open files) and "process monitor" (to look at file accesses) before to diagnose problems. If you install process monitor, you can filter on something like "command line   contains   perl" and then do a make in the softioc directory. This should give some idea of what file access the perl program is trying to do, and how successful it is at this.
>
> Regards,
>
> Freddie
>
>
> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov
> [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Andrew Johnson
> Sent: 22 June 2015 20:24
> To: Alex George
> Cc: EPICS tech-talk
> Subject: Re: EPICS base-3.14.12.5 installation error
>
> On 06/22/2015 12:28 PM, Alex George wrote:
>>   cd C:/epics/base-3.14.12.5/src/softIoc
>>   icacls ../../bin/windows-x64/registerRecordDeviceDriver.pl
>>
>> C:\epics\base-3.14.12.5\src\softIoc>icacls
>> ../../bin/windows-x64/registerRecordDeviceDriver.pl
>> ../../bin/windows-x64/registerRecordDeviceDriver.pl BUILTIN\Administrators:(I)(F)
>>                                                     NT AUTHORITY\SYSTEM:(I)(F)
>>                                                     BUILTIN\Users:(I)(RX)
>>                                                     NT
>> AUTHORITY\Authenticated Users:(I)(M)
>>
>> Successfully processed 1 files; Failed processing
>
> None of the names listed there are obviously your user account, so I'm becoming more convinced that this problem is due to file permissions.
> When I run the same command for my build the result looks like this:
>
>> D:\epics\mirror-3.14\src\softIoc>icacls
>> ..\..\bin\windows-x64\registerRecordDeviceDriver.pl
>> ..\..\bin\windows-x64\registerRecordDeviceDriver.pl ANL\anj:(I)(F)
>>                                                     ANL\Domain Users:(I)(RX)
>>                                                     Everyone:(I)(RX)
>>
>> Successfully processed 1 files; Failed processing 0 files
>
> I'm logged in as ANL\anj and I have full permissions (F) over that file.
>
> Can any Windows experts out there comment on this? I don't really understand the intricacies of the Windows permissions system or how ActiveState Perl may be unable to execute a script which it itself installed earlier in the build process.
>
> Alex,
>
> If you can either take ownership or give yourself full permissions over the C:/epics directory tree (and all its subdirectories and files) that will probably fix the problem. You would do that by bringing up Windows Explorer and the Properties dialog for the directory, then go to the Security tab and click the Edit button.
>
> - Andrew
>
> --
> Light thinks it travels faster than anything but it is wrong.
> No matter how fast light travels, it finds the darkness has always got there first, and is waiting for it.
>     -- Terry Pratchett, Reaper Man
>

--
Light thinks it travels faster than anything but it is wrong.
No matter how fast light travels, it finds the darkness has always got there first, and is waiting for it.
    -- Terry Pratchett, Reaper Man

 

--

Alex George

Bioengineering Student

A. James Clark School of Engineering

University of Maryland, College Park

Phone: (301) 741-0847

--

Alex George

Bioengineering Student

A. James Clark School of Engineering

University of Maryland, College Park

Phone: (301) 741-0847