On Sunday, October 14, 2012 3:09:25 AM UTC-4, Johan Grönqvist wrote: > > Just a remark: This is not primarily about the actual hardware specs, > but about the assumptions that the OS makes on hardware specs, like the > difference between x86 and the 64-bit version. If I install a 32 bit > ubuntu, compile a program, and send it to someone else who tries to run > it on a 64-bit installation, they would have similar problems, even if > we had the same hardware.
I hope I am not speaking out of place, but I assume that Dima was referring to the prospect of building Sage on a phone. I may look into that more if the architecture thing doesn't work out or becomes too difficult. A few quick questions which may be better answered at a later time or in a different post: Would it make more sense to build Sage natively on Android or on a Linux .img? In either case, how compatible would the build be with a different phone? On Sunday, October 14, 2012 3:43:48 AM UTC-4, Snark wrote: > Interesting idea. The AC100 I compiled sage on is on armhf. > > "gcc -v" can tell you what you have ; in my case the target is > arm-linux-gnueabihf. > > Snark on #sagemath > I ran gcc -v and it came back with arm-linux-gnueabi without either hf or el. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
