Compiling sage-8.8 or sage-8.9 from source on Mac OS X 10.13 fails in sagenb
66 views
Skip to first unread message
Matthias Goerner
Sep 17, 2019, 9:40:51 PM9/17/19
to sage-devel
I have been trying to compile sage from source. I tried sage-8.8, then sage-8.9. Both failed:
[sagenb-1.1.2] reading sources... [ 15%] misc/misc
[sagenb-1.1.2]
[sagenb-1.1.2] Exception occurred:
[sagenb-1.1.2] File "sage/misc/lazy_import.pyx", line 218, in sage.misc.lazy_import.LazyImport._get_object (build/cythonized/sage/misc/lazy_import.c:2502)
[sagenb-1.1.2] raise RuntimeError(f"resolving lazy import {self._name} during startup")
[sagenb-1.1.2] RuntimeError: resolving lazy import dumps during startup
[sagenb-1.1.2] The full traceback has been saved in /var/folders/qf/wr6_n5s56m780kv130nznmlc0000gn/T/sphinx-err-MzyE1A.log, if you want to report the issue to the developers.
[sagenb-1.1.2] Please also report this if it was a user error, so that a better error message can be provided next time.
[sagenb-1.1.2] A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
What is going on?
Dima Pasechnik
Sep 18, 2019, 2:11:59 AM9/18/19
to sage-devel
The error in sagenb building is an indication that there was an error earlier on.
What does happen if you try starting Sage by doing
./sage
?
--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/8574ac54-9e6c-41bd-bfaa-1f91ad786172%40googlegroups.com.
E. Madison Bray
Sep 18, 2019, 5:44:33 AM9/18/19
to sage-devel
On Wed, Sep 18, 2019 at 8:11 AM Dima Pasechnik <dim...@gmail.com> wrote:
>
> The error in sagenb building is an indication that there was an error earlier on.
>
> What does happen if you try starting Sage by doing
>
> ./sage
>
> ?
This seems to be happening often enough when there are build issues
>
> The error in sagenb building is an indication that there was an error earlier on.
>
> What does happen if you try starting Sage by doing
>
> ./sage
>
> ?
(and thus obscuring them because the problem seems to be something to
do with sagenb when it isn't) that we should probably change something
in the Makefile when it comes to building packages that depend on
sagelib.
Not sure about the details, but somehow make $(STARTED) a prerequisite
for any packages that have sagelib as a prerequisite.
Dima Pasechnik
Sep 18, 2019, 5:55:34 AM9/18/19
to sage-devel
On Wed, Sep 18, 2019 at 10:44 AM E. Madison Bray <erik....@gmail.com> wrote:
>
> On Wed, Sep 18, 2019 at 8:11 AM Dima Pasechnik <dim...@gmail.com> wrote:
> >
> > The error in sagenb building is an indication that there was an error earlier on.
> >
> > What does happen if you try starting Sage by doing
> >
> > ./sage
> >
> > ?
>
> This seems to be happening often enough when there are build issues
> (and thus obscuring them because the problem seems to be something to
> do with sagenb when it isn't) that we should probably change something
> in the Makefile when it comes to building packages that depend on
> sagelib.
>
> Not sure about the details, but somehow make $(STARTED) a prerequisite
> for any packages that have sagelib as a prerequisite.
Please open a ticket on this!
>
> On Wed, Sep 18, 2019 at 8:11 AM Dima Pasechnik <dim...@gmail.com> wrote:
> >
> > The error in sagenb building is an indication that there was an error earlier on.
> >
> > What does happen if you try starting Sage by doing
> >
> > ./sage
> >
> > ?
>
> This seems to be happening often enough when there are build issues
> (and thus obscuring them because the problem seems to be something to
> do with sagenb when it isn't) that we should probably change something
> in the Makefile when it comes to building packages that depend on
> sagelib.
>
> Not sure about the details, but somehow make $(STARTED) a prerequisite
> for any packages that have sagelib as a prerequisite.
>
>
>
> > On Wed, 18 Sep 2019 02:40 Matthias Goerner, <enis...@gmail.com> wrote:
> >>
> >> I have been trying to compile sage from source. I tried sage-8.8, then sage-8.9. Both failed:
> >>
> >> [sagenb-1.1.2] reading sources... [ 15%] misc/misc
> >> [sagenb-1.1.2]
> >> [sagenb-1.1.2] Exception occurred:
> >> [sagenb-1.1.2] File "sage/misc/lazy_import.pyx", line 218, in sage.misc.lazy_import.LazyImport._get_object (build/cythonized/sage/misc/lazy_import.c:2502)
> >> [sagenb-1.1.2] raise RuntimeError(f"resolving lazy import {self._name} during startup")
> >> [sagenb-1.1.2] RuntimeError: resolving lazy import dumps during startup
> >> [sagenb-1.1.2] The full traceback has been saved in /var/folders/qf/wr6_n5s56m780kv130nznmlc0000gn/T/sphinx-err-MzyE1A.log, if you want to report the issue to the developers.
> >> [sagenb-1.1.2] Please also report this if it was a user error, so that a better error message can be provided next time.
> >> [sagenb-1.1.2] A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
> >>
> >> What is going on?
> >>
> >> --
> >> 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+...@googlegroups.com.
> >> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/8574ac54-9e6c-41bd-bfaa-1f91ad786172%40googlegroups.com.
> >
> > --
> > 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+...@googlegroups.com.
> > To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2CqBSES6RBjP3zddNWdcgSt_meXs2XJLrQcELDzQrLNg%40mail.gmail.com.
>
> --
> 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+...@googlegroups.com.
E. Madison Bray
Sep 18, 2019, 5:58:10 AM9/18/19
to sage-devel
On Wed, Sep 18, 2019 at 11:55 AM Dima Pasechnik <dim...@gmail.com> wrote:
>
> On Wed, Sep 18, 2019 at 10:44 AM E. Madison Bray <erik....@gmail.com> wrote:
> >
> > On Wed, Sep 18, 2019 at 8:11 AM Dima Pasechnik <dim...@gmail.com> wrote:
> > >
> > > The error in sagenb building is an indication that there was an error earlier on.
> > >
> > > What does happen if you try starting Sage by doing
> > >
> > > ./sage
> > >
> > > ?
> >
> > This seems to be happening often enough when there are build issues
> > (and thus obscuring them because the problem seems to be something to
> > do with sagenb when it isn't) that we should probably change something
> > in the Makefile when it comes to building packages that depend on
> > sagelib.
> >
> > Not sure about the details, but somehow make $(STARTED) a prerequisite
> > for any packages that have sagelib as a prerequisite.
>
> Please open a ticket on this!
Done: https://trac.sagemath.org/ticket/28513
>
> On Wed, Sep 18, 2019 at 10:44 AM E. Madison Bray <erik....@gmail.com> wrote:
> >
> > On Wed, Sep 18, 2019 at 8:11 AM Dima Pasechnik <dim...@gmail.com> wrote:
> > >
> > > The error in sagenb building is an indication that there was an error earlier on.
> > >
> > > What does happen if you try starting Sage by doing
> > >
> > > ./sage
> > >
> > > ?
> >
> > This seems to be happening often enough when there are build issues
> > (and thus obscuring them because the problem seems to be something to
> > do with sagenb when it isn't) that we should probably change something
> > in the Makefile when it comes to building packages that depend on
> > sagelib.
> >
> > Not sure about the details, but somehow make $(STARTED) a prerequisite
> > for any packages that have sagelib as a prerequisite.
>
> Please open a ticket on this!
Matthias Goerner
Sep 18, 2019, 5:59:15 AM9/18/19
to sage-devel
On Wednesday, September 18, 2019 at 2:11:59 AM UTC-4, Dima Pasechnik wrote:
The error in sagenb building is an indication that there was an error earlier on.What does happen if you try starting Sage by doing./sage?
Crash, see attached report.
On Wed, 18 Sep 2019 02:40 Matthias Goerner, <enis...@gmail.com> wrote:
I have been trying to compile sage from source. I tried sage-8.8, then sage-8.9. Both failed:--[sagenb-1.1.2] reading sources... [ 15%] misc/misc[sagenb-1.1.2][sagenb-1.1.2] Exception occurred:[sagenb-1.1.2] File "sage/misc/lazy_import.pyx", line 218, in sage.misc.lazy_import.LazyImport._get_object (build/cythonized/sage/misc/lazy_import.c:2502)[sagenb-1.1.2] raise RuntimeError(f"resolving lazy import {self._name} during startup")[sagenb-1.1.2] RuntimeError: resolving lazy import dumps during startup[sagenb-1.1.2] The full traceback has been saved in /var/folders/qf/wr6_n5s56m780kv130nznmlc0000gn/T/sphinx-err-MzyE1A.log, if you want to report the issue to the developers.[sagenb-1.1.2] Please also report this if it was a user error, so that a better error message can be provided next time.[sagenb-1.1.2] A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!What is going on?
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-...@googlegroups.com.
E. Madison Bray
Sep 18, 2019, 6:10:15 AM9/18/19
to sage-devel
On Wed, Sep 18, 2019 at 11:59 AM Matthias Goerner <enis...@gmail.com> wrote:
>
>
>
> On Wednesday, September 18, 2019 at 2:11:59 AM UTC-4, Dima Pasechnik wrote:
>>
>> The error in sagenb building is an indication that there was an error earlier on.
>>
>> What does happen if you try starting Sage by doing
>>
>> ./sage
>>
>> ?
>
>
> Crash, see attached report.
sqlite module for Python failed to build. This is the same as this
>
>
>
> On Wednesday, September 18, 2019 at 2:11:59 AM UTC-4, Dima Pasechnik wrote:
>>
>> The error in sagenb building is an indication that there was an error earlier on.
>>
>> What does happen if you try starting Sage by doing
>>
>> ./sage
>>
>> ?
>
>
> Crash, see attached report.
thread last month
https://groups.google.com/d/msg/sage-devel/6-vl0CajnVU/hBUxSsrCCAAJ
>> On Wed, 18 Sep 2019 02:40 Matthias Goerner, <enis...@gmail.com> wrote:
>>>
>>> I have been trying to compile sage from source. I tried sage-8.8, then sage-8.9. Both failed:
>>>
>>> [sagenb-1.1.2] reading sources... [ 15%] misc/misc
>>> [sagenb-1.1.2]
>>> [sagenb-1.1.2] Exception occurred:
>>> [sagenb-1.1.2] File "sage/misc/lazy_import.pyx", line 218, in sage.misc.lazy_import.LazyImport._get_object (build/cythonized/sage/misc/lazy_import.c:2502)
>>> [sagenb-1.1.2] raise RuntimeError(f"resolving lazy import {self._name} during startup")
>>> [sagenb-1.1.2] RuntimeError: resolving lazy import dumps during startup
>>> [sagenb-1.1.2] The full traceback has been saved in /var/folders/qf/wr6_n5s56m780kv130nznmlc0000gn/T/sphinx-err-MzyE1A.log, if you want to report the issue to the developers.
>>> [sagenb-1.1.2] Please also report this if it was a user error, so that a better error message can be provided next time.
>>> [sagenb-1.1.2] A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
>>>
>>> What is going on?
>>>
>>> --
>>> 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-...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/8574ac54-9e6c-41bd-bfaa-1f91ad786172%40googlegroups.com.
>
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/1840733c-9511-41de-98ee-595924423769%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages