>So, a better question is: is there an estimate for how long a complete build, excluding or including documentation I don't care) should take on my machine (cpuinfo see above, using MAKE="make -j4").
My guess: more than two hours excluding documentation (where memory is important which info I cannot see in your post). On Mon, Oct 17, 2016 at 9:03 AM 'Martin R' via sage-release < sage-release@googlegroups.com> wrote: > complete from scratch. > > So, a better question is: is there an estimate for how long a complete > build, excluding or including documentation I don't care) should take on my > machine (cpuinfo see above, using MAKE="make -j4"). > > Martin > > Am Montag, 17. Oktober 2016 08:16:22 UTC+2 schrieb Jeroen Demeyer: > > On 2016-10-16 20:20, 'Martin R' via sage-release wrote: > > It seems that this made openblas build, thank you. > > > > However: the build takes so long that it makes me wonder. Is it > > possible that it takes much longer to build this release candidate than > > some beta before? > > The build of *what* takes so long? The openblas build? Of an incremental > Sage build? Of a complete from-scratch Sage build? > > -- > 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. > -- 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.
