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  2019  <20202021  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  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: error in 'make' during installation of areaDetector
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: 'Jong Woo Kim' <Jong.Woo.Kim at asu.edu>
Cc: tech-talk <tech-talk at aps.anl.gov>
Date: Wed, 26 Feb 2020 01:11:50 +0000

The errors you are getting are what I would expect if EPICS_BASE is not correctly defined.

 

Please double check that you have the path to EPICS_BASE correct in RELEASE_LIBS.local and RELEASE_PRODS.local.

 

Have you built EPICS_BASE successfully?

 

Mark

 

 

From: Jong Woo Kim <Jong.Woo.Kim at asu.edu>
Sent: Tuesday, February 25, 2020 7:01 PM
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk <tech-talk at aps.anl.gov>
Subject: Re: error in 'make' during installation of areaDetector

 

Hi Mark,

 

Thank you. Note that when I did 'git clone' for areaDetector under 'support', 'areaDetector' folder was created and ADCore, ADSupport and ADEiger were installed below it, not below areaDetector-R3-7.

In addition, I installed asyn4-37 under support.

 

The following is RELEASE_LIBS.local

____________________________________________

 

#RELEASE Location of external products

# Run "gnumake clean uninstall install" in the application

# top directory each time this file is changed.

 

# If using Debian packages then the following must be done:

#  SUPPORT should be defined to be the root location of any modules which should NOT come from the Debian package.

#  Any modules which should come from the Debian package should be commented out, except for EPICS_BASE.

#  For example to use a newer version of asyn and areaDetector then define ASYN, AREA_DETECTOR, ADCORE,

#  and ADSUPPORT here.  To use the Debian version of asyn then comment out ASYN here.

 

# If you don't want to install into $(TOP) then

# define INSTALL_LOCATION_APP here

#INSTALL_LOCATION_APP=<fullpathname>

 

SUPPORT=/usr/local/CXLS_SW/EPICS_NEW/synApps_6_1/support

 

# ASYN is needed for base classes

ASYN=$(SUPPORT)/asyn4-37

 

AREA_DETECTOR=$(SUPPORT)/areaDetector

 

# ADSupport is needed by ADCore plugins

ADSUPPORT=$(AREA_DETECTOR)/ADSupport

 

# ADCORE for base classes and plugins

ADCORE=$(AREA_DETECTOR)/ADCore

 

EPICS_BASE=/usr/local/CXLS_SW/EPICS_NEW/base-3.15.6

 

# If CONFIG_SITE.local defines WITH_PVA=YES and EPICS_BASE is prior to 7.0 then define the path here

# If using EPICS_BASE 7.0 or later the PVA files are in base itself and no additional definitions are needed.

#PVA=/corvette/usr/local/epics-devel/epicsV4/EPICS-CPP-4.6.0

 

# PVA modules

# For versions prior to EPICS base 7.0 use this

#PVCOMMON=$(PVA)/pvCommonCPP

#PVACCESS=$(PVA)/pvAccessCPP

#PVDATA=$(PVA)/pvDataCPP

#PVDATABASE=$(PVA)/pvDatabaseCPP

#NORMATIVETYPES=$(PVA)/normativeTypesCPP

 

-include $(AREA_DETECTOR)/configure/RELEASE_LIBS.local.$(EPICS_HOST_ARCH)

_______________________________________________________________

 

The following is RELEASE_PRODS.local

_______________________________________________________________

 

 

#RELEASE Location of external products

# Run "gnumake clean uninstall install" in the application

# top directory each time this file is changed.

 

# If using Debian packages then the following must be done:

#  SUPPORT should be defined to be the root location of any modules which should NOT come from the Debian package.

#  Any modules which should come from the Debian package should be commented out, except for EPICS_BASE.

#  For example to use a newer version of asyn and areaDetector then define ASYN, AREA_DETECTOR, ADCORE,

#  and ADSUPPORT here, but comment out AUTOSAVE, BUSY, etc.

 

# If you don't want to install into $(TOP) then

# define INSTALL_LOCATION_APP here

#INSTALL_LOCATION_APP=<fullpathname>

 

SUPPORT=/usr/local/CXLS_SW/EPICS_NEW/synApps_6_1/support

 

# ASYN is needed for base classes

ASYN=$(SUPPORT)/asyn4-37

 

AREA_DETECTOR=$(SUPPORT)/areaDetector

 

# ADSupport is needed by ADCore plugins

ADSUPPORT=$(AREA_DETECTOR)/ADSupport

 

# ADCORE for base classes and plugins

ADCORE=$(AREA_DETECTOR)/ADCore

 

#AUTOSAVE is needed for save_restore

AUTOSAVE=$(SUPPORT)/autosave-R5-10

 

# BUSY is needed for busy record

BUSY=$(SUPPORT)/busy-R1-7-2

 

# CALC is needed for the sseq record that is used for the reset in NDStats.template

# and which is loaded into the example IOCs for general purpose use.

# CALC is also needed for scalcout record that SSCAN uses

CALC=$(SUPPORT)/calc-R3-7-3

 

# SNCSEQ is needed if CALC was built with SNCSEQ support (see CALC/configure/RELEASE)

SNCSEQ=$(SUPPORT)/seq-2-2-6

 

# SSCAN is needed for scanning threshold on Pilatus and general scanning.

# SSCAN also provides support needed for the swait record in CALC

SSCAN=$(SUPPORT)/sscan-R2-11-3

 

# Optional modules

 

# DEVIOCSTATS is used to monitor IOC resources

#DEVIOCSTATS=$(SUPPORT)/devIocStats-3-1-16

 

# ALIVE is used to send IOC status info to a central server

#ALIVE=$(SUPPORT)/alive-1-0-1

 

# ADPLUGINEDGE is optional plugin

#ADPLUGINEDGE=$(AREA_DETECTOR)/ADPluginEdge

 

EPICS_BASE=/usr/local/CXLS_SW/EPICS_NEW/base-3.15.6

 

# If CONFIG_SITE.local defines WITH_PVA=YES and EPICS_BASE is prior to 7.0 then define the path here

# If using EPICS_BASE 7.0 or later the PVA files are in base itself and no additional definitions are needed.

#PVA=/corvette/usr/local/epics-devel/epicsV4/EPICS-CPP-4.6.0

 

# PVA modules

# For versions prior to EPICS base 7.0 use this

#PVCOMMON=$(PVA)/pvCommonCPP

#PVACCESS=$(PVA)/pvAccessCPP

#PVDATA=$(PVA)/pvDataCPP

#PVDATABASE=$(PVA)/pvDatabaseCPP

#NORMATIVETYPES=$(PVA)/normativeTypesCPP

 

-include $(AREA_DETECTOR)/configure/RELEASE_PRODS.local.$(EPICS_HOST_ARCH)

____________________________________________________________

 

 

This is outcomes of 'make'

____________________________________________________________

 

[root@b support]# make clean uninstall

configure/CONFIG:18: /configure/CONFIG: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

/bin/sh: /utils/depends.pl: No such file or directory

configure/RULES_TOP:2: /configure/RULES_TOP: No such file or directory

make: *** No rule to make target `/configure/RULES_TOP'.  Stop.

 

 

 

[root@b areaDetector]# make clean uninstall

configure/CONFIG:17: /configure/CONFIG: No such file or directory

configure/RULES_TOP:2: /configure/RULES_TOP: No such file or directory

configure/RULES_TOP:2: /configure/RULES_TOP: No such file or directory

make: *** No rule to make target `/configure/RULES_TOP'.  Stop.

____________________________________________

 

 

Thanks,

Jong Woo

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Tuesday, February 25, 2020 5:13 PM
To: Jong Woo Kim <Jong.Woo.Kim at asu.edu>
Cc: tech-talk <tech-talk at aps.anl.gov>
Subject: RE: error in 'make' during installation of areaDetector

 

Hi Jong Woo,

 

Ø  After modification of configure files, I ran 'make'. But the following message came out. 

 

Did you modify the following files in areaDetector/configure:

RELEASE_LIBS.local (to set paths to base, SUPPORT, asyn, etc.)

RELEASE_PRODS.local (to set paths to base, SUPPORT, asyn, etc.)

CONFIG_SITE.local (to change build options)

RELEASE.local (to control what gets built)

 

What directory were you in when you typed “make”?  You should be in the top-level areaDetector directory.

 

Please send the complete output of “make” and your RELEASE_LIBS.local and RELEASE_PRODS.local files.

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Jong Woo Kim via Tech-talk
Sent: Tuesday, February 25, 2020 6:01 PM
To: tech-talk at aps.anl.gov
Subject: error in 'make' during installation of areaDetector

 

Hello,

 

Via 'git clone', I installed 'areaDetector' under [synApps_6_1/support], and 'ADCore', 'ADsupport' and 'ADEiger' below it.

After modification of configure files, I ran 'make'. But the following message came out. 

_________________________________________________________

configure/CONFIG:17: /configure/CONFIG: No such file or directory

configure/RULES_TOP:2: /configure/RULES_TOP: No such file or directory

configure/RULES_TOP:2: /configure/RULES_TOP: No such file or directory

make: *** No rule to make target `/configure/RULES_TOP'.  Stop.

_________________________________________________________

 

It would be appreciated, if you give me a feedback.

 

Best,

Jong Woo

 

 


Replies:
Re: error in 'make' during installation of areaDetector Mark Rivers via Tech-talk
References:
error in 'make' during installation of areaDetector Jong Woo Kim via Tech-talk
RE: error in 'make' during installation of areaDetector Mark Rivers via Tech-talk
Re: error in 'make' during installation of areaDetector Jong Woo Kim via Tech-talk

Navigate by Date:
Prev: Re: error in 'make' during installation of areaDetector Jong Woo Kim via Tech-talk
Next: Re: error in 'make' during installation of areaDetector Mark Rivers 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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: error in 'make' during installation of areaDetector Jong Woo Kim via Tech-talk
Next: Re: error in 'make' during installation of areaDetector Mark Rivers 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  <20202021  2022  2023  2024 
ANJ, 25 Feb 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·