Hi Brian, The file I have been modifying is gmp-h.in. As mpir-h.in is not under source control, presumably it is only on your machine.
It's not clear to me yet whether the file will need to be called mpir-h.in or gmp-h.in. I actually see problems both ways with autotools if we want to give the user the option of generating either gmp.h or mpir.h. At any rate, the file that will be used is currently called gmp-h.in, regardless of what it will end up being called in the distribution. I *think* it will end up being called mpir-h.in. Bill. 2008/9/9 Cactus <[EMAIL PROTECTED]>: > > Hi everyone, > > I have been checking the Windows build for MPIR and I find it now > fails. This is because I derive gmp.h and mpir.h from mpir_h.in and > the latter does not define __GMP_STATIC, which it uses, for anything > other than a GCC build. > > I corrected this but I then noticed that mpir_h.in is not under svn > control and is not a part of the distribution. But gmp_h.in is in the > distribution and it is also not the same as mpir_h.in > > So I am now confused about which of the files gmp_h.in and mpir_h.in I > should use to derive the Windows versions of gmp.h and mpir.h from. > > Right now I use mpir_h.in to generate gmp.h and I then copy gmp.h into > mpir.h > > Before I correct the Windows build, I would much appreciate advice on > which of gmp_h.in and mpir_h.in is supposed to be the master for the > derivation of the gmp.h and mpir.h header files. > > best regards, > > Brian > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
