Re: ioc executable being made corrupted

["Konrad, Martin" <konrad@frib.msu.edu>]

Hi Dan,
>> ../../bin/linux-x86_64/<PROD_IOC>^M: bad interpreter: No such file or
>> directory
Andrew is right. This is probably caused by Windows line endings in your
st.cmd file. "dos2unix st.cmd" should fix your issue. In case you don't
have that command try

sed -i -e "s/\^M//" st.cmd

Cheers,

Martin

P.S.: Are you tracking your IOC code in Git? If so Git should take care
of converting line endings for you.

-- 
Martin Konrad
Control System Engineer
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: konrad@frib.msu.edu