Someone with access to the machine is going to have to give me more clues.
How does it know that it is an invalid cpu subtype? Does GMP produce differently named binaries? Were there any warnings during configure or make? Are G5 and G4 cpus compatible? Isn't G5 64 bits? Has anyone tried building a binary for the G4 with the right host= option to configure? Bill. 2009/3/16 mabshoff <michael.absh...@mathematik.uni-dortmund.de>: > > > > On Mar 16, 9:46 am, Bill Hart <goodwillh...@googlemail.com> wrote: >> I have no particular insight into this. A G5 is a PPC right? Well, I >> don't know of anything that we've changed for PPC's. > > Yes, I am surprised that the problem came up since I did not expect > any changes relative to MPIR 0.9 and the GMP 4.2.1 Sage shipped. > >> It does appear to be looking for libgmp though, not libmpir. Perhaps >> the --enable-gmplink configure option (which you used, as per the >> instructions, right?) is not dealing correctly with dylibs? > > This is MPIR 0.9, so that change should have no impact (yet). > >> Jason may be able to comment on that. >> >> Bill. > > Cheers, > > Michael > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
