Hi Leif,
On 2013-05-12, leif <[email protected]> wrote:
>> 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.
>>
>> Would this be a valid approach?
>
> If that doesn't add an overhead of days to the overall build time... Sure.
Building these programs is less than a minute (and has to be done anyway),
testing it should be less than a second. The overall build time is more
like 5 to 10 minutes, but most of the time would come *after* the test.
> [And it shouldn't leave crap / a partial install in the Sage
> installation, i.e., $SAGE_ROOT/{local,data}/*, in case the check fails.]
Indeed, the programs would create data on disk, and it relies on the
contents of some other file on disk. However, a test case would be
really small and would probably add less than 200 Byte to the spkg.
And the itt could all happen in the build directory. This would usually be
deleted after an installation attempt, isn't it? So, it would vanish,
regardless whether the check fails or not.
It sounds like I should try it.
Best regards,
Simon
--
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.
