sdpa version 7.3.5.dfsg-1build1 FTBFS on i386 in precise

Bug #935439 reported by Andreas Moog
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sdpa (Ubuntu)
Fix Released
High
Unassigned
Precise
Fix Released
High
Unassigned

Bug Description

This is a semi-automatic report based on the latest archive rebuild results [1].
Apologies if it reaches you in error.

Excerpt from the buildlog:

ar cru libsdpa.a libsdpa_a-sdpa_block.o libsdpa_a-sdpa_call.o libsdpa_a-sdpa_chordal.o libsdpa_a-sdpa_dataset.o libsdpa_a-sdpa_dpotrf.o libsdpa_a-sdpa_io.o libsdpa_a-sdpa_jordan.o libsdpa_a-sdpa_linear.o libsdpa_a-sdpa_newton.o libsdpa_a-sdpa_parts.o libsdpa_a-sdpa_solve.o libsdpa_a-sdpa_struct.o libsdpa_a-sdpa_tool.o
ranlib libsdpa.a
g++ -DPACKAGE_NAME=\"sdpa\" -DPACKAGE_TARNAME=\"sdpa\" -DPACKAGE_VERSION=\"7.3.5\" -DPACKAGE_STRING=\"sdpa\ 7.3.5\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"sdpa\" -DVERSION=\"7.3.5\" -DFC_FUNC\(name,NAME\)=name\ ##\ _ -DFC_FUNC_\(name,NAME\)=name\ ##\ _ -I. -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -D_REENTRANT -Wall -fPIC -funroll-all-loops -c -o sdpa-sdpa_exe.o `test -f 'sdpa_exe.cpp' || echo './'`sdpa_exe.cpp
g++ -I/usr/include -I/usr/include -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security -Wall -D_REENTRANT -Wall -fPIC -funroll-all-loops -Wl,-Bsymbolic-functions -Wl,-z,relro -o sdpa sdpa-sdpa_exe.o -L. -lsdpa -ldmumps_seq /usr/lib/atlas-base/atlas/liblapack.a /usr/lib/atlas-base/atlas/libblas.a -lpthread -L/usr/lib/gcc/i686-linux-gnu/4.6 -L/usr/lib/gcc/i686-linux-gnu/4.6/../../../i386-linux-gnu -L/usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib -L/lib/i386-linux-gnu -L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.6/../../.. -lgfortran -lm -lquadmath
make[2]: Leaving directory `/build/buildd/sdpa-7.3.5.dfsg'
make[1]: Leaving directory `/build/buildd/sdpa-7.3.5.dfsg'
touch debian/stamp-makefile-build
DEB_MAKE_CHECK_TARGET unset, not running checks
cd /build/buildd/sdpa-7.3.5.dfsg/mex && \
 make \
   MAKE_INCLUDE_DIR=../etc COMPILE_ENVIRONMENT=octave \
   ALL_INCLUDE=-I../ SDPA_LIB=../libsdpa.a
make[1]: Entering directory `/build/buildd/sdpa-7.3.5.dfsg/mex'
mkoctfile --mex -DPRINTF_INT_STYLE=\\\"%d\\\" \
    \
   -I../ \
   mexsdpa.cpp mexFprintf.c \
    ../libsdpa.a -ldmumps_seq /usr/lib/atlas-base/atlas/liblapack.a /usr/lib/atlas-base/atlas/libblas.a -lpthread -L/usr/lib/gcc/i686-linux-gnu/4.6 -L/usr/lib/gcc/i686-linux-gnu/4.6/../../../i386-linux-gnu -L/usr/lib/gcc/i686-linux-gnu/4.6/../../../../lib -L/lib/i386-linux-gnu -L/lib/../lib -L/usr/lib/i386-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.6/../../.. -lgfortran -lm -lquadmath
cc1: error: -I.: --param arguments should be of the form NAME=VALUE
make[1]: *** [mexsdpa] Error 1
make[1]: Leaving directory `/build/buildd/sdpa-7.3.5.dfsg/mex'
make: *** [build/sdpam] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20120211-0252
FAILED [dpkg-buildpackage died]

The full buidlog can be found at https://launchpad.net/ubuntu/+archive/test-rebuild-20120201/+build/3170764/+files/buildlog_ubuntu-precise-i386.sdpa_7.3.5.dfsg-1build1_FAILEDTOBUILD.txt.gz.

[1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120201-precise.html

Tags: ftbfs precise
Andreas Moog (ampelbein)
Changed in sdpa (Ubuntu):
importance: Undecided → High
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

fixed in later releases

Changed in sdpa (Ubuntu Precise):
status: New → Fix Released
Changed in sdpa (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.