Simon King wrote:
Version 2.1.4 of my optional p_group_cohomology spkg got a positive review a few days ago. Now, I found that it will not correctly build with gcc 4.4.5 (which my university's sysadmins have put on the computer in my office), while it *does* work with Sage's gcc spkg (4.7.2) on the same machine, and also with gcc 4.6.2 on my laptop. Cause of the problem could be an increased optimization level for some part of the C-code.
I wouldn't be too concerned with /optional/ spkgs and a few broken (in this case no longer maintained, 4.4.6 was the last bugfix release IIRC) compiler versions -- unless this may silently lead to wrong results perhaps.
Does the /build/ fail with Debian's GCC 4.4.5, or some test suite of your spkg?
If it's not too complicated, you could lower the optimization level depending on the GCC version, or some build option, though.
In any case, documenting the situation shouldn't hurt... ;-) -leif
What is to do in such situation? Is it enough to add a warning on the project web page and add a test for the gcc version to spkg-install when the next version of the spkg is ready (in a couple of months)? Or do you think the test should be added right now? Is the new package version already put into the repository of optional packages? Best regards, Simon
-- () 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.
