On x86 and x86_64 systems we use yasm to assemble the assembly code. Yasm has python as a dependency.
Eventually mpir itself will probably require python as we are considering using python for the build system. One way around it is to configure with host=..... and specify the host sytem you wish to build mpir for, but actually configure and build on another system which does have python. To figure out what the host should be, on the system you wish to build mpir for, run the config.guess script in the main source tree of mpir. Of course the final solution for us will be to supply binaries for a variety of systems. Fortunately it is rare for a system to not have python or for it to be difficult to obtain for a given system these days. I actually don't know what will happen if you build without python. If it works, you are good to go, but if it is x86_64 I doubt it will actually build, as yasm is absolutely required. Bill. On 30/03/2009, Jeff Gilchrist <jeff.gilchr...@gmail.com> wrote: > > A gcc 4.1.2 Linux 64bit Core2 system is configuring, making, and make > check just fine. > > On a an older gcc 3.4.6 Linux 64bit Opteron system, there is no python > so I get the warning: > configure: Checking for Python > checking for a Python interpreter with version >= 2.4... none > configure: WARNING: Python not found > configure: WARNING: Could not find a suitable version of Python > > Is anything disabled or not be compiled in if python is missing? What > does that mean for the user if they don't have python? > > Jeff. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
