----- Original Message -----
From: "Jason"
That's the secret then - just use a compiler later than 20100428. (If
only
I'd waited another fortnight before I downloaded that compiler :-)
Ah Ah , I'll put a note on our website about this
Ozkan posted a follow-up, explaining that he hadn't quoted the details of
the non-compliance correctly:
--quote--
It seems I have typo in my explanations: our old x64-compilers *did*
prepend an underscore to the symbols (bad behavior), but the new
compilers do not which is the expected MS-compatible behavior.
--endquote--
make check fails for a C++ shared lib build , due to the lib's being in
the
wrong place , almost certainly an autotools problem (MinGW32 had the same
problem until we upgraded autotools)
make speed , try , or tune , all won't build due to autotools not setting
the
correct include paths
I wonder if the last two problems with autotools are to do with them
assuming
*-pc-mingw32 rather than *-w64-mingw32
Sounds feasible to me. I know my 64-bit cross-compiler has the includes in
mingw/include and the libraries in mingw/lib, whereas the 32-bit compiler
(from mingw.org) has them in include and lib repectively.
There's a trap, however - sezero's 64-bit builds (and perhaps also some of
the other private builds) put them in include and lib (not mingw/include and
mingw/lib). That being the case, using one of sezero's 64-bit compilers
might currently work ... if your hypothesis is correct :-)
Cheers,
Rob
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
