Experimental Physics and
Industrial Control System

Jeong Han Lee via Tech-talk <[email protected]> · Thu, 13 Dec 2018 22:47:16 +0100

Hi Iain,

 I only think, the reason why you cannot install them on your target

are the following two :

  1) Debian 7
  2) Missing packages
  3) Both

 In order to debug your issue, it may be needed to get your full

activity log for your installation procedure.

  With snippet information, it is impossible to debug them.

  Best,
  Han

On 12/13/18 8:49 PM, Iain Marcuson wrote:

I tried installing EPICS and synApps to two different directories, and synApps failed at the same point, even on my linux-x86_64 machine.  Since this approach would not work for us for other reasons, I plan to abandon this approach unless someone wants more details.

Thank you,

Iain.

-----Original Message-----
From: Jeong Han Lee <[email protected]>
Sent: Thursday, December 13, 2018 8:31 AM
To: [email protected]
Cc: Iain Marcuson <[email protected]>
Subject: Re: FW: Build failure when compiling synApps from source

Hi Iain,

      INSTALL_LOCATION in BASE and SYNAPPS should be different. "make
clean or uninstall" will remove the BASE also. So it is better to use other
directory.

     I tested two tests on Debian 9 and Raspbian 9 as following environment
variables:

     * Debian 9
      EPICS_BASE=/opt/epics
      SUPPORT=/home/jhlee/playground/synApps/support

     * Raspbian 9
      EPICS_BASE=/opt/epics
      SUPPORT=/home/pi/playground/synApps/support

      With the enclosed instruction, I can install all on Debian 9
(linux_x86_64) and all except DXP and DXPSITORO on Raspbian 9
(linux-arm) without any issues. You may try to do this first, and switch the
INSTALL_LOCATION of synApps differently, for example,
/opt/epics/synApps-6.0.0 .

     I may try it later, since my old Raspberry Pi is not so powerful, it takes a lot
of time to do this.

     All what I've done is that I configured and installed with the direct compiling
on each architecture.

     HTH,
     Han

On 12/12/18 3:43 PM, Jeong Han Lee wrote:

Hi Iain,

    I have one more question :

    Could you install epics through cross-compiler or on the linux-arm
directly?

    If you do on the linux-arm directly, could you install epics through

    https://github.com/jeonghanlee/epics_manifest ; ?

    You can simply follow README to how it works. I don't recommend to
use this, but I would like to see whether your OS has issues or not.

    It doesn't contain the synApps, but some of them with proper orders.

    Maybe this is not the proper way, meanwhile I am setup with synApp on
my old RPi.

    Best,
    Han

On 12/12/18 3:37 PM, Jeong Han Lee wrote:

Hi Iain,

    Which EPICS BASE do you use?

    Han

On 12/12/18 3:09 PM, Iain Marcuson via Tech-talk wrote:

asyn/config/RELEASE does point to $(SUPPORT)/seq-2-2-5.

*From:* Mark Rivers <[email protected]>
*Sent:* Tuesday, December 11, 2018 3:24 PM
*To:* Iain Marcuson <[email protected]>;

Johnson,

Andrew N. <[email protected]>
*Subject:* RE: FW: Build failure when compiling synApps from source

Does asyn/config/RELEASE have an entry that correctly points to
$(SUPPORT)/seq-2-2-5?  If so, it should find the rule to build .st
files.

*From:* [email protected]
<mailto:[email protected]> <tech-talk-

[email protected]

<mailto:[email protected]>> *On Behalf Of *Iain

Marcuson

via Tech-talk
*Sent:* Tuesday, December 11, 2018 2:04 PM
*To:* Johnson, Andrew N. <[email protected] <mailto:[email protected]>>
*Cc:* [email protected] <mailto:[email protected]>
*Subject:* RE: FW: Build failure when compiling synApps from source

The synApps RELEASE files point to $(SUPPORT)/seq-2-2-5.  That said,
how would I install EPICS and synApps in a distinct directory if I
need to include the source?

Iain.

*From:* Johnson, Andrew N. <[email protected] <mailto:[email protected]>>
*Sent:* Tuesday, December 11, 2018 2:57 PM
*To:* Iain Marcuson <[email protected]
<mailto:[email protected]>>; tech-

[email protected]

<mailto:[email protected]>
*Subject:* Re: FW: Build failure when compiling synApps from source

Hi Iain,

On 12/11/18 1:20 PM, Iain Marcuson via Tech-talk wrote:

     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 sequencer provides its own set of build rules which the EPICS
build system will pull in automatically from the sncseq module when
you list it in your application's configure/RELEASE file. This isn't
happening for you, and I suspect you're trying to use a modified
build system since you also wrote this earlier:

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

That isn't how the sequencer normally comes, GNUmake needs to see

the

contents of the sncseq/configure/RULES_BUILD file for any application
that needs to compiler sequence programs.

- Andrew

--

Arguing for surveillance because you have nothing to hide is no

different than making the claim, "I don't care about freedom of

speech because I have nothing to say." -- Edward Snowdon

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System