On Tue, Feb 19, 2019 at 11:21 AM Emmanuel Charpentier <emanuel.charpent...@gmail.com> wrote: > > Dear Erik Madison, > > What setup would you like to test this patch ? My "everyday" machines do have > routinely matched gcc, g++,and gfortran packages : in such a setup, the test > would be useless, since gfortnat wouldn't be installed. > > Would a Debian virtual machine bearing the minimum dependencies described in > the Install guide give a correct test environment ? > > Do you wish to (try to) force Sage compilers' installation (ISTR that there > are some MALE targets allowing that). Would that be significant for you ? > > Do you need both Python2 and Python3 testing ?
I have done all the relevant testing myself. All I want is someone to set it to positive_review, and maybe look over the actual changes to make sure they make sense. If they want to do further testing that's up to them but really all I care about at this point is someone setting postivie_review so it can go to the buildbots for further testing, and then be merged and get still more testing by users, as with any other ticket. I believe it will solve a bug many users are having, and if there are any unintended side-effects they can be dealt with as they come (but I doubt it). > Le lundi 18 février 2019 16:47:31 UTC+1, E. Madison Bray a écrit : >> >> The ticket https://trac.sagemath.org/ticket/27016 has been sitting for >> several weeks in needs_review status, which is not all that unusual >> and normally I wouldn't care. However, people trying to build Sage >> for the first time on Linux keep getting bitten by this irritating >> gfortran issue. >> >> They can avoid it by ensuring that a gfortran is *correctly* installed >> on their system, though personally I don't care if they wind up >> (unnecessarily) building the gfortran SPKG either so long as it works. >> >> If the diff looks daunting, it really isn't. As I have explained >> multiple times on the ticket, it is mostly just refactoring of >> existing scripts: The spkg-install scripts for the gcc and gfortran >> packages were nearly identical, so I just merged them into one that >> could be reused. >> >> I then added a patch, which comes from Debian, to prevent gcc from >> installing libraries into some lib64/ directory, which we don't want >> in Sage. >> >> That's all it does, and I have tested it on multiple platforms myself >> including macOS. >> >> Thanks, >> E > > -- > 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 sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
