Your message dated Sun, 28 Jul 2013 12:26:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#718115: Acknowledgement (iml: FTBFS: configure: error:
GMP not found!)
has caused the Debian Bug report #718115,
regarding iml: FTBFS: configure: error: GMP not found!
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 [email protected]
immediately.)
--
718115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718115
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: iml
Version: 1.0.3-4.2
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20130726 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This is due to the recent switch to multiarch support on GMP.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675577
Relevant part (hopefully):
> checking for stdlib.h... (cached) yes
> checking for GNU libc compatible realloc... yes
> checking for bzero... yes
> checking for calloc... yes
> checking for floor... yes
> configure: error: GMP not found!
> GMP version 3.1.1 or greater is required for this library to compile.
> Please make sure GMP is installed and specify the header and libraries
> location with the options --with-gmp-include=<path> and --with-gmp-lib=<path>
> respectively when running configure.
> Default checking path = /usr /usr/local
> checking for GMP >= 3.1.1... not found
>
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/07/26/iml_1.0.3-4.2_unstable.log
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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi,
Closing one of duplicate bugs; #718115, #718114
(mta problems, sorry)
David
--- End Message ---
