| 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 <2019> 2020 2021 2022 2023 2024 2025 | 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 <2019> 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: ../../bin/linux-x86_64/testIOC: bad interpreter: No such file or directory |
| From: | Mark Rivers via Tech-talk <[email protected]> |
| To: | Michael Davidsaver <[email protected]> |
| Cc: | "[email protected]" <[email protected]>, Valentyn Stadnytskyi <[email protected]> |
| Date: | Mon, 18 Nov 2019 03:27:19 +0000 |
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 <[email protected]> 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