leif wrote:
Simon King wrote:
I'm just thinking: Perhaps one could check the result rather than the
gcc version?
My spkg first builds a patched version of C-MeatAxe (for linear algebra
over finite fields) and then some programs of David Green (which use
C-MeatAxe, and I wouldn't like to rewrite them to use Linbox...); this
works pretty fast. After that, my Cython code gets processed, and this
takes some time.
And it is the programs of David Green which don't work with old gcc and
high optimization. So, before processing the Cython code, I could simply
call David's programs; if they work without error, then apparently the
gcc version was fine.
You could probably even add such a check to the Makefile for his
programs; haven't yet looked at your spkg at all...
-leif
Would this be a valid approach?
If that doesn't add an overhead of days to the overall build time... Sure.
[And it shouldn't leave crap / a partial install in the Sage
installation, i.e., $SAGE_ROOT/{local,data}/*, in case the check fails.]
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
