RE: Error building EPICS V4 "pvaPy" : RpcClient.cpp:82: error: 'response' was not declared in this scope

["Williams Jr., Ernest L." <ernesto@slac.stanford.edu>]

Hi Sinisa,

Thanks for your help.

By the way,  using CONFIG_SITE.local does work.


I had a typo in there :(

So, no need to modify the source Makefile.

=== My CONFIG_SITE.local ==================================================

PACKAGE_AREA=/afs/slac/g/lcls/package
PYTHON_DIR=$(PACKAGE_AREA)/python/current
BOOST_DIR=$(PACKAGE_AREA)/boost/1.58.0/linux-x86

EPICS_HOST_ARCH=linux-x86
BOOST_PYTHON_LIB=boost_python

PVA_PY_CPPFLAGS=-DPVA_API_VERSION=440 -DPVA_RPC_API_VERSION=440 \
 -I$(BOOST_DIR)/include -I$(PYTHON_DIR)/include/python2.7

PVA_PY_LDFLAGS=-L$(BOOST_DIR)/lib -L$(PYTHON_DIR)/lib -lpython2.7
========================================================================

Now, we start testing :)

Cheers,
Ernest



________________________________________
From: Williams Jr., Ernest L.
Sent: Wednesday, August 12, 2015 7:27 AM
To: Sinisa Veseli; tech-talk@aps.anl.gov
Cc: Williams Jr., Ernest L.
Subject: RE: Error building EPICS V4 "pvaPy" : RpcClient.cpp:82: error: 'response' was not declared in this scope

________________________________________
From: Sinisa Veseli [sveseli@aps.anl.gov]
Sent: Wednesday, August 12, 2015 6:51 AM
To: Williams Jr., Ernest L.; tech-talk@aps.anl.gov
Subject: Re: Error building EPICS V4 "pvaPy" : RpcClient.cpp:82: error: 'response' was not declared in this scope

Ahh, ok. In this case, you probably used README file example, which
seems to be a bit out of date.

Could you try adding variables below in your CONFIG_SITE.local file, and
let me know what happens.

Sinisa

PVA_API_VERSION=440
PVA_PY_CPPFLAGS=-DPVA_API_VERSION=440 -DPVA_RPC_API_VERSION=440
-I$(BOOST_DIR)/include -I$(PYTHON_TOP)/include/python2.7

=======================================================
Sure, but there was no change.

Actually, I had to add your changes to the source Makefile
that is  "<....>/base-cpp-R4-4-0-pre2/pvaPy/src/pvaccess/Makefile"

Looks like "CONFIG_SITE.local" does not get referenced by the Makefile.

So, I added the following to the Makefile and all is well now :)

====== src/pvaccess/Makefile   snippet =====================

BOOST_DIR=/afs/slac/g/lcls/package/boost/1.58.0/linux-x86
PYTHON_DIR=/afs/slac/g/lcls/package/python/current

LOADABLE_LIBRARY_HOST += pvaccess
LOADABLE_SHRLIB_PREFIX =

#PROD_HOST_linux-x86_64 += testClient
PROD_HOST += $(PROD_HOST_$(T_A))


PVA_API_VERSION=440
PVA_RPC_API_VERSION=440
PVA_PY_CPPFLAGS=-DPVA_API_VERSION=440 -DPVA_RPC_API_VERSION=440
CXXFLAGS += $(PVA_PY_CPPFLAGS)
CXXFLAGS += -g -I$(BOOST_DIR)/include -I/$(PYTHON_DIR)/include/python2.7
LDFLAGS += $(PVA_PY_LDFLAGS)
=================================================================


Compile is now successful:


/usr/bin/g++ -c  -D_POSIX_C_SOURCE=199506L -D_POSIX_THREADS -D_XOPEN_SOURCE=500           -D_X86_  -DUNIX  -D_BSD_SOURCE -Dlinux  -D_REENTRANT   -O3   -Wall      -m32     -g -fPIC -MMD -DPVA_API_VERSION=440 -DPVA_RPC_API_VERSION=440 -g -I/afs/slac/g/lcls/package/boost/1.58.0/linux-x86/include -I//afs/slac/g/lcls/package/python/current/include/python2.7 -I. -I../O.Common -I. -I.. -I../../../include/os/Linux -I../../../include   -I/afs/slac/g/lcls/epics/base/base-R3-14-12/include/os/Linux -I/afs/slac/g/lcls/epics/base/base-R3-14-12/include  -I/afs/slac/g/lcls/epics/base/base-cpp-R4-4-0-pre2/pvDataCPP/include  -I/afs/slac/g/lcls/epics/base/base-cpp-R4-4-0-pre2/pvAccessCPP/include       ../StringUtility.cpp
/usr/bin/g++ -o pvaccess.so -shared -fPIC -Wl,-hpvaccess.so -L/afs/slac/g/lcls/epics/base/base-R3-14-12/lib/linux-x86 -L/afs/slac/g/lcls/epics/base/base-cpp-R4-4-0-pre2/pvAccessCPP/lib/linux-x86 -L/afs/slac/g/lcls/epics/base/base-cpp-R4-4-0-pre2/pvDataCPP/lib/linux-x86 -Wl,-rpath,/afs/slac/g/lcls/epics/base/base-R3-14-12/lib/linux-x86 -Wl,-rpath,/afs/slac/g/lcls/epics/base/base-cpp-R4-4-0-pre2/pvAccessCPP/lib/linux-x86 -Wl,-rpath,/afs/slac/g/lcls/epics/base/base-cpp-R4-4-0-pre2/pvDataCPP/lib/linux-x86       -m32        -L/afs/slac/g/lcls/package/boost/1.58.0/linux-x86/lib -L/python/current/lib -lpython2.7        pvaccess.o CaClient.o Channel.o ChannelGetRequesterImpl.o ChannelMonitorRequesterImpl.o ChannelPutRequesterImpl.o ChannelRequesterImpl.o ChannelTimeout.o FieldNotFound.o GetFieldRequesterImpl.o InvalidArgument.o InvalidDataType.o InvalidRequest.o InvalidState.o NtTable.o NtType.o ObjectNotFound.o PvaClient.o PvaException.o PvaExceptionTranslator.o PvaPyLogger.o PvAla!
 rm.o PvBoolean.o PvByte.o PvDouble.o PvFloat.o PvInt.o PvLong.o PvObject.o PvProvider.o PvScalar.o PvScalarArray.o PvShort.o PvString.o PvTimeStamp.o PvUByte.o PvUInt.o PvULong.o PvUShort.o PvUtility.o PyGilManager.o PyPvDataUtility.o PyUtility.o RequesterImpl.o RpcClient.o RpcServiceImpl.o RpcServer.o RpcTimeout.o StringUtility.o    -lpvData -lpvAccess -lCom  -lboost_python -lpthread   -lreadline -lncurses -lm -lrt -ldl -lgcc
Installing loadable shared library ../../../lib/linux-x86/pvaccess.so
make[1]: Leaving directory `/afs/slac.stanford.edu/g/lcls/vol8/epics/base/base-cpp-R4-4-0-pre2/pvaPy/src/pvaccess/O.linux-x86'


Cheers,
Ernest




On 8/12/15 8:35 AM, Williams Jr., Ernest L. wrote:
> ________________________________________
> From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Sinisa Veseli [sveseli@aps.anl.gov]
> Sent: Wednesday, August 12, 2015 5:27 AM
> To: tech-talk@aps.anl.gov
> Subject: Re: Error building EPICS V4 "pvaPy" : RpcClient.cpp:82: error: 'response' was not declared in this scope
>
> Hi,
>
> Could you please send me the output of the "make configure" step, as
> well as the contents of pvaPy/configure/CONFIG_SITE.local file?
>
> ======
> I created "CONFIG_SITE.local" and "RELEASE.local" manually.
> The dependent packages required by pvaPy are installed from source in our environment.
> We are not using a linux package manager for "boost" and "python"
>
> *************** Output of make configure ********************************************************
>
> [ernesto@lcls-dev2 pvaPy]$ make configure
> cd tools/autoconf && ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking dependency style of gcc... none
> checking for python... /afs/slac/g/lcls/package/python/current/bin/python
> checking for a version of Python >= '2.1.0'... yes
> checking for a version of Python >=2.6... yes
> checking for the distutils Python package... yes
> checking for Python include path... -I/afs/slac/g/lcls/package/python/current/include/python2.7
> checking for Python library path... -L/afs/slac/g/lcls/package/python/Python-2.7.4/lib -lpython2.7
> checking for Python site-packages path... /afs/slac/g/lcls/package/python/current/lib/python2.7/site-packages
> checking python extra libraries... -lpthread -ldl  -lutil
> checking python extra linking flags... -Xlinker -export-dynamic
> checking consistency of all components of python development environment... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... none
> checking for boostlib >= 1.40... configure: We could not detect the boost libraries (version 1.40 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option.  If you are sure you have boost installed, then check your version number looking in <boost/version.hpp>. See http://randspringer.de/boost for more documentation.
> configure: error: required Boost library version >= 1.40.
> make: *** [configure] Error 1
> ******************************************************************************************************************************
>
> **************  Output of CONFIG_SITE.local ****************************************************************************
> [ernesto@lcls-dev2 configure]$ more CONFIG_SITE.local
> PACKAGE_TOP=/afs/slac/g/lcls/package
>
> PYTHON_TOP=$(PACKAGE)/python/current
> BOOST_DIR=$(PACKAGE)/boost/1.58.0/linux-x86
>
> EPICS_HOST_ARCH=linux-x86
> BOOST_PYTHON_LIB=boost_python
> PVA_PY_CPPFLAGS=-I$(BOOST_DIR)/include -I$(PYTHON_TOP)/include/python2.7
> PVA_PY_LDFLAGS=-L$(BOOST_DIR)/lib -L$(PYTHON_TOP)/lib -lpython2.7
> ******************************************************************************************************************************
>
> Cheers,
> Ernest
>
> Thanks,
>
> Sinisa
>
> On 08/12/2015 01:08 AM, Williams Jr., Ernest L. wrote:
>> Hi,
>>
>> I am working with EPICS V4 and would like to build the python support (i.e. "pvaPy")
>>
>> HOST = RHEL5 32-bit,  linux-x86
>>
>> Indeed, I have configured/built the necessary dependent external packages
>> (1) Boost  ==>  1.58.0
>> (2) Python ==> 2.7.4
>>
>> The EPICS V4 release ==> base-cpp-R4-4-0-pre2
>> The EPICS BASE V3 release ==> base-R3-14-12
>>
>> pvaPy"
>> All of the V4 modules build nicely, except that I have the following problem with "pvaPy"
>>
>> Any help or solutions, appreciated:
>> ../RpcClient.cpp:82: error: 'response' was not declared in this scope
>> ======================= Compile Error Below ============================================
>>
>> /usr/bin/g++ -c  -D_POSIX_C_SOURCE=199506L -D_POSIX_THREADS -D_XOPEN_SOURCE=500           -D_X86_  -DUNIX  -D_BSD_SOURCE -Dlinux  -D_REENTRANT   -O3   -Wall      -m32     -g -fPIC -MMD -g -I/afs/slac/g/lcls/package/boost/1.58.0/linux-x86/include -I//afs/slac/g/lcls/package/python/current/include/python2.7 -I. -I../O.Common -I. -I.. -I../../../include/os/Linux -I../../../include   -I/afs/slac/g/lcls/epics/base/base-R3-14-12/include/os/Linux -I/afs/slac/g/lcls/epics/base/base-R3-14-12/include  -I/afs/slac/g/lcls/epics/base/base-cpp-R4-4-0-pre2/pvDataCPP/include  -I/afs/slac/g/lcls/epics/base/base-cpp-R4-4-0-pre2/pvAccessCPP/include       ../RpcClient.cpp
>> ../RpcClient.cpp: In static member function 'static std::tr1::shared_ptr<epics::pvAccess::RPCClient> RpcClient::createRpcClient(const std::string&, const epics::pvData::PVStructurePtr&, double)':
>> ../RpcClient.cpp:53: warning: no return statement in function returning non-void
>> ../RpcClient.cpp: In member function 'virtual std::tr1::shared_ptr<epics::pvData::PVStructure> RpcClient::request(const epics::pvData::PVStructurePtr&, double)':
>> ../RpcClient.cpp:82: error: 'response' was not declared in this scope
>> make[1]: *** [RpcClient.o] Error 1
>> make[1]: Leaving directory `/afs/slac.stanford.edu/g/lcls/vol8/epics/base/base-cpp-R4-4-0-pre2/pvaPy/src/pvaccess/O.linux-x86'
>> make: *** [install.linux-x86] Error 2
> --
> Sinisa Veseli
> Software Services Group
> APS Engineering Support Division
> Argonne National Laboratory
> sveseli@anl.gov
> (630)252-9182
>

--
Siniša Veseli
Scientific Software Engineering & Data Management
Advanced Photon Source
Argonne National Laboratory
sveseli@anl.gov
(630)252-9182