This bug is easily rectified.

Simply replace

#include "gmp.h"

with

#include "mpir.h"

in mpn/generic/redc_2.c

You then have to configure, make clean, make and it should build.

If you get an error about TMP_ALLOC or some such thing, then try

autoreconf -i

then do configure, make clean, make.

We are still trying to figure out how to fix the latter bug, but this
is a workaround for now.

Bill.

On 26 September 2012 22:33, James M. <jamesma...@gmail.com> wrote:
> When building MPIR 2.5.1 using msys I encountered a bug where during the
> make step an error complaining about there being no gmp.h
> steps to reproduce:
> 1) install msys on a windows system, installing the gcc, g++, and gfortran
> compilers making certain there is no lurking previous installation of gmp or
> mpir
> 2) extract the MPIR tarball to a new directory
> 3) open the mingw shell and navigate to the new mpir source directory
> 4) invoke configure as follows:
>     ./configure --enable-cxx --disable-shared
> 5) invoke make as follows:
>     make
> or
>     make -j 4
> Shortly you get the error message:
> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I..
> -D__GMP_WITHIN_GMP -I.. -DOPERATION_redc_2 -m32 -O2 -fomit-frame-pointer
> -mtune=corei7 -march=corei7 -c redc_2.c -o redc_2.o
> redc_2.c:24:17: fatal error: gmp.h: No such file or directory
> compilation terminated.
> make[2]: *** [redc_2.lo] Error 1
> make[2]: Leaving directory `/mpir-2.5.1/mpn'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/mpir-2.5.1'
> make: *** [all] Error 2
> (this error message came from running make instead of make -j 4 as the
> message ordering is a bit confusing with parallel jobs
>
> I found an easy workaround for this thankfully. when invoking configure add
> the option --enable-gmpcompat
> doing this enables successful compilation.
>
> I have not tested this on other windows systems or with configure options
> other than what I show here, sorry.
>
> --
> James M.
>
> --
> You received this message because you are subscribed to the Google Groups
> "mpir-devel" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/mpir-devel/-/xYv7DAnkEZkJ.
> To post to this group, send email to mpir-devel@googlegroups.com.
> To unsubscribe from this group, send email to
> mpir-devel+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/mpir-devel?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com.
To unsubscribe from this group, send email to 
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en.

Reply via email to