Experimental Physics and Industrial Control System
|
I solved the installation problem:
- my env vars:
# --------------------------------------------------------------------
export EPICS_BASE="/opt/epics/base"
export EPICS_HOST_ARCH=`${EPICS_BASE}/startup/EpicsHostArch`
export PATH="${PATH}:${EPICS_BASE}/bin/${EPICS_HOST_ARCH}"
export EPICS_EXTENSIONS="/opt/epics/extensions"
export PATH="${PATH}:${EPICS_EXTENSIONS}/bin/${EPICS_HOST_ARCH}"
export
LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${EPICS_BASE}/lib/${EPICS_HOST_ARCH}"
export EPICS_SUPPORT="/opt/epics/extensions/synApps_6_1"
export EPICS_HOST_ARCH="linux-x86_64"
export HOST_ARCH="linux-x86_64"
# --------------------------------------------------------------------
Then:
in /opt/epics/extensions/synApps_6_1/support/configure/RELEASE
edited the variables as:
SUPPORT=/opt/epics/extensions/synApps_6_1/support
EPICS_BASE=/opt/epics/base
in /opt/epics/extensions/synApps_6_1/support/xxx-R6-1/configure/RELEASE
added:
SUPPORT=/opt/epics/extensions/synApps_6_1/support
EPICS_BASE=/opt/epics/base
and commented:
#SUPPORT=$(SUPPORT)
in /opt/epics/extensions/synApps_6_1/support/assemble_synApps.sh
commented (because it is in my $EPICS_BASE environment vars)
#EPICS_BASE=/APSshare/epics/base-3.15.6
cd synApps_6_1/support
make release
make
make install
and everything went smoothy...
Thank you,
Ernesto
On 10/3/2019 6:24 AM, Johnson, Andrew N. wrote:
Oops, sorry I should have looked first. I was describing the generic process I had set up in the EPICS build system for submodules, I didn’t realize you had changed it that much – my bad!
- Andrew
On Oct 3, 2019, at 9:15 AM, Peterson, Kevin M. <[email protected]> wrote:
Andrew,
The motor/modules/Makefile puts more than INSTALL_LOCATION in the generated RELEASE.local.<arch> file:
https://github.com/epics-modules/motor/blob/1fc606fa1f7e75aec6f5da0a8cab0ad1a28f1c2a/modules/Makefile#L59
Driver modules rely on this file when they're built as submodules:
https://github.com/epics-motor/motorOms/blob/ee078b399c77135f88cbd672da72bc2ae9e0669e/configure/RELEASE#L4
But they use motor's RELEASE when built outside the motor tree:
https://github.com/epics-motor/motorOms/blob/ee078b399c77135f88cbd672da72bc2ae9e0669e/configure/EXAMPLE_RELEASE.local#L2
An error occurs when the generated RELEASE file contains only INSTALL_LOCATION and the driver modules include include motor's RELEASE. I'd have to look though the notes from the motor split to find the specific error message.
Kevin
On October 2, 2019 10:21:09 PM CDT, "Johnson, Andrew N. via Tech-talk" <[email protected]> wrote:
Hi Ernesto,
On Oct 2, 2019, at 7:24 PM, Ernesto Paiser via Tech-talk <[email protected]> wrote:
I'm trying to compile the motor-7-1 from synApps_6_1,
but after fixing some wrong files versions in
motor-7-1modules/RELEASE.linux-x86_64.local
and
motor-7-1/configure/RELEASE
asyn-R4-35 >>> asyn-R4-36
busy-R1-7-1 >>> busy-R1-7-2
ipac-R2-15 >>> ipac-2-15
I still getting this error:
#motor-7-1/make clean; make
...
make -C ./modules install
make[1]: Entering directory `/opt/epics/extensionsTop_20120904/synApps_6_1/support/motor-7-1/modules'
make -C ./motorOms install
make[2]: Entering directory `/opt/epics/extensionsTop_20120904/synApps_6_1/support/motor-7-1/modules/motorOms'
configure/CONFIG:17: /configure/CONFIG: No such file or directory
configure/RULES_DIRS:2: /configure/RULES_DIRS: No such file or directory
make[2]: *** No rule to make target `/configure/RULES_DIRS'. Stop.
When you said you fixed the modules/RELEASE.linux-x86_64.local file I think that’s where you went wrong, that is not a regular configure/RELEASE file. It actually gets created by the build and provides the install location of the top-level motor-7-1 tree for building the individual submodules.
I suggest you delete that file, then cd into the modules directory and type ‘make RELEASE.host’ which will recreate it with what should be the correct content (it should ONLY set one variable, probably MOTOR, pointing to the INSTALL_LOCATION for the motor-7-1 build). If you disagree with its contents, please post both versions here and explain why. When the file is correct you should be able to run ‘make’ from the modules directory to build all of the submodules.
HTH,
- Andrew
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
- References:
- motor-7-1 make errors Ernesto Paiser via Tech-talk
- Re: motor-7-1 make errors Johnson, Andrew N. via Tech-talk
- Re: motor-7-1 make errors Peterson, Kevin M. via Tech-talk
- Re: motor-7-1 make errors Johnson, Andrew N. via Tech-talk
- Navigate by Date:
- Prev:
Re: motor-7-1 make errors Johnson, Andrew N. via Tech-talk
- Next:
Set enum strings from SNL David Vine 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
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: motor-7-1 make errors Johnson, Andrew N. via Tech-talk
- Next:
CAS UDP Errors Abdalla Ahmad 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
<2019>
2020
2021
2022
2023
2024
|
ANJ, 03 Oct 2019 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|