Experimental Physics and
Industrial Control System

On 4/14/11 10:01 AM, Allison, Stephanie wrote:
> I discovered that even building RTEMS 32 bit sequences (using
> the RTEMS 32bit tool chain) on a linux-x86_64 build is
> problematic as the 64bit-built SNC compiler will, in some
> special cases, convert the .st file to a buggy .c file (in the
> initialization of the state event masks).

I had a similar problem compiling on RHEL 5 (linux-x86_64) for
VxWorks (vxWorks-ppc603, vxWorks-ppc604, and
vxWorks-ppc604_long) using EPICS 3.14.11 (+ Known Problems
patches), SEQ 2.0.12 (as packaged in SynApps 5.5), and the
Tornado 2.0.2 toolchain.  I haven't had time to investigate, but
indeed the SNC compiler was generating .c files that the
cross-compiler could not compile.  I think the SNC compiler was
generating integer values greater than what could fit in 32 bits
which the cross-compiler choked on.

Lewis

-- 
J. Lewis Muir
Software Engineer
IMCA-CAT

Replies:

Re: ioc segfault if - c seq flag is not set or +c? Benjamin Franksen

References:

ioc segfault if - c seq flag is not set or +c? Abadie Lana

RE: ioc segfault if - c seq flag is not set or +c? Abadie Lana

RE: ioc segfault if - c seq flag is not set or +c? Allison, Stephanie

Navigate by Date:

Prev: RE: ioc segfault if - c seq flag is not set or +c? Allison, Stephanie

Next: Re: ca.py - Throws error - workaround Matt Newville

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: RE: ioc segfault if - c seq flag is not set or +c? Allison, Stephanie

Next: Re: ioc segfault if - c seq flag is not set or +c? Benjamin Franksen

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