EPICS Controls 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  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: EPICS build for MVME3100
From: Andrew Johnson <[email protected]>
To: "Lawrence T. Hoff" <[email protected]>, "'William F. Steele'" <[email protected]>
Cc: [email protected]
Date: Tue, 20 Oct 2009 10:48:32 -0500
Hi Larry,

On Tuesday 20 October 2009 05:46:13 Lawrence T. Hoff wrote:
> 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 ...

Thanks for those, I'll modify the CONFIG.Common.vxWorks-mpc8540 in Base to 
match those flags.  We have also been giving  -mstrict-align -mlongcall  for 
the other PowerPC targets, which I will include with this target as well 
unless you can confirm they are not needed.

William F. Steele wrote:
> 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?

Very interesting, Wind River have upgraded the GCC compiler for the PowerPC 
e500 family; that does make some sense.  Unfortunately we don't have access to 
the e500 family architecture on vxWorks here at APS which is why Base doesn't 
build for it.

Please try editing your base/configure/os/CONFIG.Common.vxWorks-mpc8540 file 
and add the following line (anywhere below the include line), which should 
modify the build system to use the right compiler based on your paths above:

GNU_DIR_5 = $(WIND_BASE)/gnu/3.3/$(WIND_HOST_TYPE)

While you're at it, based on Larry's email I'm proposing the following 
settings as well which I'd appreciate if you could try out in place of the 
existing ones:

ARCH_DEP_CPPFLAGS = -DCPU=PPC85XX
ARCH_DEP_CFLAGS = -mcpu=8540 -msoft-float -mspe=no -mabi=no-spe
ARCH_DEP_CFLAGS += -mstrict-align -mlongcall

Please let me know whether all this works or if it needs tweaking.

- Andrew
-- 
The best FOSS code is written to be read by other humans -- Harald Welte


References:
EPICS build for MVME3100 William F. Steele
Re: EPICS build for MVME3100 Ron Sluiter
RE: EPICS build for MVME3100 Lawrence T. Hoff

Navigate by Date:
Prev: RE: EPICS build for MVME3100 Lawrence T. Hoff
Next: genSub and synApps 5_4_1 Emmanuel Mayssat
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: EPICS build for MVME3100 Lawrence T. Hoff
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  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·