By "this bug", you mean even after a "make distclean" it does not compile? Or just get to a step where "make" doesn't work, the latter is probably easy since some packages can trip over headers that were left over by old / incomplete installs.
On Monday, March 10, 2014 2:23:30 PM UTC, Nathann Cohen wrote: > > Because Sage would not start anymore after I "finally achieved" to > reproduce this bug, I tried to recompile Sage from scratch... And ended up > with that : > > **************************************************** > NOTE: Set SAGE_MATPLOTLIB_GUI to anything but 'no' to try to build the > Matplotlib GUI. > Not building any matplotlib graphical backends. > patching file setupext.py > basedirlist is: ['/home/ncohen/.Sage/local'] > > ============================================================================ > BUILDING MATPLOTLIB > matplotlib: 1.2.1 > python: 2.7.5 (default, Mar 10 2014, 14:13:21) [GCC 4.8.2] > platform: linux2 > > REQUIRED DEPENDENCIES > numpy: no > * You must install numpy 1.4 or later to build > * matplotlib. > Error building matplotlib package. > > real 0m0.203s > user 0m0.100s > sys 0m0.020s > ************************************************************************ > Error installing package matplotlib-1.2.1 > ************************************************************************ > > Somehow, when "make" fails and I re-type "make" immediately after, it > seems that Sage does not do exactly what it failed to do before. But maybe > that's normal because the previous "make" did compile some dependencies > after all. > > Nathann > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
