Experimental Physics and
Industrial Control System

 

Hi Iain,

 

What version of seq did you build?  Did you get any errors when it built?

 

When the seq module builds it compiles lots of .st files.  For example, this is part of the output I see:

 

preprocessing ../syncq.st

/usr/bin/gcc -x c -E  -D_GNU_SOURCE -D_DEFAULT_SOURCE           -D_X86_64_  -DUNIX  -Dlinux   -I. -I../O.Common -I. -I. -I.. -I../../../include/compiler/gcc -I../../../include/os/Linux -I../../../include -I/corvette/usr/local/epics-devel/base-7.0.1/include/compiler/gcc -I/corvette/usr/local/epics-devel/base-7.0.1/include/os/Linux -I/corvette/usr/local/epics-devel/base-7.0.1/include        ../syncq.st > syncq.i

compiling syncq.i to C

/home/epics/devel/seq-2-2-5/bin/linux-x86_64/snc   +m  syncq.i -o syncq.c

/usr/bin/gcc  -D_GNU_SOURCE -D_DEFAULT_SOURCE           -D_X86_64_  -DUNIX  -Dlinux     -O3 -g   -Wall      -mtune=generic     -m64  -I. -I../O.Common -I. -I. -I.. -I../../../include/compiler/gcc -I../../../include/os/Linux -I../../../include -I/corvette/usr/local/epics-devel/base-7.0.1/include/compiler/gcc -I/corvette/usr/local/epics-devel/base-7.0.1/include/os/Linux -I/corvette/usr/local/epics-devel/base-7.0.1/include        -c syncq.c

/usr/bin/g++ -o syncq  -L/home/epics/devel/seq-2-2-5/lib/linux-x86_64 -L/usr/local/epics-devel/base-7.0.1/lib/linux-x86_64 -Wl,-rpath,/home/epics/devel/seq-2-2-5/lib/linux-x86_64 -Wl,-rpath,/usr/local/epics-devel/base-7.0.1/lib/linux-x86_64           -rdynamic -m64        syncq.o    -lseq -lpv -ldbRecStd -ldbCore -lca -lCom

preprocessing ../timer.st

/usr/bin/gcc -x c -E  -D_GNU_SOURCE -D_DEFAULT_SOURCE           -D_X86_64_  -DUNIX  -Dlinux   -I. -I../O.Common -I. -I. -I.. -I../../../include/compiler/gcc -I../../../include/os/Linux -I../../../include -I/corvette/usr/local/epics-devel/base-7.0.1/include/compiler/gcc -I/corvette/usr/local/epics-devel/base-7.0.1/include/os/Linux -I/corvette/usr/local/epics-devel/base-7.0.1/include        ../timer.st > timer.i

compiling timer.i to C

/home/epics/devel/seq-2-2-5/bin/linux-x86_64/snc   +m  timer.i -o timer.c

/usr/bin/gcc  -D_GNU_SOURCE -D_DEFAULT_SOURCE           -D_X86_64_  -DUNIX  -Dlinux     -O3 -g   -Wall      -mtune=generic     -m64  -I. -I../O.Common -I. -I. -I.. -I../../../include/compiler/gcc -I../../../include/os/Linux -I../../../include -I/corvette/usr/local/epics-devel/base-7.0.1/include/compiler/gcc -I/corvette/usr/local/epics-devel/base-7.0.1/include/os/Linux -I/corvette/usr/local/epics-devel/base-7.0.1/include        -c timer.c

/usr/bin/g++ -o timer  -L/home/epics/devel/seq-2-2-5/lib/linux-x86_64 -L/usr/local/epics-devel/base-7.0.1/lib/linux-x86_64 -Wl,-rpath,/home/epics/devel/seq-2-2-5/lib/linux-x86_64 -Wl,-rpath,/usr/local/epics-devel/base-7.0.1/lib/linux-x86_64           -rdynamic -m64        timer.o    -lseq -lpv -ldbRecStd -ldbCore -lca -lCom

 

 

Do you see that output?  If so, then it knew how to compile .st files when building the seq module, and it seems like it should know how to do it for other modules as well.

 

Mark

 

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Iain Marcuson via Tech-talk
Sent: Tuesday, December 11, 2018 1:21 PM
To: [email protected]
Subject: FW: Build failure when compiling synApps from source

 

I was able to build the standalone sequencer fine.  Yokogawa appears to build, but asyn fails with

 

make[4]: *** No rule to make target `ipSNCServer.o', needed by `libtestIPServerSupport.a'.  Stop.

 

The other modules appear to depend on asyn, so I was not able to test them.

 

 

> -----Original Message-----

> From: [email protected] <[email protected]> On

> Behalf Of Mark Rivers via Tech-talk

> Sent: Tuesday, December 11, 2018 11:51 AM

> To: [email protected]

> Subject: Fw: Build failure when compiling synApps from source

>

>

>

>

> ________________________________

> From: Mark Rivers

> Sent: Tuesday, December 11, 2018 10:50 AM

> To: Iain Marcuson

> Subject: Re: Build failure when compiling synApps from source

>

>

> What happens when you build other synApps modules that have SNL

> program (optics, motor, asyn, mca, etc.)?  Do they all fail the same

> way?  Did the seq code itself build without errors?  It build lots of .st programs.

>

>

> Mark

>

>

>

> ________________________________

> From: [email protected] <[email protected]> on

> behalf of Iain Marcuson via Tech-talk <[email protected]>

> Sent: Tuesday, December 11, 2018 10:38 AM

> To: [email protected]

> Subject: Build failure when compiling synApps from source

>

>

> I am attempting to build EPICS natively on an ARM platform running Linux.

> EPICS base installs fine, but synApps fails when building (make

> release followed by make) SSCAN with the following error:

>

>

>

> make[4]: *** No rule to make target `scanProg.o', needed by

> `libscanProgress.a'.  Stop.

>

>

>

> snc is installed in the installation, and I have tried manually

> including the sequencer RULES_BUILD file.  My configuration is as

> below

>

>

>

> -OS Debian 7.11

>

> -System: 32-bit ARM, EPICS_HOST_ARCH=linux-arm

>

> -Base from launchpad, November 30, commit 0649a2f1

>

> -SynApps 6.0

>

> -Base installed to /opt/epics

>

> -SynApps SUPPORT var set to source directory, EPICS_BASE set to

> /opt/epics

>

> -snc binary in /opt/epics/bin/linux-arm

>

> -PATH, LD_LIBRARY_PATH, and HOST_ARCH appropriately set

>

>

>

> Are there other configurations I need to change, or something else entirely?

>

>

>

> Thank you,

>

>

>

> Iain Marcuson

>

> Software Engineer, Sydor Technologies

>

> 585.278.1168 |

> www.SydorTechnologies.com<http://www.sydortechnologies.com/>

>

> Skype: [email protected]

>