On Monday, June 10, 2019 at 2:58:27 AM UTC-7, David Coudert wrote: > > working properly after make distclean with py2. Will now do it for py3. >
Right, I think that this is an issue with upgrading from the previous version; building from scratch by first doing `make distclean` worked for me, too. > > David. > > Le 9 juin 2019 à 23:23, John H Palmieri <jhpalm...@gmail.com <javascript:>> > a écrit : > > I performed the incremental build the way I always do: "git pull trac" > followed by "make". When I ran into problems, I restarted from 8.8.beta7, > which worked, and then merged #27847, after which I again got a crash. > > Building from scratch seems to work; at least Sage builds and runs; now > I'm running tests. > > John > > > > On Sunday, June 9, 2019 at 2:03:45 PM UTC-7, François Bissey wrote: >> >> As I suspect in the ticket (in which I also left a comment) the fact >> that the version 0.3.5 instead of 0.3.6 is mentioned in the trace make >> me think this is an incremental build problem. >> Something that should have been rebuilt didn’t and that may be because of >> the way you performed the incremental build. >> >> François >> >> > On 10/06/2019, at 7:46 AM, John H Palmieri <jhpalm...@gmail.com> >> wrote: >> > >> > >> > >> > On Sunday, June 9, 2019 at 12:37:52 PM UTC-7, John H Palmieri wrote: >> > I think the problem is with the openblas upgrade, >> https://trac.sagemath.org/ticket/27847. >> > >> > I opened https://trac.sagemath.org/ticket/27961 (not that I know how >> to fix it...) >> > >> > >> > >> > >> > On Sunday, June 9, 2019 at 10:19:27 AM UTC-7, David Coudert wrote: >> > crash with both python 2 and python 3 on osX. I attach the crash report >> with python 3. >> > >> > Any help is more than welcome. >> > >> > David. >> > >> > ===== >> > >> > confetti:sage dcoudert$ ./sage >> > ┌────────────────────────────────────────────────────────────────────┐ >> > │ SageMath version 8.8.rc0, Release Date: 2019-06-09 │ >> > │ Using Python 3.7.3. Type "help()" for help. │ >> > └────────────────────────────────────────────────────────────────────┘ >> > ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ >> > ┃ Warning: this is a prerelease version, and it may be unstable. ┃ >> > ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ >> > >> > ********************************************************************** >> > >> > Oops, Sage crashed. We do our best to make it stable, but... >> > >> > A crash report was automatically generated with the following >> information: >> > - A verbatim copy of the crash traceback. >> > - A copy of your input history during this session. >> > - Data on your current Sage configuration. >> > >> > It was left in the file named: >> > '/Users/dcoudert/.sage/ipython-5.0.0/Sage_crash_report.txt' >> > If you can email this file to the developers, the information in it >> will help >> > them in understanding and correcting the problem. >> > >> > You can mail it to: sage-support at sage-s...@googlegroups.com >> > with the subject 'Sage Crash Report'. >> > >> > If you want to do it now, the following command will work (under Unix): >> > mail -s 'Sage Crash Report' sage-s...@googlegroups.com < >> /Users/dcoudert/.sage/ipython-5.0.0/Sage_crash_report.txt >> > >> > In your email, please also include information about: >> > - The operating system under which the crash happened: Linux, macOS, >> Windows, >> > other, and which exact version (for example: Ubuntu 16.04.3, macOS >> 10.13.2, >> > Windows 10 Pro), and whether it is 32-bit or 64-bit; >> > - How Sage was installed: using pip or conda, from GitHub, as part of >> > a Docker container, or other, providing more detail if possible; >> > - How to reproduce the crash: what exact sequence of instructions can >> one >> > input to get the same crash? Ideally, find a minimal yet complete >> sequence >> > of instructions that yields the crash. >> > >> > To ensure accurate tracking of this issue, please file a report about >> it at: >> > http://trac.sagemath.org >> > >> > Hit <Enter> to quit (your terminal may close): >> > c >> > >> > >> > -- >> > 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-r...@googlegroups.com. >> > To post to this group, send email to sage-r...@googlegroups.com. >> > Visit this group at https://groups.google.com/group/sage-release. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/sage-release/6cab4410-4a6b-49b9-8346-19e3f0cb3f08%40googlegroups.com. >> >> >> > 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-r...@googlegroups.com <javascript:>. > To post to this group, send email to sage-r...@googlegroups.com > <javascript:>. > Visit this group at https://groups.google.com/group/sage-release. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/29806fdd-9364-469f-8839-d3b8b274362a%40googlegroups.com > > <https://groups.google.com/d/msgid/sage-release/29806fdd-9364-469f-8839-d3b8b274362a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/486992ef-f35f-4e3e-b017-53ad1a3057f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
