Re: FW: Build failure when compiling synApps from source

[Jeong Han Lee via Tech-talk <tech-talk@aps.anl.gov>]

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 <rivers@cars.uchicago.edu>
> > > *Sent:* Tuesday, December 11, 2018 3:24 PM
> > > *To:* Iain Marcuson <iain.marcuson@sydortechnologies.com>; Johnson, 
> > > Andrew N. <anj@anl.gov>
> > > *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:* tech-talk-bounces@aps.anl.gov 
> > > <mailto:tech-talk-bounces@aps.anl.gov> <tech-talk-bounces@aps.anl.gov 
> > > <mailto:tech-talk-bounces@aps.anl.gov>> *On Behalf Of *Iain Marcuson 
> > > via Tech-talk
> > > *Sent:* Tuesday, December 11, 2018 2:04 PM
> > > *To:* Johnson, Andrew N. <anj@anl.gov <mailto:anj@anl.gov>>
> > > *Cc:* tech-talk@aps.anl.gov <mailto:tech-talk@aps.anl.gov>
> > > *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. <anj@anl.gov <mailto:anj@anl.gov>>
> > > *Sent:* Tuesday, December 11, 2018 2:57 PM
> > > *To:* Iain Marcuson <iain.marcuson@sydortechnologies.com 
> > > <mailto:iain.marcuson@sydortechnologies.com>>; tech-talk@aps.anl.gov 
> > > <mailto:tech-talk@aps.anl.gov>
> > > *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

git clone https://git.launchpad.net/epics-base

cd epics-base

git checkout 0649a2f1

git submodule update --init --reference ./


echo "INSTALL_LOCATION=/opt/epics" > configure/CONFIG_SITE.local

sudo make


wget -c https://epics.anl.gov/bcda/synApps/tar/synApps_6_0.tar.gz

tar xvzf synApps_6_0.tar.gz


cd synApps/support/


echo "SUPPORT=/home/pi/playground/synApps/support" > configure/SUPPORT.linux-arm
echo "EPICS_BASE=/opt/epics" > configure/EPICS_BASE.linux-arm
export EPICS_HOST_ARCH=linux-arm



echo "SUPPORT=/home/jhlee/playground/synApps/support" > configure/SUPPORT.linux-x86_64
echo "EPICS_BASE=/opt/epics" > configure/EPICS_BASE.linux-x86_64
export EPICS_HOST_ARCH=linux-x86_64



Disable DXP 
Disable DXPSITORO

configure/RELEASE

#DXP=$(SUPPORT)/dxp-R5-0
#DXPSITORO=$(SUPPORT)/dxpSITORO-R1-1


make release
make clean uninstall
make




# apt install libnet1-dev libpcap-dev