Re: Window build error - can find script. [SEC=OFFICIAL]

["Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>]

Another possible issues I see is that there are colon characters (C:/​) in the paths. Make really doesn't like colons (or spaces) in filenames since colons are used as separators in rules, so it might be worth trying to remove them if nothing else helps.

- Andrew

-- 

Complexity comes for free, Simplicity you have to work for.

On 7/27/26, 10:16 AM, "Tech-talk" <tech-talk-bounces at aps.anl.gov> wrote:

Hi,

 

I think I saw this same error once before with gnu make 3.81 on windows, so as Yong mentions worth checking which version of make has been picked up by the build

 

Regards,

 

Freddie  

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Hu, Yong via Tech-talk
Sent: 27 July 2026 14:59
To: Mark Rivers <rivers at cars.uchicago.edu>; Tech-Talk <tech-talk at aps.anl.gov>; STARRITT, Andrew <andrews at ansto.gov.au>
Subject: Re: Window build error - can find script. [SEC=OFFICIAL]

 

This appears to be a classic Windows path separator issue, where backslashes (\) and forward slashes (/) get mixed up.

Using a native Windows version of GNU Make might be the cleanest solution. Alternatively, you can override the TOOLS variable by adding the following line to adSpectrum/CONFIG_SITE (or adSpectrum/CONFIG_SITE.local): TOOLS = $(EPICS_BASE_HOST_BIN)

Yong

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
Date: Monday, July 27, 2026 at 9:12 AM
To: Tech-Talk <tech-talk at aps.anl.gov>, STARRITT, Andrew <andrews at ansto.gov.au>
Subject: Re: Window build error - can find script. [SEC=OFFICIAL]

 

Hi Andrew,

 

Does this error happen only when building ADSpectrum, and not when building ADCore, etc.?

 

I don't know what ADSpectrum is.  Where is it located?

 

Mark

 

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of STARRITT, Andrew via Tech-talk <tech-talk at aps.anl.gov>
Sent: Monday, July 27, 2026 12:22 AM
To: Tech-Talk <tech-talk at aps.anl.gov>
Subject: Window build error - can find script. [SEC=OFFICIAL]

 

Hi all,

 

One of my colleagues is having a windows build issue building areaDetector-R3-13/adSpectrum using base-7.0.8 on windows-x64 architecture.

He is getting same result with 7.0.10

 

The error:

 

C:\controls_sw\devel\areaDetector-R3-13\adSpectrum>make

make: Entering directory `C:/controls_sw/devel/areaDetector-R3-13/adSpectrum'

make -C ./configure install

make[1]: Entering directory `C:/controls_sw/devel/areaDetector-R3-13/adSpectrum/configure'

perl -CSD C:/controls_sw/devel/areaDetector-R3-13/adSpectrum/configure/c:/controls_sw/devel/epics-base-R7.0.8/bin/windows-x64/makeMakefile.pl O.windows-x64 ../..

Can't open perl script "C:/controls_sw/devel/areaDetector-R3-13/adSpectrum/configure/c:/controls_sw/devel/epics-base-R7.0.8/bin/windows-x64/makeMakefile.pl": Invalid argument

make[1]: *** [O.windows-x64] Error 22

 

Changing TOOLS = $(abspath $(EPICS_BASE_HOST_BIN)) to TOOLS = $(EPICS_BASE_HOST_BIN) in

epics base CONFIG_BASE fixes the issue when compiling under windows.

 

Is there a better way to get this to work?

 

Thanks in advance

 

Andrew Starritt

Australian Synchrotron