On 16/03/2009, mabshoff <michael.absh...@mathematik.uni-dortmund.de> wrote:
>
>
>
> On Mar 16, 10:00 am, Bill Hart <goodwillh...@googlemail.com> wrote:
>> Someone with access to the machine is going to have to give me more clues.
>
> This is a Sage build on varro (a G5), but it is being run on a G4
> laptop we do not have access to.
>

OK.

>> How does it know that it is an invalid cpu subtype?
>
> I do not know, but I have never seen this error message before.

Me either. I don't think MPIR outputs it. Would it be a linker error message?

>
>> Does GMP produce differently named binaries?
>
> No. GMP might set different march and mcpu values, but AFAIK no other
> changes besides the switch from GMP to MPIR was made, i.e. it is the
> same XCode, etc.

Which package issues the warning then? If it doesn't tell based on the
name, it must look inside the binary. It doesn't look like the sort of
thing the linker is checking, but rather something some autoconf
script is checking. If we find out what the script actually does, I.e.
Look at the generated configure we might figure out what the
difference is.

>
>> Were there any warnings during configure or make?
>
> I will have to look.
>
>> Are G5 and G4 cpus compatible?
>
> Binaries using the G4 instruction set build on a G5 should run on the
> G4. THe G5 has additional SIMD instructions over the G4, but those are
> not used in GMP or MPIR.

OK.

>
>> Isn't G5 64 bits?
>
> Yes, but the binary we build is 32 bit.

OK.

>
>> Has anyone tried building a binary for the G4 with the right host=
>> option to configure?
>
> Not that I know of. At some point in the past the binaries from varro
> worked on G4 laptops. I am not 100% sure the issue reported here
> popped up right at the GMP->MPIR switch in Sage, but it looks like too
> much of a coincidence.

Right, but I don't recall changing any ppc compiler flags. If they
were different without a reason this would be a bug in MPIR.

Bill.

>
>> Bill.
>
> I will build GMP.spkg and MPIR.spkg on that box and see if anything
> pops out in the log.
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to