On 2011-11-04 08:19, Julien Puydt wrote: > but rather a more deliberately fragile one : > - check very-specific-arch1, and set magic options if so ; > ... > - check very-specific-archN, and set magic options if so ; > - if we aren't on a known arch, or a fly farted too near a known one : > FAIL. This is *so* true. The problem here is that most Sage developers simply don't know about these issues and simply don't know or don't care about how to solve this.
> Another problem on the way to cross-compilation is that some packages > want to run tests at compile-time to adjust settings : those tests will > have to be disabled when cross-compiling. I think it's totally unrealistic to think that Sage will ever work under cross-compilers. There are so many spkgs which are written without giving thought to cross-compiling. So you would need to fix every such spkg (or convince upstream to do it, which is even harder). -- 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
