Hi Peter,
The errors appeared to be file permissions. Do the permissions look OK in the module directory where you are building? Is this the same location you have built previously with 3.15.1,
or a copy in a new location?
My test yesterday was on a Linux file server in a tree shared with other builds (linux-x86_64, etc.). I did the Linux builds first, so the O.Common directories were already built,
etc.
Today I did a clean install on my Windows C: drive of base-3.15.2 and asyn-4-26 and both built fine with the windows-x64 architecture.
These are the first few lines of the build of asyn:
C:\EPICS\Support-3-15\asyn-R4-26>make
make -C ./configure install
make[1]: Entering directory 'C:/EPICS/Support-3-15/asyn-R4-26/configure'
perl -CSD C:/EPICS/base-3.15.2/bin/windows-x64/makeMakefile.pl O.windows-x64 ../..
perl -CSD -MExtUtils::Command -e mkpath O.Common
make -C O.windows-x64 -f ../Makefile TOP=../.. \
T_A=windows-x64 install
make[2]: Entering directory 'C:/EPICS/Support-3-15/asyn-R4-26/configure/O.windows-x64'
perl -CSD C:/EPICS/base-3.15.2/bin/windows-x64/convertRelease.pl checkRelease
make[2]: Leaving directory 'C:/EPICS/Support-3-15/asyn-R4-26/configure/O.windows-x64'
make[1]: Leaving directory 'C:/EPICS/Support-3-15/asyn-R4-26/configure'
make -C ./makeSupport install
make[1]: Entering directory 'C:/EPICS/Support-3-15/asyn-R4-26/makeSupport'
perl -CSD C:/EPICS/base-3.15.2/bin/windows-x64/makeMakefile.pl O.windows-x64 ../..
perl -CSD -MExtUtils::Command -e mkpath O.Common
make -C O.windows-x64 -f ../Makefile TOP=../.. \
T_A=windows-x64 install
make[2]: Entering directory 'C:/EPICS/Support-3-15/asyn-R4-26/makeSupport/O.windows-x64'
"Installing created executable ../../bin/windows-x64/makeSupport.pl"
mkdir ../../bin
mkdir ../../bin/windows-x64
"Installing ../../templates/top/Makefile"
mkdir ../../templates
mkdir ../../templates/top
"Installing ../../templates/top/configure/CONFIG"
mkdir ../../templates/top/configure
"Installing ../../templates/top/configure/CONFIG_APP"
Mark
From: Heesterman, Peter J [mailto:[email protected]]
Sent: Tuesday, September 15, 2015 12:13 PM
To: Mark Rivers; EPICS Tech-Talk ([email protected])
Subject: RE: Unable to build support modules on Windows, with base 3.15.2
Hi Mark,
Thank you for having a look at this.
I’m still at a loss, it’s interesting that it works for you.
I’m using ActivePerl v5.16.3.
As it happens, I have both the 32 and 64-bit versions installed (same version).
This is unnecessary for the EPICS build - I can choose either by altering the PATH to the Perl tools.
I note you are using the 64-bit version – I set my usage to match yours, but that didn’t make a difference.
Cheers,
Peter.
From: Mark Rivers [mailto:[email protected]]
Sent: 14 September 2015 19:54
To: Heesterman, Peter J; EPICS Tech-Talk ([email protected])
Subject: RE: Unable to build support modules on Windows, with base 3.15.2
Hi Peter,
I just tested building base 3.15.2 on windows-x64, and then building the support modules (seq, asyn, autosave, etc.). It worked fine for me, I did not get the errors you did.
What version of perl are you using?
I am using ActivePerl 5.14.2.
*********************************
C:\EPICS>perl --version
This is perl 5, version 14, subversion 2 (v5.14.2) built for MSWin32-x64-multi-thread
(with 1 registered patch, see perl -V for more detail)
Copyright 1987-2011, Larry Wall
Binary build 1402 [295342] provided by ActiveState
http://www.ActiveState.com
Built Oct 7 2011 15:19:36
*********************************
Mark
Hi,
I just downloaded EPICS base 3.15.2, superseding previous 3.15.1.
I am experiencing a problem building any of the support modules, while using the make file build.
(There is no problem building base 3.15.2 itself, however.)
I’ve built all the same code successfully on Linux, while using 3.15.2.
See attached, these are examples when trying to build Asyn or Seq, but this applies to all modules I’ve looked at, and to different build configurations I’ve attempted.
It all built OK when using 3.15.1.
What could I be missing?
Thanks,
Peter.