Yar i do not undarstand u? On 12/27/12, Jean-Pierre Flori <[email protected]> wrote: > > > On Wednesday, December 26, 2012 7:43:16 PM UTC+1, Jeroen Demeyer wrote: >> >> On 2012-12-26 19:04, Volker Braun wrote: >> > * SAGE_DEBUG=no means no debugging symbols (no gcc -g), which >> > basically only saves disk space. >> > >> > * SAGE_DEBUG=yes builds debug versions if possible (in particular, >> > Python and Singular). These will be notable slower but allow us to >> > pinpoint memory problems much more easily. >> > >> > * Anything else (including unset SAGE_DEBUG) is the same as the old >> > default, compile with debugging symbols but no debugging options that >> > influence performance. >> Good idea! >> >> Let me add that the GCC spkg also implements SAGE_DEBUG=yes by building >> a slower compiler with more internal checks (but the programs generated >> by GCC are the same). >> > As far as i remember, some spkg already have such a behavior, i.e. pass > different flags depending whether SAGE_DEBUG is actually set to yes or is > not set, which already differs from what the doc says. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > Visit this group at http://groups.google.com/group/sage-devel?hl=en. > > >
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
