Experimental Physics and Industrial Control System
Hi Dan,
On 10/03/2016 05:13 PM, Crisp, Daniel wrote:
> When running my st.cmd, I get a bad interpreter error for my ioc’s
> executable:
>
> ../../bin/linux-x86_64/<PROD_IOC>^M: bad interpreter: No such file or
> directory
That error doesn't mean that your binary has been corrupted, the problem
is the ^M at the end of the #! line in your st.cmd file. Linux thinks
the ^M is part of the filename of the binary you want to use as the
interpreter for the st.cmd file, and it can't find such a binary. Try
typing the path to the binary directly and specifying the name of the
st.cmd file as its argument and I think it will run. Then remove all the
^M characters from your st.cmd file.
HTH,
- 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
- References:
- ioc executable being made corrupted Crisp, Daniel
- Navigate by Date:
- Prev:
ioc executable being made corrupted Crisp, Daniel
- Next:
Re: ioc executable being made corrupted Konrad, Martin
- 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
- Navigate by Thread:
- Prev:
ioc executable being made corrupted Crisp, Daniel
- Next:
Re: ioc executable being made corrupted Konrad, Martin
- 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