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  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  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  <20192020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: SPEC "can't get a big memory buffer" issue
From: "Johnson, Andrew N. via Tech-talk" <[email protected]>
To: Gerry Swislow <[email protected]>, Matt Newville <[email protected]>
Cc: "Stubbs, Joanne E." <[email protected]>, Zhang Dongzhou <[email protected]>, Peter Eng <[email protected]>, "[email protected]" <[email protected]>
Date: Wed, 23 Jan 2019 17:51:24 +0000
Hi Gerry,

On 1/23/19 10:19 AM, Gerry Swislow via Tech-talk wrote:
> I don't know perl, but just to get through the build, I added a line to the file modules/ca/src/perl/Makefile in the EPICS 7.0.2 distribution as shown.  With that, the build completes on the macOS Mojave platform.  And as far as linking goes, the next release of spec will link with the 7.0 channel access libraries if the spec install configuration points to them.
>
> I would think that the EPICS build should work with the stock perl distributed with macOS.  If it is a bug in the way macOS packages perl, maybe the EPICS configuration tools should work around the bug, as macOS is a rather mainstream platform.  It seems excessive to have to install a /usr/local version of perl just to fix the one "-I" flag.
I'm sorry you got hit by this, but as you guessed the problem was caused
by Apple installing Perl differently in Mojave (again). None of my macOS
systems here at APS have been upgraded to Mojave yet or I would have
seen it already, you just happened to be the first person to report the
problem. Other applications have had similar problems with building on
Mojave, so it's not that we're doing things wrong, we just can't predict
how Apple will changes things next so we have to play catch-up.

There was already one workaround for incomplete Perl installations in
that Makefile but it was detecting a different issue that happened years
ago, although I don't remember if macOS was reponsible for that or not.
I will work out how to detect this and modify the Makefile to either
find EXTERN.h in the new location, or disable building the Perl CA bindings.

- 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:
Re: SPEC "can't get a big memory buffer" issue Mark Rivers via Tech-talk
Re: SPEC "can't get a big memory buffer" issue Matt Newville via Tech-talk
Re: SPEC "can't get a big memory buffer" issue Gerry Swislow via Tech-talk
Re: SPEC "can't get a big memory buffer" issue Matt Newville via Tech-talk
Re: SPEC "can't get a big memory buffer" issue Gerry Swislow via Tech-talk

Navigate by Date:
Prev: Re: SPEC "can't get a big memory buffer" issue Gerry Swislow via Tech-talk
Next: Re: Segmentation Fault when exiting certain Area Detector IOCs Wlodek, Jakub via Tech-talk
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  <20192020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: SPEC "can't get a big memory buffer" issue Gerry Swislow via Tech-talk
Next: Re: SPEC "can't get a big memory buffer" issue Heinz Junkes via Tech-talk
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  <20192020  2021  2022  2023  2024 
ANJ, 07 Feb 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·