Re: ../../bin/linux-x86_64/testIOC: bad interpreter: No such file or directory

[Valentyn Stadnytskyi via Tech-talk <tech-talk@aps.anl.gov>]

Thank you Mark!

On a similar note:

If one does everything according to these instructions from https://epics-controls.org/resources-and-support/documents/getting-started/

mkdir -p $HOME/EPICS/TEST/testIoc
cd $HOME/EPICS/TEST/testIoc
makeBaseApp.pl -t example testIoc
makeBaseApp.pl -i -t example testIoc
make
cd iocBoot/ioctestIoc
chmod u+x st.cmd

You get a st.cmd file with curly brackets instead of parenthesis for {TOP} and {IOC}. I don’t know where this is generated and where to report the bug. See the file below. This is minor but for someone who does it for the first time and never seen EPICS shell but be a big slowdown.

~/EPICS/IOCs/testIoc/iocBoot/ioctestIoc$ more st.cmd

#!../../bin/linux-x86_64/testIoc

#- You may have to change testIoc to something else

#- everywhere it appears in this file

< envPaths

cd "${TOP}"

## Register all support components

dbLoadDatabase "dbd/testIoc.dbd"

testIoc_registerRecordDeviceDriver pdbbase

## Load record instances

dbLoadTemplate "db/user.substitutions"

dbLoadRecords "db/testIocVersion.db", "user=femtoland"

dbLoadRecords "db/dbSubExample.db", "user=femtoland"

#- Set this to see messages from mySub

#var mySubDebug 1

#- Run this to trace the stages of iocInit

#traceIocInit

cd "${TOP}/iocBoot/${IOC}"

iocInit

## Start any sequence programs

#seq sncExample, "user=femtoland"

-----------------------------------

Valentyn Stadnytskyi

v.stadnytskyi@gmail.com

On Nov 17, 2019, at 9:27 PM, Mark Rivers <rivers@cars.uchicago.edu> wrote:

I helped Valentyn fix this today. It was a simple problem with testIoc vs testIOC. Changing the case fixed it.

Mark

Sent from my iPhone

On Nov 17, 2019, at 9:17 PM, Michael Davidsaver via Tech-talk <tech-talk@aps.anl.gov> wrote:

On 11/17/19 12:06 PM, Valentyn Stadnytskyi via Tech-talk wrote:
:~/EPICS/epics-base/test/testIoc/iocBoot/ioctestIoc$ ./st.cmd
-bash: ./st.cmd: ../../bin/linux-x86_64/testIOC: bad interpreter: No such file or directory

What happens if you instead run the following from the same directory?

$ ../../bin/linux-x86_64/testIOC st.cmd