On Feb 15, 11:55 am, degski <deg...@gmail.com> wrote:
> > 15/02/2011 10:05 <DIR> .
> > 15/02/2011 10:05 <DIR> ..
> > 15/02/2011 10:03 <DIR> bin
> > 15/02/2011 10:02 <DIR> doc
> > 15/02/2011 10:03 <DIR> include
> > 15/02/2011 10:03 <DIR> lib
> > 15/02/2011 10:03 <DIR> libexec
> > 15/02/2011 10:03 <DIR> mingw32
> > 13/02/2011 18:08 <DIR> mingw64
> > 15/02/2011 10:03 <DIR> msys
> > 15/02/2011 10:03 <DIR> share
> > 15/02/2011 09:59 18,244 unins000.dat
> > 15/02/2011 09:57 756,062 unins000.exe
> > 15/02/2011 09:59 <DIR> var
>
> > The only intervention here on my part is the addition of the mingw64
> > directory holding the 64 bit tools.
>
> > The msys home directory is at:
>
> > Directory of C:\mingw\msys\1.0\home
>
> > and contains:
>
> > 15/02/2011 10:07 <DIR> .
> > 15/02/2011 10:07 <DIR> ..
> > 15/02/2011 10:05 <DIR> Brian Gladman
> > 15/02/2011 10:50 <DIR> mpir
>
> I don't think it really matters alot as long as ..\msys\1.0\etc\fstab
> contains something like: c:/mingw-w64 /mingw, or whatever is applicable and
> the mingw bin-directory is in the path. Then, I've added name-stripped
> versions of x86_64-w64-mingw32-gcc.exe etc (i.e. gcc.exe) in the same
> directory, that seems to help some builds I've tried with mingw64...
>
> Cheers
>
> d.
Jason worked out what the problem is - configure fails if configure.in
has Windows line endings.
The build works fine once this file is given Unix line endings.
The resulting library fails in Visual Studio builds though because the
___chkstk symbol is undefined.
Does anyone know how to solve this one?
Congratulations to Jason on his detective work.
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-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.
