Sounds like progress! By the way, I don't know the specifics of the static + shared thing. It's been a limitation for a very long time, including way back when very little worked properly on Windows. The build system would randomly hang, things would randomly crash, compilers were really broken, you had to use a specific version of MinGW and it was really difficult to install, everything was really, really slow, it would run out of memory when building, parallel make didn't work, antivirus flagged configure as malicious, autotools needed a special version to work with Windows, even the archiving tool could completely crash the machine when symlinks were present. So the shared + static limitation didn't seem like that much of an issue.
But perhaps these days some of these old problems have been worked out on Windows. Bill. On 22 June 2013 00:40, Jean-Pierre Flori <[email protected]> wrote: > > > On Friday, June 21, 2013 7:20:23 PM UTC+2, Jean-Pierre Flori wrote: >> >> >> But it's definitely something asm related as passing MPN_PATH=generic to >> configure solves the tests segfault. >> (The ld segfault was solved following http://www.cygwin.com/ml/** >> cygwin/2013-06/msg00558.html<http://www.cygwin.com/ml/cygwin/2013-06/msg00558.html>) >> >> >>> >>>> Ok, the problem is that now the asm code used was the one targeted for > System V calling convention... > The solution is basically to do the (almost) same thing on cygwin(64) as > on mingw64, passing -f win64 passed to yasm, using the x86_64w directories > and renaming .asm to .as, using yasm_macwin.inc, expanding m4 macros, and > so on. > > Now I can build MPIR easily and it passes (nearly all of) its testsuite. > > By the way it's stated one cannot build static and shared libraries at the > same time because some headers are different but I cannot spot a difference > except for one lind defining the value of a *DLL macro to 0 or 1... > I asked the same question on the GMP list in december 2012 and never got > an answer. > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/mpir-devel. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/groups/opt_out.
