Strange, it is putting the current path in front of the path to the perl script in base.
Have you modified any of the files in base/configure/os?
Send the contents of asyn/configure/RELEASE and the output of the "set" command.
Mark
-----Original Message-----
From: Heesterman, Peter J [mailto:[email protected]]
Sent: Wednesday, September 16, 2015 12:21 PM
To: Mark Rivers; 'Jani Hakala'
Cc: EPICS Tech-Talk ([email protected])
Subject: RE: Unable to build support modules on Windows, with base 3.15.2
Hi Mark,
That's a combination that I've tried, with the result attached.
Cheers,
Peter.
-----Original Message-----
From: Mark Rivers [mailto:[email protected]]
Sent: 16 September 2015 17:45
To: Heesterman, Peter J; 'Jani Hakala'
Cc: EPICS Tech-Talk ([email protected])
Subject: RE: Unable to build support modules on Windows, with base 3.15.2
I define EPICS_BASE like this:
EPICS_BASE=H:/epics/base-3.14.12.5
I use a drive letter and forward slashes.
Mark
-----Original Message-----
From: Heesterman, Peter J [mailto:[email protected]]
Sent: Wednesday, September 16, 2015 11:36 AM
To: Mark Rivers; 'Jani Hakala'
Cc: EPICS Tech-Talk ([email protected])
Subject: RE: Unable to build support modules on Windows, with base 3.15.2
Hi Mark, Jani,
Thank you for your responses.
FYI my build directory structure has:
D:\EPICS
Base
Support
Seq
Asyn
...
I have configured RELEASE in these modules as:
EPICS_BASE=\EPICS\base
I have also experimented with (explicitly) D:\EPICS\base - I prefer to avoid doing so, as the C: drive could be used.
I have also experimented with various combinations of the slash character.
None of this made any difference.
You are correct, perl -CSD \EPICS\base/bin/win32-x86-static/makeMakefile.pl ... is the correct and expected output.
I have no idea why D:/EPICS/support/asyn/configure/ has been prepended - it doesn't make any sense.
Also, why are the directories '.' and '..' being compiled as perl scripts, resulting in 'permission denied'?
BTW, I have not set any unusual permissions - (Everyone - Read only), (Administrators, system and myself, full control).
Cheers,
Peter.
-----Original Message-----
From: Mark Rivers [mailto:[email protected]]
Sent: 15 September 2015 21:43
To: 'Jani Hakala'; Heesterman, Peter J
Cc: EPICS Tech-Talk ([email protected])
Subject: RE: Unable to build support modules on Windows, with base 3.15.2
Hi Peter,
I agree with Jani.
This is what you are getting:
make[1]: Entering directory `D:/EPICS/support/asyn/configure'
perl -CSD D:/EPICS/support/asyn/configure/\EPICS\base/bin/win32-x86-static/makeMakefile.pl O.win32-x86-static ../..
This is what I get:
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 ../..
For some reason for you it is putting the current path in front of the path to the makeMakefile.pl script in EPICS base.
How have you defined EPICS_BASE in asyn/configure/RELEASE?
Mark
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Jani Hakala
Sent: Tuesday, September 15, 2015 3:03 PM
To: Heesterman, Peter J
Cc: EPICS Tech-Talk ([email protected])
Subject: Re: Unable to build support modules on Windows, with base 3.15.2
"Heesterman, Peter J" <[email protected]> writes:
> 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?
>
This doesn't look so good
perl -CSD D:/EPICS/support/asyn/configure/\EPICS\base/bin/win32-x86-static/makeMakefile.pl O.win32-x86-static ../..
i.e. that "\EPICS\base" part.
I would check the contents of asyn/configure/RELEASE for definitions of SUPPORT and EPICS_BASE or the contents of environment variables.
Jani Hakala
- Replies:
- RE: Unable to build support modules on Windows, with base 3.15.2 Heesterman, Peter J
- References:
- Unable to build support modules on Windows, with base 3.15.2 Heesterman, Peter J
- Re: Unable to build support modules on Windows, with base 3.15.2 Jani Hakala
- RE: Unable to build support modules on Windows, with base 3.15.2 Mark Rivers
- RE: Unable to build support modules on Windows, with base 3.15.2 Heesterman, Peter J
- RE: Unable to build support modules on Windows, with base 3.15.2 Mark Rivers
- RE: Unable to build support modules on Windows, with base 3.15.2 Heesterman, Peter J
- Navigate by Date:
- Prev:
RE: Unable to build support modules on Windows, with base 3.15.2 Heesterman, Peter J
- Next:
RE: Unable to build support modules on Windows, with base 3.15.2 Heesterman, Peter J
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Unable to build support modules on Windows, with base 3.15.2 Heesterman, Peter J
- Next:
RE: Unable to build support modules on Windows, with base 3.15.2 Heesterman, Peter J
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|