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 <2019> 2020 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 <2019> 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Trying to get new R3.15.7 and synapps 6.1 working. |
From: | "Lang, Keenan C. via Tech-talk" <[email protected]> |
To: | "Johnson, Andrew N. via Tech-talk" <[email protected]>, Eric Norum <[email protected]> |
Date: | Mon, 4 Nov 2019 23:38:19 +0000 |
Looking over makefiles, if the CALC module is defined in the StreamDevice RELEASE file, the stream.dbd file will contain that scalcout device support line. The CaenFastPS module then includes stream.dbd without also including sCalcoutRecord.dbd (or calcSupport.dbd
which grabs all the calc dbd files) which means that the scalcout record is never defined when the dbd is expanded.
You'll either need to:
* comment out the CALC module in StreamDevice,
* include the calc module and the needed dbd files into the CaenFastPS module,
* or change the inclusion of stream.dbd to including the file stream-base.dbd instead
From: Tech-talk <[email protected]> on behalf of Eric Norum via Tech-talk <[email protected]>
Sent: Monday, November 4, 2019 5:12 PM To: Johnson, Andrew N. via Tech-talk <[email protected]> Subject: Trying to get new R3.15.7 and synapps 6.1 working.
My attempts at upgrading to a newer version of EPICS base and support modules have foundered. I downloaded and built base-3-15.7, synapps-6., and the latest StreamDevice. No (major) problems there. I had to
comment out the Oriel motor support because there appears to be no OrielRegister.h but other than that everything built.
But when trying to build one of my support modules and test IOCs I get odd complaints about scalcout record support:
The empty scalcout record declaration breaks things when the test IOC starts
up:
Suggestions?
--
Eric Norum [email protected] |