Hi Brian
I notice that for win64 you have a scipt gen_mpir_h.bat which define's
LONG_LONG_LIMB 1
Is there any reason you did it this way , rather than at somewhere before
line194 in gmp-h.in
#ifdef _WIN64
#define _LONG_LONG_LIMB 1
#endif
because for the mingw64 I need to set it anyway
Thanks
Jason
----- Original Message -----
From: "jason" <ja...@njkfrudils.plus.com>
To: <mpir-devel@googlegroups.com>
Sent: Saturday, August 14, 2010 2:41 AM
Subject: Re: [mpir-devel] Re: MPIR 2.2
Hi Brian
your new changes work , make check passes
cheers
To get mingw64 to work I need to go thru the code so that the long long
int get used when we are using mingw64 as well as win64 MSVC
I'm assuming
_MSC_VER defined <=> using MSVC
_WIN64 defined <=> 64bit
_WIN32 defined <=> 32bit
mingw64 defines _WIN64 but not _MSC_VER , as you would expect
Thanks
Jason
----- Original Message -----
From: "jason" <ja...@njkfrudils.plus.com>
To: <mpir-devel@googlegroups.com>
Sent: Saturday, August 14, 2010 1:13 AM
Subject: Re: [mpir-devel] Re: MPIR 2.2
----- Original Message -----
From: "jason" <ja...@njkfrudils.plus.com>
To: <mpir-devel@googlegroups.com>
Sent: Saturday, August 14, 2010 12:31 AM
Subject: Re: [mpir-devel] Re: MPIR 2.2
On vs2008 configure && make gave us this
prebuild failed , I'll fix my batch file to use the new method
Done
and in make check
Build failure for mpn.divebyff
Build failure for mpn.divebyfobm1
Looks like t-NAME.c must match mpn/NAME.c for your MSVC builds
I've not bothered with this in linux , YET
this was on a nehalem
make clean needs to be update to cope with new directory structure as it
leaves a lots of files around
Jason
On the 64Mingw , I 'll have to change the autotools to get it to accept
longlong build
----- Original Message -----
From: "jason" <ja...@njkfrudils.plus.com>
To: <mpir-devel@googlegroups.com>
Sent: Saturday, August 14, 2010 12:15 AM
Subject: Re: [mpir-devel] Re: MPIR 2.2
Thanks , I'll test it now.
I dont think I can agree to take it on as it completely unfamilar to
use a gui for me , and I wont have the time.
I'm going to look at a cmd line build for it though.
On a similar note I've just installed mingw64 , but for some reason it
still thinks it 32bit.
Ha just worked it out , Of COURSE , long is 32bit , have to try
longlong
Jason
----- Original Message -----
From: "Cactus" <rieman...@gmail.com>
To: "mpir-devel" <mpir-devel@googlegroups.com>
Sent: Friday, August 13, 2010 11:48 PM
Subject: [mpir-devel] Re: MPIR 2.2
On Aug 13, 10:42 pm, Cactus <rieman...@gmail.com> wrote:
On Aug 13, 8:41 pm, Jason <ja...@njkfrudils.plus.com> wrote:
> I've changed the files to match the function names of
> mpn/perfsqr.c to mpn/perfect_square_p.c
> mpn/jacbase.c to mpn/jacobi_base.c
> mpn/divis.c to mpn/divisible_p.c
> and I've split out
> mpn/dc_bdiv_qr_n.c from mpn/dc_bdiv_qr.c
> mpn/dc_div_qr_n.c from mpn/dc_div_qr.c
> again I've not touched the build.vc* directorys . For the first 3
> changes , I
> know how to do it , but I dont know how to add a file under NSVC .
Hi Jason,
This is much harder than a name change and I might not even be able to
do it now that I don't have Visual Studio 2008 installed.
I can explain the steps but it is intricate and I would not want to do
this until you (or someone else) agrees to take on the Visual Studio
2008 ongoing support and maintenance task.
The Visual Studio 2008 build definitely won't work now and I won't do
any further work on it as it is too time consuming and tedious to do
both this and the 2010 builds.
Brian
I have made the changes to the Visual Studio 2008 build files that I
think are needed to add all the recent changes.
But I have not tested anything.
Brian
--
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.
--
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.
--
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.
--
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.
--
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.
--
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.