On Fri, Nov 19, 2010 at 3:24 PM, Jason <ja...@njkfrudils.plus.com> wrote:
> In regard to Mingw* , well , what can I say , for mingw32 I have to install it > twice to get it to work ,apparently once just isn't good enough! I'm not > installing the latest though , but then again I didn't have this problem a > year ago. For mingw64 I used someone pre-packaged version "mingw-w64-bin-i686- > mingw-20100628.zip" (it was posted to the mpir-list about 9 months ago) , and > then I had to rename the exe's , install MSYS-1.0.11 , change fstab , and > maybe change path? > > Once it's working , then I used the usual configure options , nothing special > , > the only failure I got was for a shared library with c++ on make check (which > is an autotools problem, it gets the path wrong) , it passed make check on all > the other combinations of options(16 combinations). So my guess is that you > have a duff mingw64 install . I'm using a pre-packaged version that seems slightly older than yours: mingw-w64-bin_x86_64-mingw_20100322_sezero.zip with MSYS-1.0.11 as well. I'm not sure I would consider my mingw64 a "bad" installation since I have compiled many other things that work just fine, including GMP 5.0.1 with it. So not sure what is going on in this case. I did try just a basic ./configure && make && make check which did not work. Hopefully other people out there can try it on their systems to see what happens. I will see if I can upgrade to a newer release and also try to install it on another 64bit machine I just acquired. Jeff. -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-de...@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.
