EPICS Home

Experimental Physics and Industrial Control System


 
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  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 
<== Date ==> <== Thread ==>
Subject: RE: EPICS build for MVME3100
From: "Lawrence T. Hoff" <[email protected]>
To: "'Ron Sluiter'" <[email protected]>, "'William F. Steele'" <[email protected]>
Cc: [email protected]
Date: Tue, 20 Oct 2009 06:46:13 -0400 
I just checked my MV3100 build environment for VxWorks
5.5.1. I use :

Ccppc -mcpu=8540 -msoft-float -mspe=no -mabi=no-spe -DCPU=PPC85XX ...

It *is* a "special" compiler:
$ccppc -v
Reading specs from ../lib/gcc-lib/powerpc-wrs-vxworks/3.3-e500/specs
Configured with: /wind/river/host/src/gnu.e500/configure --with-headers=yes
--srcdir=/wind/river/host/src/gnu.e500
--prefix=/wind/river/host/gnu/3.3/sun4-solaris2 --target=powerpc-wrs-vxworks
--enable-languages=c,c++
Thread model: vxworks
gcc version 3.3-e500 20030421 (Wind River)

Compared with MV2100:
$ccppc -v
Reading specs from ../lib/gcc-lib/powerpc-wrs-vxworks/gcc-2.96/specs
gcc version gcc-2.96 (2.96+) 19990621 AltiVec VxWorks 5.5

HTH -- Larry

> -----Original Message-----
> From: [email protected] [mailto:tech-talk-
> [email protected]] On Behalf Of Ron Sluiter
> Sent: Thursday, October 15, 2009 1:01 PM
> To: William F. Steele
> Cc: [email protected]
> Subject: Re: EPICS build for MVME3100
> 
> Hello William,
> 
> According to this WRS web page;
> 
> http://www.windriver.com/products/bsp_web/bsp_architecture.html?archite
> cture=PowerPC
> 
> it does not look like the MVME3100 is supported with Tornado 2.2.1.
> 
> Ron
> 
> 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.
Replies:
Re: EPICS build for MVME3100 Andrew Johnson
References:
EPICS build for MVME3100 William F. Steele
Re: EPICS build for MVME3100 Ron Sluiter
Navigate by Date:
Prev: Bug in asyn 4-7 and up ?? Eric Norum
Next: Re: EPICS build for MVME3100 Andrew Johnson
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: EPICS build for MVME3100 Erik Johansson
Next: Re: EPICS build for MVME3100 Andrew Johnson
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