gsw wrote: > > +1 to option (3). > > Cheers, Georg OK, give there are two +1's, I also think option 3 is best, then when I make a new prereq, the following will happen. (option 3)
----------------------------------- 3) Exit if gcc or g++ can not be found unless SAGE_PORT is exported to some non-empty value. Currently SAGE_PORT is only needed on some operating systems, and has nothing to do with compilers, but we could extend it's usage to mean any unsupported operating systems or unsupported compiler. If SAGE_PORT is exported to some non-empty value, then the build can proceed without gcc and g++ even if gcc and g++ are not in the path. ----------------------------------- I'll make a new prereq-0.5 which fixes that issue, and a few others I am aware of. I'd really appreciate if anyone has any ideas for other things which should be checked to make sure there build environment is sane. There is nothing worst than someone spending half a day compiling code to find it fails, when the reason for the failure could have been picked up very early on. 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 -~----------~----~----~----~------~----~------~--~---
