[Pkg-scicomp-devel] Bug#577338: arpack++: FTBFS: make[1]: *** No rule to make target `default'. Stop.

Lucas Nussbaum lucas at lucas-nussbaum.net
Sun Apr 11 08:02:15 UTC 2010


Source: arpack++
Version: 2.3-1
Severity: serious
Tags: squeeze sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20100410 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> test -x debian/rules
> dh_testroot
> rmdir ./
> rmdir: failed to remove `./': Invalid argument
> make: [cleanbuilddir] Error 1 (ignored)
> rm -f debian/stamp-makefile-build debian/stamp-makefile-install
> /usr/bin/make  -C ./  -k distclean
> make[1]: *** No rule to make target `distclean'.make[1]: Entering directory `/build/user-arpack++_2.3-1-amd64-3vSqQ9/arpack++-2.3'
> 
> make[1]: Leaving directory `/build/user-arpack++_2.3-1-amd64-3vSqQ9/arpack++-2.3'
> make: [makefile-clean] Error 2 (ignored)
> rm -f debian/stamp-autotools
> rmdir --ignore-fail-on-non-empty ./
> rmdir: failed to remove `./': Invalid argument
> make: [makefile-clean] Error 1 (ignored)
> for i in ./config.guess ./config.sub  ; do \
> 		if test -e $i.cdbs-orig ; then \
> 			mv $i.cdbs-orig $i ; \
> 		fi ; \
> 	done
> rm -f debian/stamp-autotools-files
> dh_clean 
> dh_clean: Compatibility levels before 5 are deprecated.
>  dpkg-source -b arpack++-2.3
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building arpack++ using existing arpack++_2.3.orig.tar.gz
> dpkg-source: info: building arpack++ in arpack++_2.3-1.diff.gz
> dpkg-source: info: building arpack++ in arpack++_2.3-1.dsc
>  debian/rules build
> test -x debian/rules
> mkdir -p "./"
> echo 5 >debian/compat
> if test -e /usr/share/misc/config.guess ; then \
> 		for i in ./config.guess ; do \
> 			if ! test -e $i.cdbs-orig ; then \
> 				mv $i $i.cdbs-orig ; \
> 				cp --remove-destination /usr/share/misc/config.guess $i ; \
> 			fi ; \
> 		done ; \
> 	fi
> if test -e /usr/share/misc/config.sub ; then \
> 		for i in ./config.sub ; do \
> 			if ! test -e $i.cdbs-orig ; then \
> 				mv $i $i.cdbs-orig ; \
> 				cp --remove-destination /usr/share/misc/config.sub $i ; \
> 			fi ; \
> 		done ; \
> 	fi
> touch debian/stamp-autotools-files
> chmod a+x /build/user-arpack++_2.3-1-amd64-3vSqQ9/arpack++-2.3/configure
> mkdir -p ./
> cd ./ && CC="cc" CXX="g++" CFLAGS="-O3" CXXFLAGS="-O3" CPPFLAGS="" LDFLAGS="" /build/user-arpack++_2.3-1-amd64-3vSqQ9/arpack++-2.3/configure --build=x86_64-linux-gnu  --prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/arpack++" --disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules   --host=x86_64-linux-gnu --build=x86_64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --includedir=/usr/include/arpack++ 
> 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... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> 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 g++ accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of g++... none
> checking for x86_64-linux-gnu-gcc... cc
> checking whether we are using the GNU C compiler... yes
> checking whether cc accepts -g... yes
> checking for cc option to accept ISO C89... none needed
> checking dependency style of cc... none
> checking for log in -lm... yes
> checking for daxpy_ in -lblas... yes
> checking for dgemm_ in -llapack... yes
> checking for dnaupd_ in -larpack... yes
> checking how to run the C preprocessor... cc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking malloc.h usability... yes
> checking malloc.h presence... yes
> checking for malloc.h... yes
> checking for stdlib.h... (cached) yes
> checking for string.h... (cached) yes
> checking for stdbool.h that conforms to C99... yes
> checking for _Bool... yes
> checking for an ANSI C-conforming const... yes
> checking for inline... inline
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for ld used by cc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognize dependent libraries... pass_all
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for x86_64-linux-gnu-g77... no
> checking for x86_64-linux-gnu-xlf... no
> checking for x86_64-linux-gnu-f77... no
> checking for x86_64-linux-gnu-frt... no
> checking for x86_64-linux-gnu-pgf77... no
> checking for x86_64-linux-gnu-cf77... no
> checking for x86_64-linux-gnu-fort77... no
> checking for x86_64-linux-gnu-fl32... no
> checking for x86_64-linux-gnu-af77... no
> checking for x86_64-linux-gnu-xlf90... no
> checking for x86_64-linux-gnu-f90... no
> checking for x86_64-linux-gnu-pgf90... no
> checking for x86_64-linux-gnu-pghpf... no
> checking for x86_64-linux-gnu-epcf90... no
> checking for x86_64-linux-gnu-gfortran... x86_64-linux-gnu-gfortran
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether x86_64-linux-gnu-gfortran accepts -g... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking command to parse /usr/bin/nm -B output from cc object... ok
> checking for objdir... .libs
> checking for x86_64-linux-gnu-ar... no
> checking for ar... ar
> checking for x86_64-linux-gnu-ranlib... no
> checking for ranlib... ranlib
> checking for x86_64-linux-gnu-strip... no
> checking for strip... strip
> checking if cc supports -fno-rtti -fno-exceptions... no
> checking for cc option to produce PIC... -fPIC
> checking if cc PIC flag -fPIC works... yes
> checking if cc static flag -static works... yes
> checking if cc supports -c -o file.o... yes
> checking whether the cc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/bin/ld -m elf_x86_64
> checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ static flag -static works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> (cached) (cached) checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to libtool
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for x86_64-linux-gnu-gfortran option to produce PIC... -fPIC
> checking if x86_64-linux-gnu-gfortran PIC flag -fPIC works... yes
> checking if x86_64-linux-gnu-gfortran static flag -static works... yes
> checking if x86_64-linux-gnu-gfortran supports -c -o file.o... yes
> checking whether the x86_64-linux-gnu-gfortran linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> (cached) (cached) checking how to hardcode library paths into programs... immediate
> checking for sqrt... yes
> checking for strchr... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating include/Makefile
> config.status: creating src/Makefile
> config.status: creating examples/Makefile
> config.status: creating examples/matrices/Makefile
> config.status: creating examples/matrices/sym/Makefile
> config.status: creating examples/matrices/nonsym/Makefile
> config.status: creating examples/matrices/complex/Makefile
> config.status: creating examples/matprod/Makefile
> config.status: creating examples/matprod/sym/Makefile
> config.status: creating examples/matprod/nonsym/Makefile
> config.status: creating examples/matprod/complex/Makefile
> config.status: creating examples/reverse/Makefile
> config.status: creating examples/reverse/sym/Makefile
> config.status: creating examples/reverse/nonsym/Makefile
> config.status: creating examples/reverse/complex/Makefile
> config.status: creating examples/band/Makefile
> config.status: creating examples/band/sym/Makefile
> config.status: creating examples/band/nonsym/Makefile
> config.status: creating examples/band/complex/Makefile
> config.status: creating examples/dense/Makefile
> config.status: creating examples/dense/sym/Makefile
> config.status: creating examples/dense/nonsym/Makefile
> config.status: creating examples/dense/complex/Makefile
> config.status: creating examples/product/Makefile
> config.status: creating examples/product/simple/Makefile
> config.status: creating examples/product/sym/Makefile
> config.status: creating examples/product/nonsym/Makefile
> config.status: creating examples/product/complex/Makefile
> config.status: creating config.h
> config.status: executing depfiles commands
> touch debian/stamp-autotools
> /usr/bin/make  -C ./  default
> make[1]: *** No rule to make target `default'.  Stop.
> make[1]: Entering directory `/build/user-arpack++_2.3-1-amd64-3vSqQ9/arpack++-2.3'
> make[1]: Leaving directory `/build/user-arpack++_2.3-1-amd64-3vSqQ9/arpack++-2.3'
> make: *** [debian/stamp-makefile-build] Error 2

The full build log is available from:
   http://people.debian.org/~lucas/logs/2010/04/10/arpack++_2.3-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lucas at lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr             GPG: 1024D/023B3F4F |





More information about the Pkg-scicomp-devel mailing list