On Fri, Oct 23, 2009 at 4:56 PM, Jason Moxham <ja...@njkfrudils.plus.com> wrote: > > Actually being an apple machine can we narrow down the cpu some more , ie will > it just be a core2 in 32bit mode , as apple didn't start using intel cpus > until then ?
I think it will just be a core2 cpu. Below are the comments I received: Can't build MPIR 1.3 in a way that pleases gmpy: unless I use --disable_shared MPIR won't build (there's a note in the .info about problems doing PIC on the Mac), if I do MPIR is fine but gmpy can't link to it (because of the lack of PIC). casevh > > On Saturday 24 October 2009 00:45:03 Jason Moxham wrote: >> On Friday 23 October 2009 19:17:18 casevh wrote: >> > I've been tested the latest version of gmpy with mpir-1.3.0rc1. >> > Everything works fine on Windows and Linux. Another developer tested >> > with OSX and encountered trac issue #94. Python/gmpy wants the PIC >> > option. :( >> > >> > Is there a chance this issue will be fixed soon? (I have no idea if >> > the fix is easy or hard.) >> > >> > Thanks, >> > >> > casevh >> >> This should be easy to do a workaround once we have identitfied which >> systems are affected.Does a config.guess of >> x86*-apple-darwin >> cover all the affected systems and no others? >> And is this only for a shared library ? or is it for static as well? >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
