EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: Build failed in Jenkins: epics-pvaPy-linux32 #970
From: APS Jenkins via Core-talk <core-talk at aps.anl.gov>
To: core-talk at aps.anl.gov
Date: Fri, 28 Jan 2022 19:47:27 -0600 (CST)
See <https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/970/display/redirect?page=changes>

Changes:

[Veseli, Sinisa] distutils are being deprecated

[Veseli, Sinisa] save epics/boost build for osx


------------------------------------------
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on linux32-1 (linux32) in workspace <https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/ws/>
The recommended git tool is: NONE
No credentials specified
 > git rev-parse --resolve-git-dir <https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/ws/.git> # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/epics-base/pvaPy.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from https://github.com/epics-base/pvaPy.git
 > git --version # timeout=10
 > git --version # 'git version 1.7.1'
Setting http proxy: webproxy1.anl.gov:9091
 > git fetch --tags --progress https://github.com/epics-base/pvaPy.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 4eed89b8a5859ae5742682aa3fccc6c6376a57ae (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4eed89b8a5859ae5742682aa3fccc6c6376a57ae # timeout=10
Commit message: "save epics/boost build for osx"
 > git rev-list --no-walk 7b4cf78cfd72c510435e6ce3d000c1fd6f93c370 # timeout=10
[epics-pvaPy-linux32] $ /bin/sh -xe /tmp/jenkins140962067452505742.sh
+ rm -rf epics
+ mkdir -p epics
+ ln -s /local/jenkins/workspace/epics-base-3.16-linux32 epics/base
+ ln -s /local/jenkins/workspace/epics-pvCommon-linux32 epics/pvCommonCPP
+ ln -s /local/jenkins/workspace/epics-pvData-linux32 epics/pvDataCPP
+ ln -s /local/jenkins/workspace/epics-normativeTypes-linux32 epics/normativeTypesCPP
+ ln -s /local/jenkins/workspace/epics-pvAccess-linux32 epics/pvAccessCPP
+ ln -s /local/jenkins/workspace/epics-pvaClient-linux32 epics/pvaClientCPP
+ ln -s /local/jenkins/workspace/epics-pvDatabase-linux32 epics/pvDatabaseCPP
+ EPICS_BASE=<https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/ws/epics/base>
+ EPICS4_DIR=<https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/ws/epics>
+ make configure
autoreconf --install tools/autoconf
configure.ac:2: installing `./install-sh'
configure.ac:2: installing `./missing'
tools/autoconf/configure --with-top=.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
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 ISO C89... none needed
checking dependency style of gcc... none
checking for python... /usr/bin/python
checking for a version of Python >= '2.1.0'... yes
checking for Python include path... Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named sysconfig
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named sysconfig

checking for Python library path... Traceback (most recent call last):
  File "<stdin>", line 4, in <module>
ImportError: No module named sysconfig
Traceback (most recent call last):
  File "<stdin>", line 3, in <module>
ImportError: No module named sysconfig
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
ImportError: No module named sysconfig
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named sysconfig
-L -lpython2.6
checking for Python site-packages path... Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named sysconfig

checking python extra libraries... Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named sysconfig

checking python extra linking flags... Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named sysconfig

checking consistency of all components of python development environment... no
configure: error: in `<https://jenkins.aps.anl.gov/job/epics-pvaPy-linux32/ws/'>:
configure: error:
  Could not link test program to Python. Maybe the main Python library has been
  installed in some non-standard library path. If so, pass it to configure,
  via the LDFLAGS environment variable.
  Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib"
  ============================================================================
   ERROR!
   You probably have to install the development version of the Python package
   for your distribution.  The exact name of this package varies among them.
  ============================================================================

See `config.log' for more details.
Makefile:53: recipe for target 'configure' failed
make: *** [configure] Error 1
Build step 'Execute shell' marked build as failure

Replies:
Jenkins build is back to normal : epics-pvaPy-linux32 #971 APS Jenkins via Core-talk

Navigate by Date:
Prev: [Bug 1959457] [NEW] pvget/pvput for aai/aao record types, with data type=enum, wrong results Jerzy Tarasiuk via Core-talk
Next: Jenkins build is back to normal : epics-pvaPy-linux32 #971 APS Jenkins via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
Navigate by Thread:
Prev: [Bug 1959457] [NEW] pvget/pvput for aai/aao record types, with data type=enum, wrong results Jerzy Tarasiuk via Core-talk
Next: Jenkins build is back to normal : epics-pvaPy-linux32 #971 APS Jenkins via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
ANJ, 14 Sep 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·