Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: RE: Problem building base-7.0.1 with Windows on a Linux file system
From: Mark Rivers <rivers@cars.uchicago.edu>
To: 'Andrew Johnson' <anj@aps.anl.gov>, "core-talk@aps.anl.gov" <core-talk@aps.anl.gov>
Date: Tue, 5 Dec 2017 00:35:40 +0000
Hi Andrew,

Thanks for the quick reply.

> Do you ever need an architecture-specific CONFIG_SITE.local file to match?

Not that I can recall.

Note that building for Windows on a Linux host used to be very slow.  I put up with it because the simplicity of a single working directory where I could test Linux and Windows together was worth it.

However, as of the SMB server that is in Centos 7 the performance is excellent. I just timed building all of base-7.0.1 on Windows with the files on my Centos 7 server.  It was under 5 minutes. It was using more than 7 on my 8 core Windows machine, so it is now CPU bound and no longer I/O bound like it was when I was running Fedora 15, for example.

Mark


> -----Original Message-----
> From: core-talk-bounces@aps.anl.gov [mailto:core-talk-bounces@aps.anl.gov] On Behalf
> Of Andrew Johnson
> Sent: Monday, December 04, 2017 6:14 PM
> To: core-talk@aps.anl.gov
> Subject: Re: Problem building base-7.0.1 with Windows on a Linux file system
> 
> Hi Mark,
> 
> On 12/04/2017 05:38 PM, Mark Rivers wrote:
> > I am having trouble building for EPICS_HOST_ARCH=windows-x64-static on a
> > Linux file server.  Previously when building EPICS base there were no
> > RELEASE or RELEASE.local files to worry about.  This is not the case
> > with 7.0.1.
> 
> Actually your issue isn't really that you're building for Windows on a
> Linux file-system (the file-system itself isn't the problem), as that
> you want to share a single installation of Base between both Linux and
> Windows, and we obviously haven't thought about that configuration
> properly because it just doesn't work at the moment.
> 
> > The file modules/RELEASE.local contains
> >
> > EPICS_BASE = /usr/local/epics/base-7.0.1
> >
> > which is where I put it on Linux.
> 
> Right. This file gets created the first time that GNUmake descends into
> the modules directory. If you had built this on Windows first the
> contents would reflect the path there instead.
> 
> > I tried creating a new file in that directory,
> > RELEASE.local.windows-x64-static.  It contains:
> >
> > EPICS_BASE = H:/epics/base-7.0.1
> >
> > which is the correct path for Windows.  However, that file does not seem
> > to get included
> 
> Right, it won't, we currently only include a single RELEASE.local file.
> 
> > It would be very nice if all I need to do is to create
> > modules/RELEASE.local.$(EPICS_HOST_ARCH)  to define EPICS_BASE and
> > everything else just built out of the box.  As it is now I need to edit
> > configure/RELEASE in 9 directories.
> >
> > Perhaps I am missing something?
> 
> No, we just didn't think of this - you're the only person I know who
> uses this particular configuration.
> 
> Then on 12/04/2017 at 05:55 PM, Mark Rivers wrote:
> 
> > Never mind, I came up with a simple solution.  I edited
> > modules/RELEASE.local to pull in architecture-specific version from that
> > location:
> >
> > EPICS_BASE = /usr/local/epics/base-7.0.1
> > -include $(TOP)/../RELEASE.local.$(EPICS_HOST_ARCH)
> >
> > That works fine, and involves editing just that file and adding the new
> > RELEASE.local.$(EPICS_HOST_ARCH) files.
> >
> > This second line might be added when modules/RELEASE.local is created.
> > It would save others having to reinvent what I just did.
> 
> I will probably just generate RELEASE.local.<host-arch> and modify our
> submodule configure/RELEASE files to pull that in instead. This way the
> solution is automatic and you shouldn't have to do anything for it to
> work (you will get a RELEASE.local.* file for each host-architecture you
> build for).
> 
> Do you ever need an architecture-specific CONFIG_SITE.local file to match?
> 
> Thanks for the report and suggested fix.
> 
> - Andrew
> 
> 
> --
> Arguing for surveillance because you have nothing to hide is no
> different than making the claim, "I don't care about freedom of
> speech because I have nothing to say." -- Edward Snowdon

References:
Problem building base-7.0.1 with Windows on a Linux file system Mark Rivers
Re: Problem building base-7.0.1 with Windows on a Linux file system Andrew Johnson

Navigate by Date:
Prev: Re: Problem building base-7.0.1 with Windows on a Linux file system Andrew Johnson
Next: Problem building areaDetector with base7.0.1-rc1 Mark Rivers
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: Problem building base-7.0.1 with Windows on a Linux file system Andrew Johnson
Next: Problem building areaDetector with base7.0.1-rc1 Mark Rivers
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 04 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·