Your message dated Mon, 10 Aug 2009 12:18:05 -0400 (EDT)
with message-id <alpine.deb.1.10.0908101215160.7...@vinegar-pot.mit.edu>
and subject line This bug is fixed in version 3.2.13-1
has caused the Debian Bug report #526585,
regarding givaro: FTBFS: libtool errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
526585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: givaro
Version: 3.2.10-1
Severity: serious
From my pbuilder build log:
...
Making all in system
make[5]: Entering directory `/tmp/buildd/givaro-3.2.10/src/kernel/system'
/bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
-I../../.. -I../../.. -I../../../src/kernel/memory -g -O2 -g -Wall -O2 -c -o
givbasictype.lo givbasictype.C
../../../libtool: line 841: X--tag=CXX: command not found
../../../libtool: line 874: libtool: ignoring unknown tag : command not found
../../../libtool: line 841: X--mode=compile: command not found
../../../libtool: line 1008: *** Warning: inferring the mode of operation is
deprecated.: command not found
../../../libtool: line 1009: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
../../../libtool: line 1152: Xg++: command not found
../../../libtool: line 1152: X-DHAVE_CONFIG_H: command not found
../../../libtool: line 1152: X-I.: command not found
../../../libtool: line 1152: X-I../../..: No such file or directory
../../../libtool: line 1152: X-I../../..: No such file or directory
../../../libtool: line 1152: X-I../../../src/kernel/memory: No such file or
directory
../../../libtool: line 1152: X-g: command not found
../../../libtool: line 1152: X-O2: command not found
../../../libtool: line 1152: X-g: command not found
../../../libtool: line 1152: X-Wall: command not found
../../../libtool: line 1152: X-O2: command not found
../../../libtool: line 1152: X-c: command not found
../../../libtool: line 1205: Xgivbasictype.lo: command not found
../../../libtool: line 1210: libtool: compile: cannot determine name of library
object from `': command not found
make[5]: *** [givbasictype.lo] Error 1
make[5]: Leaving directory `/tmp/buildd/givaro-3.2.10/src/kernel/system'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/tmp/buildd/givaro-3.2.10/src/kernel'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/tmp/buildd/givaro-3.2.10/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/givaro-3.2.10'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/givaro-3.2.10'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
Version 3.2.13 of Givaro contains a libtool update that fixed this build
failure (I forgot to include the bug closer in the changelog itself).
-Tim Abbott
--- End Message ---
