When one types 'make', a configure script is run. That checks for various things (not very much currently), but it does check the gcc version and the perl version, plus a few other things.
One issue is that if someone starts a build, stops it, then restarts it by typing 'make', those checks will not take place a second time. If the build environment has changed, then this will not be detected. This seems a bit dangerous to me. Consider the following cenerario 1) Compiler change. * Log in and set CC, CXX and SAGE_FORTRAN to the Sun compilers. * The build fails (as it will now). * On another day, I type 'make', but this time gcc gets used, as I forgot to set CC 2) GCC update * Start building Sage * It fails, so we decide to update gcc * Type make again. Now part of the build is with one version gcc, but part with another. That seems pretty dangerous to me. For the time it takes to run ./spkg/base/prereq-0.3/configure (plus a few other other .spkg it currently rebuilds) it should be done each time 'make' is started. i.e. Add to the top of 'makefile' rm -f spkg/installed/prereq-0.3 Ideally, something should be done if the environment has changed. 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 URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
