Bug#718094: Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-31 Thread Steve M. Robbins
On Tue, Jul 30, 2013 at 04:05:10PM +0200, Vincent Lefevre wrote: On 2013-07-30 08:25:20 -0500, Steve M. Robbins wrote: On July 30, 2013 12:42:09 PM Vincent Lefevre wrote: (note that libmpfr-dev:i386 is not installable). I'm surprised you say that as it appears to have worked here. To my

Bug#718094: Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-31 Thread Vincent Lefevre
On 2013-07-31 09:31:10 -0500, Steve M. Robbins wrote: On Tue, Jul 30, 2013 at 04:05:10PM +0200, Vincent Lefevre wrote: I thought there was a clash with gcc (or some other installed package), but this was apparently due to a bug in apt. Adding gcc to apt-get install libmpfr-dev:i386 solves

Bug#718094: Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-30 Thread Vincent Lefevre
On 2013-07-29 23:46:38 -0500, Steve M. Robbins wrote: OK, how about with standard abi, the compiler will find it;i.e. without -m32. The lib32gmp package had to place its header in an unusual location which means, yes, the compiler won't find it without help. But in the past, the header was

Bug#718094: Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-30 Thread Steve M. Robbins
On July 30, 2013 12:42:09 PM Vincent Lefevre wrote: On 2013-07-29 23:46:38 -0500, Steve M. Robbins wrote: OK, how about with standard abi, the compiler will find it;i.e. without -m32. The lib32gmp package had to place its header in an unusual location which means, yes, the compiler won't

Bug#718094: Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-30 Thread Vincent Lefevre
On 2013-07-30 08:25:20 -0500, Steve M. Robbins wrote: On July 30, 2013 12:42:09 PM Vincent Lefevre wrote: (note that libmpfr-dev:i386 is not installable). I'm surprised you say that as it appears to have worked here. To my surprise, it appears even to be co-installable with the amd64

Bug#718094: Bug#675577: Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-29 Thread Steve M. Robbins
On July 28, 2013 05:40:23 PM Vincent Lefevre wrote: On 2013-07-28 17:28:57 +0200, Vincent Lefevre wrote: Currently I still don't understand why -m32 would be a problem. On http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675577 it is said My apologies -- it wasn't meant to be an intrusive

Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-28 Thread David Suárez
Source: mpfr4 Version: 3.1.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org 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

Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-28 Thread Vincent Lefevre
Hi, On 2013-07-27 19:29:10 +0200, David Suárez wrote: During a rebuild of all packages in sid, your package failed to build on amd64. I cannot reproduce this problem when compiling the official tarball (3.1.1 and 3.1.2) and when building Debian's version (3.1.1-1) with debuild -i -us -uc -b.

Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-28 Thread Vincent Lefevre
On 2013-07-28 17:23:28 +0200, Vincent Lefevre wrote: Hi, On 2013-07-27 19:29:10 +0200, David Suárez wrote: During a rebuild of all packages in sid, your package failed to build on amd64. I cannot reproduce this problem when compiling the official tarball (3.1.1 and 3.1.2) and when

Bug#718094: mpfr4: FTBFS: configure: error: gmp.h can't be found, or is unusable.

2013-07-28 Thread Vincent Lefevre
On 2013-07-28 17:28:57 +0200, Vincent Lefevre wrote: Sorry, forget my message. I didn't see that it was with -m32 (thus in a second call of configure). I can reproduce the problem and will investigate. Currently I still don't understand why -m32 would be a problem. ypig:~ cat tst.c #include