EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: ../../bin/linux-x86_64/testIOC: bad interpreter: No such file or directory
From: Valentyn Stadnytskyi via Tech-talk <[email protected]>
To: [email protected]
Date: Sun, 17 Nov 2019 14:06:54 -0600
Hello,

I am having problem running a test IOC I just created following instructions https://epics-controls.org/resources-and-support/documents/getting-started/

:~/EPICS/epics-base/test/testIoc/iocBoot/ioctestIoc$ ./st.cmd
-bash: ./st.cmd: ../../bin/linux-x86_64/testIOC: bad interpreter: No such file or directory

Back in 2016 Daniel Crisp had a similar error. https://epics.anl.gov/tech-talk/2016/msg01736.php
../../bin/linux-x86_64/<PROD_IOC>^M: bad interpreter: No such file or directory

He had an extra symbol at the end resulting in a conflict. In my case it seems to be fine but I get the same error. I have looked into /bin/ folder and I cannot find linux-x86_64 there. (I tried to use find and ls -a)

The st.cmd file looks fine except the first line that presumably points at non-existing directory.

#!../../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"

And my envPath entries are pointing to where I think they should point. I didn’t change anything, it was all generated automatically, but I still inspected it.
epicsEnvSet("IOC","ioctestIoc")
epicsEnvSet("TOP","/home/femtoland/EPICS/epics-base/test/testIoc")
epicsEnvSet("EPICS_BASE","/home/femtoland/EPICS/epics-base")

Do I need to install some extra module or is something missing on my Linux installation? I am running Ubuntu 18.04

Thank you!
Valentyn
—————————————————
Valentyn Stadnytskyi
[email protected]






Replies:
Re: ../../bin/linux-x86_64/testIOC: bad interpreter: No such file or directory Michael Davidsaver via Tech-talk

Navigate by Date:
Prev: Re: Getting started with EPICS Heinz Junkes via Tech-talk
Next: string conversion to uppercase or lowercase Jeong Han Lee via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Getting started with EPICS Heinz Junkes via Tech-talk
Next: Re: ../../bin/linux-x86_64/testIOC: bad interpreter: No such file or directory Michael Davidsaver via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
ANJ, 17 Nov 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·