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: Building ASYN on Windows
From: Andrew Johnson <[email protected]>
To: [email protected]
Date: Mon, 10 Aug 2009 12:51:58 -0500
Hi John

On Monday 10 August 2009 11:39:47 John Dobbins wrote:
>
> The R3.14.10 Visual C++ build fails when executing the created file
> genApps.exe.
>
> The MinGW build fails when executing the created file dBToMenuH.exe

Both of those failures were in programs that were built earlier in the 
process.  What is strange though is that those aren't the first programs to 
be run that we built earlier; that honor goes to e_flex.exe and antelope.exe 
which are both used when compiling in the base/src/dbStatic directory and 
which run quite happily on your builds.  Indeed for your Visual C++ build all 
of the code that you actually need to build IOCs and Mark's areaDetector 
application have successfully been built by that stage, so you could ignore 
the gdd build failure (which is only needed for non-IOC CA servers) and 
continue on to compile your other modules at this point.

Question: What was your PATH set to when you were building these?  You didn't 
have the bin directory from another release of Base or from the EPICS Win32 
extensions in the path did you?  I would guess not, but I'd like to be sure 
of that.

> I am including the full output from both builds below, which includes
> some warnings.

At a brief glance through I recognize many of those warnings, which are not 
something that could have caused this problem.

The interesting thing is that in both cases the same error code occurs, which 
Mark Rivers points out to mean access violation (I'm taking his word there).

> Any advice on how to proceed from this point would be welcome.

If you still have or can repeat the VC++ build, just use that and ignore the 
build failure in gdd, the parts of Base you need have already built correctly 
by then so you can continue to build the other modules.  It would be good to 
get to the bottom of this though.

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

Replies:
Re: Building ASYN on Windows John Dobbins
References:
Building ASYN on Windows John Dobbins
RE: Building ASYN on Windows Mark Rivers
RE: Building ASYN on Windows John Dobbins

Navigate by Date:
Prev: RE: Building ASYN on Windows Mark Rivers
Next: RE: Building ASYN on Windows John Dobbins
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: Building ASYN on Windows Andrew Johnson
Next: Re: Building ASYN on Windows John Dobbins
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 ·