[sage-release] were ubuntu 14.04 binaries of 7.0 meant to work on any x86_64 CPU?
It appears that this report https://groups.google.com/d/msg/sage-support/fseE3_tQoQE/BCbFrskFCgAJ is an indication that these binaries are slightly broken; namely, an optional package csdp compiled on it gets faulty executables (they use blas/lapack/atlas in a nontrivial way). Could it be that SAGE_FAT_BINARY was not set for the build, or something like this? Just wondering, Dima -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Reverting blacklisting of GCC 4.8 (#20231)
+1 for still supporting GCC 4.8 for a while (unless it's very troublesome): this is the GCC version of Ubuntu 14.04 LTS, which is officially supported until April 2019. Eric. Le mercredi 11 mai 2016 17:40:44 UTC+2, Jeroen Demeyer a écrit : > > Hello Volker, > > would it be okay for you to revert Trac #20231 in Sage 7.2? The reason > for blacklisting GCC 4.8 was to support #20226, but that's not going to > be merged in Sage 7.2. So maybe it's best to still support GCC 4.8 in > Sage 7.2 (maybe with a deprecation warning in configure.ac). > > When #20226 gets merged in some later beta, we can then either re-merge > #20231 or find a work-around to make it work with GCC 4.8. > > Jeroen (discussing with Luca De Feo and Erik Bray) > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Re: Reverting blacklisting of GCC 4.8 (#20231)
If you make a ticket then I'm happy to merge it... On Wednesday, May 11, 2016 at 5:40:44 PM UTC+2, Jeroen Demeyer wrote: > > Hello Volker, > > would it be okay for you to revert Trac #20231 in Sage 7.2? The reason > for blacklisting GCC 4.8 was to support #20226, but that's not going to > be merged in Sage 7.2. So maybe it's best to still support GCC 4.8 in > Sage 7.2 (maybe with a deprecation warning in configure.ac). > > When #20226 gets merged in some later beta, we can then either re-merge > #20231 or find a work-around to make it work with GCC 4.8. > > Jeroen (discussing with Luca De Feo and Erik Bray) > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
[sage-release] Reverting blacklisting of GCC 4.8 (#20231)
Hello Volker, would it be okay for you to revert Trac #20231 in Sage 7.2? The reason for blacklisting GCC 4.8 was to support #20226, but that's not going to be merged in Sage 7.2. So maybe it's best to still support GCC 4.8 in Sage 7.2 (maybe with a deprecation warning in configure.ac). When #20226 gets merged in some later beta, we can then either re-merge #20231 or find a work-around to make it work with GCC 4.8. Jeroen (discussing with Luca De Feo and Erik Bray) -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.