[Lsb-messages] Build failure for python-test on ia32

lsb-autobuild at freestandards.org lsb-autobuild at freestandards.org
Sun Apr 26 01:08:14 PDT 2009


This is an automated message generated when a build failure occurs

Linux lfdev-ia32 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 i686 i386 GNU/Linux
Failed to make packages for python-test
sed -e "s#@PVER4@#`echo 2.4.2`#" -e "s#@PVER5@#`echo 2.5`#" -e "s#@VERSION@#`echo 4.0.1`#" -e "s#@RELEASE@#`echo 2`#" < lsb-test-python.spec.sed > lsb-test-python.spec
bzr export python-test-4.0.1.tar.gz /nethome/autobuild/tmp/LSBauto/python-test	
bzr cat /nethome/autobuild/tmp/LSBauto/misc-test/tetj/tetj.py > tetj.py
spawn rpmbuild --sign --rcfile /usr/lib/rpm/rpmrc:./rpmrc --define=_sourcedir /nethome/autobuild/tmp/LSBauto/python-test/scripts/package --define=_topdir /nethome/autobuild/tmp/rpm-build --define=_target_cpu i486 -ba lsb-test-python.spec
Enter pass phrase: 
Pass phrase is good.
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.90275
+ umask 022
+ cd /nethome/autobuild/tmp/rpm-build/BUILD
+ cd /nethome/autobuild/tmp/rpm-build/BUILD
+ rm -rf lsb-test-python-4.0.1
+ /bin/mkdir -p lsb-test-python-4.0.1
+ cd lsb-test-python-4.0.1
+ /usr/bin/bzip2 -dc /nethome/autobuild/tmp/LSBauto/python-test/scripts/package/Python-2.4.2.tar.bz2
+ tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ /usr/bin/bzip2 -dc /nethome/autobuild/tmp/LSBauto/python-test/scripts/package/Python-2.5.tar.bz2
+ tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ /usr/bin/gzip -dc /nethome/autobuild/tmp/LSBauto/python-test/scripts/package/python-test-4.0.1.tar.gz
+ tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ echo 'Patch #1 (python-tet-test.patch):'
Patch #1 (python-tet-test.patch):
+ patch -p0 -b --suffix .tet-output -s
+ pushd Python-2.4.2/Lib/test
~/tmp/rpm-build/BUILD/lsb-test-python-4.0.1/Python-2.4.2/Lib/test ~/tmp/rpm-build/BUILD/lsb-test-python-4.0.1
+ echo 'Patch #0 (python-system-python.patch):'
Patch #0 (python-system-python.patch):
+ patch -p0 -b --suffix .system-python -s
+ popd
~/tmp/rpm-build/BUILD/lsb-test-python-4.0.1
+ echo 'Patch #2 (python-test-new-behavior.patch):'
Patch #2 (python-test-new-behavior.patch):
+ patch -p0 -b --suffix .new-behavior -s
+ echo 'Patch #3 (python-test-private-testcapi.patch):'
Patch #3 (python-test-private-testcapi.patch):
+ patch -p0 -b --suffix .testcapi -s
+ pushd Python-2.5/Lib/test
~/tmp/rpm-build/BUILD/lsb-test-python-4.0.1/Python-2.5/Lib/test ~/tmp/rpm-build/BUILD/lsb-test-python-4.0.1
+ echo 'Patch #4 (python-test-handle-26.patch):'
Patch #4 (python-test-handle-26.patch):
+ patch -p0 -b --suffix .26 -s
+ popd
~/tmp/rpm-build/BUILD/lsb-test-python-4.0.1
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.12516
+ umask 022
+ cd /nethome/autobuild/tmp/rpm-build/BUILD
+ cd lsb-test-python-4.0.1
+ for pyver in 2.4.2 2.5
+ cd Python-2.4.2
+ CC=lsbcc
+ CXX=lsbc++
+ ./configure --enable-unicode=ucs4
checking MACHDEP... linux2
checking EXTRAPLATDIR... 
checking for --without-gcc... no
checking for --with-cxx=<compiler>... no
checking for c++... lsbc++
checking for C++ compiler default output file name... configure: error: C++ compiler cannot create executables
See `config.log' for more details.
error: Bad exit status from /var/tmp/rpm-tmp.12516 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.12516 (%build)
expect: spawn id exp3 not open
    while executing
"expect "exit 0""
send: spawn id exp3 not open
    while executing
"send "\n""
mv: cannot stat `/nethome/autobuild/tmp/rpm-build/SRPMS/lsb-test-python-4.0.1-2.src.rpm': No such file or directory
make: *** [lsb-test-python-4.0.1-2.i486.rpm] Error 1


More information about the lsb-messages mailing list