Please ignore error report from my previous e-mail. I just forgot to run
autoreconf -i.

I've successfully compiled (all tests passed) the latest revision 3947 from
the trunk using the following configuration

./configure --prefix=/mingw --host=i686-pc-mingw32 --enable-gmpcompat

I've used latest mingw32 with gcc 4.7.0

On Wed, Sep 26, 2012 at 1:52 AM, Bill Hart <goodwillh...@googlemail.com>wrote:

> On 25 September 2012 17:02, Bill Hart <goodwillh...@googlemail.com> wrote:
> > I would *really* appreciate some help with the Mingw32 issue. What we
> > need to do is bisect the repo (svn trunk) and rebuild mpir until we
> > find out which commit caused mingw32 to stop working. It might only be
> > necessary to run configure and check to see if config.h has been
> > populated correctly with all the HAVE_NATIVE flags, which would save a
> > lot of time.
>
> Below is the relevant information from a previous post by Jason which
> explains what goes wrong. It has always been a problem on MinGW64, but
> seems to be a problem now on MinGW32.
>
> At any rate, all that would be required is to build mpir from svn
> trunk starting with the revision corresponding to mpir-2.5.1 (where it
> presumably last worked on MinGW32), i.e. revision 3850 and find which
> commit before revision 3949 causes the config.h file to not be
> properly populated as explained by Jason below.
>
> Any volunteers?
>
> ---------------
>
> I figured out what going on here , basically configure is failing to
> populate config.h with the required
> #define HAVE_NATIVE_mpn_addmul_2 1
> and all the others , it has always done this on mingw64 but because of
> the way the C file redc_2 uses addmul_2 it now causes a problem.A
> quick fix is to delete the lines in the mpn/generic/redc_2.c file
> where it trys to redefine addmul_2
>
> I don't know why configure fails to populate config.h , it manages to
> do the sym links
>
> ----------------
>
> Bill.
>
> --
> 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.
>
>

-- 
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