Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: EPICS build for MVME3100
From: Dirk Zimoch <dirk.zimoch@psi.ch>
To: "William F. Steele" <wfsteele@lbl.gov>
Cc: tech-talk@aps.anl.gov
Date: Thu, 15 Oct 2009 09:15:29 +0200
Hi William,

I has a similar problem with the MVME4100, which is also based on a e500 core like your MVME3100. Finally, I had to use vxWorks 6.7 which provides a newer compiler. I guess that the compiler options were done for vxWorks 6 and vxWorks 5 does not know about CPU=PPC32.

Maybe you have to modify the compiler options in the EPICS make configurations to work with vxWorks 5. I suggest to find out which options vxWorks uses when it builds the kernel. You may also have a look at the processor specific supplement documentation of vxWorks.

Hope that helps
Dirk

William F. Steele wrote:
I don't understand how to build EPICS for MVME3100. I have no problem with mcp750, mvme2100, 68040, or 68060. I am trying to build EPICS 3.14.11 and am using vxWorks 5.5.1 with Tornado 2.2.1. If I put vxWorks-mpc8540 in my list of CROSS_COMPILER_TARGET_ARCHS, I get compile errors which I traced to ARCH_DEP_CPPFLAGS which is set to -DCPU=PPC32 which the compiler does not recognize. If I change that to ARCH_DEP_CPPFLAGS = -DCPU=PPC85XX, then I no longer get compile errors, but EPICS will not load due to a lot of undefined symbols. I talked to WRS about this problem and was advised that I was using the wrong compiler. When I use Tornado to build vxWorks, Tornado uses /home/als2/devel/vxWorks/tornado2.2.1-ppc/host/gnu/3.3/sun4-solaris2/bin/ccppc, but when building EPICS, the EPICS build system uses /home/als2/devel/vxWorks/tornado2.2.1-ppc/host/sun4-solaris2/bin/ccppc, so, apparently, the EPICS build system does not automatically setup to use the correct tools when specifying the target
vxWorks-mpc8540. What needs to be done to make this work right? Thanks.


--
Dr. Dirk Zimoch
Paul Scherrer Institut, WBGB/006
5232 Villigen PSI, Switzerland
Phone +41 56 310 5182

References:
EPICS build for MVME3100 William F. Steele

Navigate by Date:
Prev: EPICS build for MVME3100 William F. Steele
Next: procServ softIOC server - V2.4.1 released Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: EPICS build for MVME3100 William F. Steele
Next: Re: EPICS build for MVME3100 Ron Sluiter
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·