Re: [mpir-devel] Re: MinGW64

2011-02-14 Thread degski
> > my msys directory structure didn't have the home and user name part though > Probably: mingw mingw64 msys home 1.0 <<< Brian Gladman (added by msys) mpir Cheers -- You received this message because you are subscribed to the Google Gr

Re: [mpir-devel] Re: MinGW64

2011-02-14 Thread Jason
On Monday 14 February 2011 17:14:25 Cactus wrote: > On Feb 14, 5:09 pm, Cactus wrote: > > On Feb 14, 3:38 pm, "jason" wrote: > > > Python doesn't matter it's not used , this happens on every machine and > > > OS I have tested with or without python , the yasm python detect is > > > broken .I thin

[mpir-devel] Re: MinGW64

2011-02-14 Thread Cactus
On Feb 14, 5:09 pm, Cactus wrote: > On Feb 14, 3:38 pm, "jason" wrote: > > > > > > > > > > > Python doesn't matter it's not used , this happens on every machine and OS I > > have tested with or without python , the yasm python detect is broken .I > > think yasm uses python to build it's docs >

[mpir-devel] Re: MinGW64

2011-02-14 Thread Cactus
On Feb 14, 3:38 pm, "jason" wrote: > Python doesn't matter it's not used , this happens on every machine and OS I > have tested with or without python , the yasm python detect is broken .I > think yasm uses python to build it's docs > > Jason > > > > > > > > - Original Message - > From:

Re: [mpir-devel] Re: MinGW64

2011-02-14 Thread jason
Python doesn't matter it's not used , this happens on every machine and OS I have tested with or without python , the yasm python detect is broken .I think yasm uses python to build it's docs Jason - Original Message - From: "Cactus" To: "mpir-devel" Sent: Monday, February 14, 2011

[mpir-devel] Re: MinGW64

2011-02-14 Thread Cactus
On Feb 14, 10:32 am, Jason wrote: > On Monday 14 February 2011 09:59:46 Cactus wrote: > > > > > > > > > > > On Feb 14, 9:45 am, Jason wrote: > > > Hi > > > > I've tried this combination > > > MSYS installed c:\msys > > > mingw installed c:\mingw > > > > and as long as I specified the full path

Re: [mpir-devel] Re: MinGW64

2011-02-14 Thread Jason
On Monday 14 February 2011 09:59:46 Cactus wrote: > On Feb 14, 9:45 am, Jason wrote: > > Hi > > > > I've tried this combination > > MSYS installed c:\msys > > mingw installed c:\mingw > > > > and as long as I specified the full path to configure it worked fine , ie > > > > ./configure CC=/c/min

Re: [mpir-devel] Re: The 'length of long' issue

2011-02-14 Thread Jason
On Sunday 13 February 2011 16:43:47 Cactus wrote: > [cut previous text] > > > > Probably the easiest solution on Windows is to simply to express the > > > integer parameters of ui/si functions (and some internal integers in > > > the functions themselves) as a new global integer type that is > > >

[mpir-devel] Re: MinGW64

2011-02-14 Thread Cactus
On Feb 14, 9:45 am, Jason wrote: > Hi > > I've tried this combination > MSYS installed c:\msys > mingw installed c:\mingw > > and as long as I specified the full path to configure it worked fine , ie > > ./configure CC=/c/mingw/bin/x86_64-w64-mingw32-gcc.exe > > although for C++ you would a

Re: [mpir-devel] Re: MinGW64

2011-02-14 Thread Jason
Hi I've tried this combination MSYS installed c:\msys mingw installed c:\mingw and as long as I specified the full path to configure it worked fine , ie ./configure CC=/c/mingw/bin/x86_64-w64-mingw32-gcc.exe although for C++ you would also have to tell it where the standard C++ library is

Re: [mpir-devel] Re: MinGW64

2011-02-14 Thread Jason
On Sunday 13 February 2011 22:48:00 Cactus wrote: > On Feb 13, 10:37 pm, "jason" wrote: > > Hi > > > > I think when using as a cross compile use > > CC=x86_64-w64-mingw32-gcc.exe > > and not > > CC=c:/path_etc/bin/x86_64-w64-mingw32-gcc.exe > > > > The configure for me works with space but the b