EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: moving initHooks into libCom
From: Mark Rivers <[email protected]>
To: 'Michael Davidsaver' <[email protected]>, Andrew Johnson <[email protected]>, "[email protected]" <[email protected]>
Date: Fri, 8 Dec 2017 20:48:07 +0000
Hi Michael,

I have tested that fix on VS2015 and VS2017.  It fixes the problem.  I am now building all of R7.0.1-rc1 with that patch on 2010, 2015, and 2017.

Mark


> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of Michael Davidsaver
> Sent: Friday, December 08, 2017 2:32 PM
> To: Andrew Johnson; [email protected]
> Subject: Re: moving initHooks into libCom
> 
> On 12/08/2017 03:29 PM, Andrew Johnson wrote:
> > Michael,
> >
> > In case your Inbox filters out Jenkins emails the epics-master-windows
> > APS job is now demonstrating the pva2pva build failure.
> 
> I noticed.  If this is the only failure, then I might have it sorted out quickly.
> 
> https://github.com/mdavidsaver/pva2pva/commit/049ed8cead5e59dea7f6631698c45ea63db
> 78d66
> 
> 
> > Thanks,
> >
> > - Andrew
> >
> > On 12/08/2017 02:09 PM, Andrew Johnson wrote:
> >> On 12/08/2017 01:57 PM, Mark Rivers wrote:
> >>> I forget exactly what CALL does, but I don't think it's necessary.  It's
> >>> worth trying I guess.
> >>
> >> Yes, that fixed it. Jenkins runs build commands inside its own .BAT
> >> file, and apparently executing one .BAT file inside another stops the
> >> parent script. It's currently compiling using
> >>
> >>> Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24215.1 for x64
> >>
> >> as against
> >>
> >>> Microsoft (R) C/C++ Optimizing Compiler Version 16.00.40219.01 for x64
> >>
> >>> Can you try the command interactively on that machine?
> >>
> >> I can't open a command window with the Jenkins build environment, the
> >> Jenkins agent sets up the shell environment by itself, and it's
> >> complicated by the fact that it's all running inside a JVM too.
> >>
> >> - Andrew
> >>
> >


Replies:
Re: moving initHooks into libCom Andrew Johnson
References:
moving initHooks into libCom Michael Davidsaver
Re: moving initHooks into libCom Andrew Johnson
Re: moving initHooks into libCom Michael Davidsaver
Re: moving initHooks into libCom Andrew Johnson
RE: moving initHooks into libCom Mark Rivers
Re: moving initHooks into libCom Andrew Johnson
RE: moving initHooks into libCom Mark Rivers
Re: moving initHooks into libCom Andrew Johnson
Re: moving initHooks into libCom Andrew Johnson
Re: moving initHooks into libCom Michael Davidsaver

Navigate by Date:
Prev: Re: moving initHooks into libCom Michael Davidsaver
Next: Re: moving initHooks into libCom Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: moving initHooks into libCom Michael Davidsaver
Next: Re: moving initHooks into libCom Andrew Johnson
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·