On Tuesday, 22 May 2012, Bill Hart <goodwillh...@googlemail.com> wrote: > > > On Tuesday, 22 May 2012, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: >> On 2012-05-22 15:37, Bill Hart wrote: >>> We could then >>> ditch building Yasm on Linux, which would save some headaches for >>> Sage. >> I don't really think that yasm is a problem for Sage. It's true that >> sometimes a Sage build might build because of a problem with yasm, but >> it's more because MPIR/YASM is the first non-trivial program built in >> Sage, it would have failed somewhere else anyway. > > Appreciated Jeroen. The current discussion is about whether Brian can use the default assembler with MSVC. Unfortunately that has pretty massive consequences for which assembler is used. That is independent of your original question. > > Does nasm accept MASM files. We could perhaps switch to including that if Brian switches to MASM.
No it doesn't. In fact there are no Open Source 32/64 bit assemblers which support MASM format which have licenses that would be accepted in major Linux distributions (this is important for Sage which uses MPIR and is distributed in this way). So we only have three options: * abandon MinGW support * find someone to maintain MinGW support, including conversion of assembly code to Yasm or GCC format * continue to use yasm for Linux, MinGW and MSVC builds Given the particular contributors we have, option 1 seems to be the only way to switch to Masm on MSVC. That would be highly ironic given that GMP now fully supports MinGW. It also stops projects which want to use MPIR from supporting MinGW. At the moment that does not include Sage, as it is considered too hard for Sage to support MinGW. But there are other projects we need to consider, such as PHP and GMPY. Bill. > > Bill. > >> >> My question was meant mostly to try to understand the MPIR build process. >> >> -- >> 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. >> >> -- 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.
