On Oct 24, 5:52 pm, Robert Bradshaw <rober...@math.washington.edu>
wrote:
> On Oct 23, 2009, at 8:30 AM, Dr. David Kirkby wrote:
>
>
>
> > Georg S. Weber wrote:
> >> Hi,
>
> >> for the record, the (above mentioned) Wikipedia article:
> >>http://en.wikipedia.org/wiki/Darwin_%28operating_system%29
> >> seems to be quite close to the truth;
> >> on MacPPC OS X 10.4.11 "uname -r" gives me:
> >> 8.11.0
> >> on MacIntel OS X 10.4.11 "uname -r" gives me:
> >> 8.11.1
>
> >> and finally on MacPPC OS X 10.2.1 "uname -r " gives me:
>
> >> 6.1
>
> >> So the rationale should be get the result from "uname -r" (or the
> >> like), either two or three digits separated by points, extract the
> >> first digit, and test whether it is "greater or equal to 8" (which
> >> corresponds to "Mac OS X 10.4 at least")
>
> >> In practice, however, it would be far more important to test, whether
> >> one tries to run a Sage binary, built on a MacPPC with a G5 CPU, on a
> >> MacPPC with only a G4 (or G3) CPU. This fails, and I myself know
> >> where
> >> to look in the pages long output to recognize this, but never had the
> >> time to do something about it. (BTW, this is a ticket on the sage-
> >> wishlist: trac #6414, "OS X binaries should issue a better warning
> >> on incompatible CPUs".)
>
> >> Cheers,
> >> Georg
>
> > Thank you. I took a look athttp://sagetrac.org/sage_trac/ticket/6414
>
> > The configure script can't perform a run-time check, which is what
> > is needed to
> > check if a binary is run on hardware unable to support it.
>
> > The configure script could however issue a warning at compile-time,
> > like:
>
> > "WARNING: Be aware, that the MacPPC you are building Sage on has a
> > G5 CPU. The
> > binary created can not be run on a MacPPC with a G3 or G4 CPU. If
> > you wish to
> > execute the binaries on a MacPPC with a G3 or G4 CPU, you MUST build
> > them on a
> > G3 or G4 CPU"
>
> -1 to this idea. Most users who compile Sage do it for their own use,
> not to transfer and use on another computer.
>
> It might be appropriate to put this into the bdist script, but even
> better would probably be to just have g5 in the name of the bdist, and
> also store the build info somewhere in the distribution so that if
> someone tries to run it on an older cpu they get an error/warning.
>
> - Robert
Personally, I can not see anything wrong with adding it to the
configure script. One could add
"If you only intend building Sage for use on your own computer, you
can safely ignore this warning."
Dave
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
