[mpir-devel] Re: Release candidate 4

2009-04-23 Thread Bill Hart
Perfect!! 2009/4/23 Jeff Gilchrist : > > On Thu, Apr 23, 2009 at 12:08 PM, Bill Hart > wrote: > >> This fixes a build issue on very recent apple machines reported by >> Marshall Hampton. > > So I had temporary access to a brand new MacBook Pro and tried RC4, it > detected it as penryn-apple-dar

[mpir-devel] Re: Release candidate 4

2009-04-23 Thread Jeff Gilchrist
On Thu, Apr 23, 2009 at 12:08 PM, Bill Hart wrote: > This fixes a build issue on very recent apple machines reported by > Marshall Hampton. So I had temporary access to a brand new MacBook Pro and tried RC4, it detected it as penryn-apple-darwin9.6.2 and configured, make, and make check all tes

[mpir-devel] Re: Release Candidate 4

2009-03-31 Thread Bill Hart
This issue is not relevant for MPIR 1.0.0 as we don't build yasm that way any more. So assuming Sage release their 3.4.1 today we'll make the current release candidate of MPIR the final release. I'm just sitting next to the build manager for Sage, and he tells me by tomorrow morning he should hav

[mpir-devel] Re: Release Candidate 4

2009-03-31 Thread Bill Hart
If, as you say, it built and passed make check, then according to the config.log, it's definitely built using the assembly for amd64. I'll add a ticket to look into removing the dependency of yasm on python. For now, it looks like you are good to go! Bill. 2009/3/31 Jeff Gilchrist : > On Tue, Ma

[mpir-devel] Re: Release Candidate 4

2009-03-30 Thread Bill Hart
Scratches head. Maybe it doesn't really need python. Configure output would certainly settle it. Bill. On 30/03/2009, Jeff Gilchrist wrote: > > On Mon, Mar 30, 2009 at 5:32 PM, Bill Hart > wrote: > >> I actually don't know what will happen if you build without python. If >> it works, you are

[mpir-devel] Re: Release Candidate 4

2009-03-30 Thread Jeff Gilchrist
On Mon, Mar 30, 2009 at 5:32 PM, Bill Hart wrote: > 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. It is an x86_64 system, and it builds, and make checks

[mpir-devel] Re: Release Candidate 4

2009-03-30 Thread Bill Hart
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

[mpir-devel] Re: Release Candidate 4

2009-03-30 Thread Jeff Gilchrist
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: Pyth

[mpir-devel] Re: Release Candidate 4

2009-03-29 Thread Bill Hart
If Jason agrees that this is a fix, and gets time to make the changes to trunk and mpir-1.0 before I go to sleep (I'm just packing bags now), I'll issue rc5. Otherwise it won't make it. Bill. 2009/3/29 mabshoff : > > > > On Mar 29, 2:43 pm, Bill Hart wrote: >> I've put release candidate 4 up. T

[mpir-devel] Re: Release Candidate 4

2009-03-29 Thread mabshoff
On Mar 29, 2:43 pm, Bill Hart wrote: > I've put release candidate 4 up. This fixes the yasm configure error > when -pc is present in the hostname. > > Known issues: > > * MSYS and mingw32: --enable-fat build failure > * Cygwin32: make check fails if build path contained spaces > * X86 32 bit Ap