It should be enough to run Sage in a shell session where PATH variable does not contain anything from /sw/.
(there may be more variable that might affect running Sage, although this is probably a bug then) PS. it is true that Core2 duo is x86_64, but not all such CPUs are created equal. Different CPUs support different machine hardware commands, and compilers are able to use this to produce faster code, at expense of portability. This is why a binary distribution needs to use the most basic subset of machine commands to be useful on all x86_64s. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
