Your message dated Sun, 15 Jan 2012 11:26:27 +0100
with message-id <20120115102627.gg9...@radis.cristau.org>
and subject line Re: Bug#640703: Bug#640702: libqalculate: FTBFS: libtool:
link: `/usr/lib/libgmp.la' is not a valid libtool archive
has caused the Debian Bug report #640703,
regarding linbox: FTBFS: libtool: link: `/usr/lib/libgmp.la' is not a valid
libtool archive
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.)
--
640703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linbox
Version: 1.1.6~rc0-4.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20110902 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> libtool: link: g++ -fPIC -DPIC -shared -nostdlib
> /usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../../x86_64-linux-gnu/crti.o
> /usr/lib/gcc/x86_64-linux-gnu/4.6.1/crtbeginS.o .libs/linbox-sage.o -lntl
> /usr/lib/libgivaro.so -llapack -lcblas -latlas
> /usr/lib/x86_64-linux-gnu/libgmp.so /usr/lib/x86_64-linux-gnu/libgmpxx.so
> -L/usr/lib/gcc/x86_64-linux-gnu/4.6.1
> -L/usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../../x86_64-linux-gnu
> -L/usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../../../lib -L/lib/x86_64-linux-gnu
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib
> -L/usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../.. -lstdc++ -lm -lc -lgcc_s
> /usr/lib/gcc/x86_64-linux-gnu/4.6.1/crtendS.o
> /usr/lib/gcc/x86_64-linux-gnu/4.6.1/../../../x86_64-linux-gnu/crtn.o -O2 -O2
> -O2 -Wl,-soname -Wl,liblinboxsage.so.0 -o .libs/liblinboxsage.so.0.0.0
> libtool: link: (cd ".libs" && rm -f "liblinboxsage.so.0" && ln -s
> "liblinboxsage.so.0.0.0" "liblinboxsage.so.0")
> libtool: link: (cd ".libs" && rm -f "liblinboxsage.so" && ln -s
> "liblinboxsage.so.0.0.0" "liblinboxsage.so")
> libtool: link: ar cru .libs/liblinboxsage.a linbox-sage.o
> libtool: link: ranlib .libs/liblinboxsage.a
> /bin/sed: can't read /usr/lib/libgmp.la: No such file or directory
> libtool: link: `/usr/lib/libgmp.la' is not a valid libtool archive
> make[4]: *** [liblinboxsage.la] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2011/09/02/linbox_1.1.6~rc0-4.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.
--- End Message ---
--- Begin Message ---
On Sun, Jan 15, 2012 at 10:48:28 +0100, Julien Cristau wrote:
> On Sun, Jan 15, 2012 at 10:39:46 +0100, Lucas Nussbaum wrote:
>
> > Actually linbox is still failing to build with this error (but not
> > libqalculate).
> >
> > See
> > http://people.debian.org/~lucas/logs/2012/01/12/linbox_1.1.6~rc0-4.1_lsid64.buildlog
> >
> > And #633169 has been fixed.
> >
> > I agree that it's unlikely to be a bug in linbox (even though linbox is
> > the only package failing to build due to a missing libgmp.la), but I'm
> > reopening this bug so that it's properly tracked and can be
> > investigated.
> >
> Bug is in libgivaro-dev:
> $ dpkg --fsys-tarfile
> /var/cache/apt/archives/libgivaro-dev_3.2.13-1.1_amd64.deb |tar xOf -
> ./usr/lib/libgivaro.la | grep dependency_libs
> dependency_libs=' /usr/lib/libgmp.la'
>
I've scheduled binNMUs so it'll have -lgmp instead. Better would be to
have libgivaro.la disappear, but there's already a bug for that.
Closing again.
Cheers,
Julien
signature.asc
Description: Digital signature
--- End Message ---
