Re: [sage-devel] sagenb failed to build on 8.8.beta3
I've installed (or rather updated) libpng and am attempting to build sage again. I'll post again if there is still a complication. Thanks so much for your efforts! On Friday, May 31, 2019 at 5:10:45 PM UTC-4, Dima Pasechnik wrote: > > On Fri, May 31, 2019 at 9:35 PM 'Justin C. Walker' via sage-devel > > wrote: > > > > > > > > > On May 31, 2019, at 12:02 , Dima Pasechnik > wrote: > > > > > > On Fri, May 31, 2019 at 5:49 PM Colby Kelln > wrote: > > >> > > >> Hi, > > >> > > >> $ pkg-config --libs libpng > > >> > > >> -L/usr/local/Cellar/libpng/1.6.34/lib -lpng16 -lz > > >> > > >> > > >> and > > >> > > >> > > >> $ pkg-config --cflags libpng > > >> > > >> -I/usr/local/Cellar/libpng/1.6.34/include/libpng16 > > > > > > Thanks. Can you just uninstall it? Then building Sage should work one > > > way or another. > > > IIRC, MacOS 10.13/14 has its own libpng, which is good enoug: e.g. > > > Homebrew links its libraries against the system's one, (And if memory > > > fails me here then Sage will biuld its own libpng) > > > > FWIW, I checked my 10.13/14 systems. Neither has libpng (at least, in > /usr/lib). Not sure what the implications are… > > > I probably confused it with ncurses. (Homebrew installs ncurses in > Cellar in order to avoid a conflict with the system - they call such > installs "keg-only"). If so, I don't see a reason libpng is not > installed in /usr/local/, where it would work just fine for Sage. > > Colby, could you perhaps install libpng into the usual /usr/local, and > try again? Thanks. > > > > > Justin > > > > -- > > Justin C. Walker, Curmudgeon at Large > > Institute for the Absorption of Federal Funds > > --- > > I'm beginning to like the cut of his jibberish. > > --- > > > > > > > > -- > > 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 post to this group, send email to sage-...@googlegroups.com > . > > Visit this group at https://groups.google.com/group/sage-devel. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/89524CF4-7CD7-4652-9C21-701C88190A6E%40mac.com. > > > > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/dd3ebe58-99e3-43a7-b5ef-a522f2cd2f14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] sagenb failed to build on 8.8.beta3
On Fri, May 31, 2019 at 9:35 PM 'Justin C. Walker' via sage-devel wrote: > > > > > On May 31, 2019, at 12:02 , Dima Pasechnik wrote: > > > > On Fri, May 31, 2019 at 5:49 PM Colby Kelln wrote: > >> > >> Hi, > >> > >> $ pkg-config --libs libpng > >> > >> -L/usr/local/Cellar/libpng/1.6.34/lib -lpng16 -lz > >> > >> > >> and > >> > >> > >> $ pkg-config --cflags libpng > >> > >> -I/usr/local/Cellar/libpng/1.6.34/include/libpng16 > > > > Thanks. Can you just uninstall it? Then building Sage should work one > > way or another. > > IIRC, MacOS 10.13/14 has its own libpng, which is good enoug: e.g. > > Homebrew links its libraries against the system's one, (And if memory > > fails me here then Sage will biuld its own libpng) > > FWIW, I checked my 10.13/14 systems. Neither has libpng (at least, in > /usr/lib). Not sure what the implications are… > I probably confused it with ncurses. (Homebrew installs ncurses in Cellar in order to avoid a conflict with the system - they call such installs "keg-only"). If so, I don't see a reason libpng is not installed in /usr/local/, where it would work just fine for Sage. Colby, could you perhaps install libpng into the usual /usr/local, and try again? Thanks. > Justin > > -- > Justin C. Walker, Curmudgeon at Large > Institute for the Absorption of Federal Funds > --- > I'm beginning to like the cut of his jibberish. > --- > > > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/89524CF4-7CD7-4652-9C21-701C88190A6E%40mac.com. > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq2%2Bnif2Zv0kQf9Q6GdAGPSaKe5tq4d%3D_0pkz1w0W9FA2g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] sagenb failed to build on 8.8.beta3
> On May 31, 2019, at 12:02 , Dima Pasechnik wrote: > > On Fri, May 31, 2019 at 5:49 PM Colby Kelln wrote: >> >> Hi, >> >> $ pkg-config --libs libpng >> >> -L/usr/local/Cellar/libpng/1.6.34/lib -lpng16 -lz >> >> >> and >> >> >> $ pkg-config --cflags libpng >> >> -I/usr/local/Cellar/libpng/1.6.34/include/libpng16 > > Thanks. Can you just uninstall it? Then building Sage should work one > way or another. > IIRC, MacOS 10.13/14 has its own libpng, which is good enoug: e.g. > Homebrew links its libraries against the system's one, (And if memory > fails me here then Sage will biuld its own libpng) FWIW, I checked my 10.13/14 systems. Neither has libpng (at least, in /usr/lib). Not sure what the implications are… Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds --- I'm beginning to like the cut of his jibberish. --- -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/89524CF4-7CD7-4652-9C21-701C88190A6E%40mac.com. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
On Fri, May 31, 2019 at 5:49 PM Colby Kelln wrote:
>
> Hi,
>
> $ pkg-config --libs libpng
>
> -L/usr/local/Cellar/libpng/1.6.34/lib -lpng16 -lz
>
>
> and
>
>
> $ pkg-config --cflags libpng
>
> -I/usr/local/Cellar/libpng/1.6.34/include/libpng16
Thanks. Can you just uninstall it? Then building Sage should work one
way or another.
IIRC, MacOS 10.13/14 has its own libpng, which is good enoug: e.g.
Homebrew links its libraries against the system's one, (And if memory
fails me here then Sage will biuld its own libpng)
The problem with libpng in /usr/local/Cellar/libpng/1.6.34/ is that
it's a very non-standard location, and
the only way to use it is to either rely on pkg-config all the way, or
copy this location into (say) src/bin//sage-env-config and use it.
Hmm, the current way of using pkg-configure's macros in
spkg-configure.m4 files is flaky:
if the location of the package known to pkg-configure is non-standard,
chances are it won't get picked,
as this libpng example shows...
Dima
>
>
>
> On Friday, May 31, 2019 at 8:22:01 AM UTC-4, Dima Pasechnik wrote:
>>
>> On Fri, May 31, 2019 at 12:54 PM E. Madison Bray wrote:
>> >
>> > On Wed, May 29, 2019 at 2:12 AM Colby Kelln wrote:
>> > >
>> > > Hi,
>> > >
>> > > I'm receiving a similar error message. What exactly did you do to fix
>> > > the problem?
>> > >
>> > > Thanks
>> >
>> > FWIW I also experienced this problem upon updating to 8.8.beta7 on
>> > Cygwin. Possibly for unrelated reasons. Will investigate though.
>>
>> the underlying reason for this error is that $(SAGERUNTIME) (in all
>> the cases I saw it was broken sagelib), which is a dependency of
>> sagenb,
>> is broken at the time sagenb is building.
>>
>> SAGERUNTIME should depend on sage-starts
>> (and this probably is not hard to fix in the main Makefile)
>>
>>
>>
>> >
>> > > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
>> > >>
>> > >> Indeed, sage did not start... After fixing it, sagenb installs.
>> > >>
>> > >> The error message is really confusing.
>> > >>
>> > >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
>> > >> > this error is an indication of an earlier build error. Try starting
>> > >> > sage.
>> > >> >
>> > >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
>> > >> > wrote:
>> > >> >
>> > >> >> Ignore the second e-mail: the error occurred again compiling
>> > >> >> from scratch.
>> > >> >>
>> > >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
>> > >> >>> It appears to be a problem with my setup.
>> > >> >>>
>> > >> >>> I had some Python libraries in my $HOME/.sage/local
>> > >> >>> that made interference with the sage installation.
>> > >> >>>
>> > >> >>> Vincent
>> > >> >>>
>> > >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
>> > >> Dear all,
>> > >>
>> > >> Starting from scratch, I failed to build sagenb. More precisely,
>> > >> it failed building its documentation with
>> > >>
>> > >> Running Sphinx v1.8.5
>> > >> making output directory...
>> > >> building [mo]: targets for 0 po files that are out of date
>> > >> building [html]: targets for 19 source files that are out of date
>> > >> updating environment: 19 added, 0 changed, 0 removed
>> > >> reading sources... [ 5%] index
>> > >> reading sources... [ 10%] misc/introspect
>> > >> reading sources... [ 15%] misc/misc
>> > >>
>> > >> Exception occurred:
>> > >> File "sage/misc/lazy_import.pyx", line 218, in
>> > >> sage.misc.lazy_import.LazyImport._get_object
>> > >> (build/cythonized/sage/misc/lazy_import.c:2495)
>> > >> raise RuntimeError(f"resolving lazy import {self._name}
>> > >> during
>> > >> startup")
>> > >> RuntimeError: resolving lazy import dumps during startup
>> > >>
>> > >> See also the more complete log in attachment.
>> > >>
>> > >> Vincent
>> > >> >>
>> > >> >> --
>> > >> >> 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 post to this group, send email to sage-...@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-...@googlegroups.com.
>> > > To post to this group, send email to sage-...@googlegroups.com.
>> > > Visit this group at https://groups.google.com/group/sage-devel.
>> > > To view this discussion on the web visit
>> > > https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%40googlegrou
Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10
I've encountered similar, but different, problems on a different Linux system. Opened https://trac.sagemath.org/ticket/27907 for this. On Tuesday, May 28, 2019 at 10:15:08 AM UTC-7, Dima Pasechnik wrote: > > On Tue, May 28, 2019 at 6:43 PM Christian Stump > > wrote: > > > > > well, building gcc 7 with a 7-years old complier (gcc version 4.4.7 > > > 20120313 (Red Hat 4.4.7-23), as the log says) > > > probably not possible. > > > Do they have something newer installed? > > > > They did install for me both gcc-7.2.0 (didn't work) and gcc-7.3.0 > (didn't work either). > > > > Let me emphasize again that their setup (with the old gcc 4.x.x) let me > compile a fresh sage-8.6 without any trouble, only when trying sage-8.7, > the error occurs. Doesn't that suggest that the issue is not the old > compiler? > > > the final error in your gcc build log : > > /lib/crti.o: could not read symbols: File in wrong format > > suggests that something is messed up w.r.t. 32- vs 64-bit support. > It probably should have used /lib64/crti.o > > So something is dodgy with the environment on your machine (gfan error > you posted looks of the same sort). > Probably it is assumed you must have something nontrivial in LDFLAGS or > so. > (or maybe you do have something in LDFLAGS or other similar variable > that should not be there) > E.g. gfan did not link to the right libraries for no apparent reason > whatsoever. > > Since 8.6 there were several chnages in how Sage is built, e.g. in the > minimum C++ standard requied (gnu++11 now), some changes in how there > 32- vs 64-bit issues are handled, etc., this might explian why 8.6 > still works. > > > > -- > > 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 post to this group, send email to sage-...@googlegroups.com > . > > Visit this group at https://groups.google.com/group/sage-devel. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/d41ea0d0-d463-4d93-8895-7a4a17802716%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-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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/0fdc02f3-be20-48a8-a148-b88908a935fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
Hi,
$ pkg-config --libs libpng
-L/usr/local/Cellar/libpng/1.6.34/lib -lpng16 -lz
and
$ pkg-config --cflags libpng
-I/usr/local/Cellar/libpng/1.6.34/include/libpng16
On Friday, May 31, 2019 at 8:22:01 AM UTC-4, Dima Pasechnik wrote:
>
> On Fri, May 31, 2019 at 12:54 PM E. Madison Bray > wrote:
> >
> > On Wed, May 29, 2019 at 2:12 AM Colby Kelln > wrote:
> > >
> > > Hi,
> > >
> > > I'm receiving a similar error message. What exactly did you do to fix
> the problem?
> > >
> > > Thanks
> >
> > FWIW I also experienced this problem upon updating to 8.8.beta7 on
> > Cygwin. Possibly for unrelated reasons. Will investigate though.
>
> the underlying reason for this error is that $(SAGERUNTIME) (in all
> the cases I saw it was broken sagelib), which is a dependency of
> sagenb,
> is broken at the time sagenb is building.
>
> SAGERUNTIME should depend on sage-starts
> (and this probably is not hard to fix in the main Makefile)
>
>
>
> >
> > > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
> > >>
> > >> Indeed, sage did not start... After fixing it, sagenb installs.
> > >>
> > >> The error message is really confusing.
> > >>
> > >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
> > >> > this error is an indication of an earlier build error. Try starting
> sage.
> > >> >
> > >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
>
> > >> > wrote:
> > >> >
> > >> >> Ignore the second e-mail: the error occurred again compiling
> > >> >> from scratch.
> > >> >>
> > >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
> > >> >>> It appears to be a problem with my setup.
> > >> >>>
> > >> >>> I had some Python libraries in my $HOME/.sage/local
> > >> >>> that made interference with the sage installation.
> > >> >>>
> > >> >>> Vincent
> > >> >>>
> > >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
> > >> Dear all,
> > >>
> > >> Starting from scratch, I failed to build sagenb. More precisely,
> > >> it failed building its documentation with
> > >>
> > >> Running Sphinx v1.8.5
> > >> making output directory...
> > >> building [mo]: targets for 0 po files that are out of date
> > >> building [html]: targets for 19 source files that are out of
> date
> > >> updating environment: 19 added, 0 changed, 0 removed
> > >> reading sources... [ 5%] index
> > >> reading sources... [ 10%] misc/introspect
> > >> reading sources... [ 15%] misc/misc
> > >>
> > >> Exception occurred:
> > >> File "sage/misc/lazy_import.pyx", line 218, in
> > >> sage.misc.lazy_import.LazyImport._get_object
> > >> (build/cythonized/sage/misc/lazy_import.c:2495)
> > >> raise RuntimeError(f"resolving lazy import {self._name}
> during
> > >> startup")
> > >> RuntimeError: resolving lazy import dumps during startup
> > >>
> > >> See also the more complete log in attachment.
> > >>
> > >> Vincent
> > >> >>
> > >> >> --
> > >> >> 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 post to this group, send email to sage-...@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-...@googlegroups.com .
> > > To post to this group, send email to sage-...@googlegroups.com
> .
> > > Visit this group at https://groups.google.com/group/sage-devel.
> > > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%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-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to sage-...@googlegroups.com .
> > To post to this group, send email to sage-...@googlegroups.com
> .
> > Visit this group at https://groups.google.com/group/sage-devel.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAOTD34Zw48dMEZ3w%3DwiQgRZwkMaBhikU71H-ihOsh%3DC%3DJXWOxw%40mail.gmail.com.
>
>
> > 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 s
Re: [sage-devel] Continuous benchmarking
On Thu, May 30, 2019 at 8:07 AM Samuel Lelièvre wrote: > > Dear sage-devel, > > This blog post on continuous benchmarking looks interesting! > > https://medium.com/@wolfv/building-an-open-source-continuous-benchmark-system-717839093962 > > There have been related discussions on this list in the past, > for example around airspeed velocity: > > https://groups.google.com/forum/#!searchin/sage-devel/airspeed$20velocity%7Csort:date I agree of course per previous discussions about it. It would be nice to have the infrastructure to do continuous *anything* outside the Sage buildbots. I've all but given up on Paris-Sud's OpenStack infrastructure. Everything I try to do with it regarding CI (be it the Cygwin buildbot, or gitlab runners) breaks constantly and I don't think it's anything I'm doing wrong. E.g. recently (within the last few weeks) they seem to have fiddled with some firewall rules such that now it terminates long-running TCP/IP connections. At least, that's my guess. I haven't been able to investigate thoroughly yet but it's basically causing all my CI processes to lose connections with their master servers mid-build. We need reliable infrastructure for Sage builds. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34ZS3fPN8MYAhmaDshaCYtyT-Fdu7p6tz7--Spf%2B0H77eQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] error building sage for Scientific Linux 7.6
Are you trying to upgrade from some old, partial build? Or is this a fresh build from scratch? If the former, I would just run `make distclean` and start again. On Thu, May 30, 2019 at 9:51 PM Charles Campbell wrote: > > Been trying to build sage 8.7 under Scientific Linux (a redhat derivative); > actually, I've tried to do so on and off for several years with no success > ever. I've installed openblas.x86_64 already. > > From make: > > The following package(s) may have failed to build (not necessarily > during this run of 'make all-start'): > > * package: openblas-0.3.5.p0 > log file: /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/openblas-0.3.5.p0.log > build directory: > /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/openblas-0.3.5.p0 > > * package: pari_seadata_small-20090618.p0 > log file: > /home/cecbkup/SW/SAGE/sage-8.7/logs/pkgs/pari_seadata_small-20090618.p0.log > build directory: > /home/cecbkup/SW/SAGE/sage-8.7/local/var/tmp/sage/build/pari_seadata_small-20090618.p0 > > I have no idea where pari... comes from; yum -y list shows > > opari2.x86_64 1.1.2-3.el7epel > paris-traceroute.x86_64 0.92-6.el7 epel > > Neither of which are "pari", although perhaps "opari..." is close. > > Regards, > Charles Campbell > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/f087424b-b8a3-4f86-854c-fd2372695f81%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-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. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34bp19BOZGUDNnxu6%2BA9iU2kEVZdOn%2BSYkae3QxUvamwUQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
On Fri, May 31, 2019 at 2:51 PM Dima Pasechnik wrote:
>
> For Colby, it's broken matrix_mod2_dense.so, due to libgd, which got
> built without libpng.
> A result of a failed attempt to use libpng from the "system" - I guess
> Homebrew or a similar thing.
In my case it was *not* trying to use the libpng from the system.
That, or maybe I have a libgd that was originally linked against a
system libpng (e.g. while testing spkg-configure) but is now linking
to my Sage libpng. I'll have to do some log archaeology to figure out
what happened: I've been preoccupied with other madness the last two
weeks and have barely had any time to work on Sage, so I'm not sure
exactly where I left things :(
> On Fri, May 31, 2019 at 1:47 PM E. Madison Bray wrote:
> >
> > On Fri, May 31, 2019 at 2:22 PM Dima Pasechnik wrote:
> > >
> > > On Fri, May 31, 2019 at 12:54 PM E. Madison Bray
> > > wrote:
> > > >
> > > > On Wed, May 29, 2019 at 2:12 AM Colby Kelln wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I'm receiving a similar error message. What exactly did you do to fix
> > > > > the problem?
> > > > >
> > > > > Thanks
> > > >
> > > > FWIW I also experienced this problem upon updating to 8.8.beta7 on
> > > > Cygwin. Possibly for unrelated reasons. Will investigate though.
> > >
> > > the underlying reason for this error is that $(SAGERUNTIME) (in all
> > > the cases I saw it was broken sagelib), which is a dependency of
> > > sagenb,
> > > is broken at the time sagenb is building.
> > >
> > > SAGERUNTIME should depend on sage-starts
> > > (and this probably is not hard to fix in the main Makefile)
> >
> > Yes, I suppose. But that's less interesting: The problem is why is
> > Sage failing to start? In my case it's because the DLL for
> > sage.matrix.matrix_mod2_dense cannot be loaded, either due to a
> > missing dependency or some DLL incompatibility hell. It's hard to be
> > certain why I'm just getting this *now* though upon upgrading from
> > 8.8.beta6 (which worked, I think) to 8.8.beta7. I don't see that much
> > changed. maxima was upgraded as was gmpy2. That shouldn't have
> > broken loading of this DLL.
> >
> >
> > > > > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
> > > > >>
> > > > >> Indeed, sage did not start... After fixing it, sagenb installs.
> > > > >>
> > > > >> The error message is really confusing.
> > > > >>
> > > > >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
> > > > >> > this error is an indication of an earlier build error. Try
> > > > >> > starting sage.
> > > > >> >
> > > > >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
> > > > >> > wrote:
> > > > >> >
> > > > >> >> Ignore the second e-mail: the error occurred again compiling
> > > > >> >> from scratch.
> > > > >> >>
> > > > >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
> > > > >> >>> It appears to be a problem with my setup.
> > > > >> >>>
> > > > >> >>> I had some Python libraries in my $HOME/.sage/local
> > > > >> >>> that made interference with the sage installation.
> > > > >> >>>
> > > > >> >>> Vincent
> > > > >> >>>
> > > > >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
> > > > >> Dear all,
> > > > >>
> > > > >> Starting from scratch, I failed to build sagenb. More precisely,
> > > > >> it failed building its documentation with
> > > > >>
> > > > >> Running Sphinx v1.8.5
> > > > >> making output directory...
> > > > >> building [mo]: targets for 0 po files that are out of date
> > > > >> building [html]: targets for 19 source files that are out of
> > > > >> date
> > > > >> updating environment: 19 added, 0 changed, 0 removed
> > > > >> reading sources... [ 5%] index
> > > > >> reading sources... [ 10%] misc/introspect
> > > > >> reading sources... [ 15%] misc/misc
> > > > >>
> > > > >> Exception occurred:
> > > > >> File "sage/misc/lazy_import.pyx", line 218, in
> > > > >> sage.misc.lazy_import.LazyImport._get_object
> > > > >> (build/cythonized/sage/misc/lazy_import.c:2495)
> > > > >> raise RuntimeError(f"resolving lazy import {self._name}
> > > > >> during
> > > > >> startup")
> > > > >> RuntimeError: resolving lazy import dumps during startup
> > > > >>
> > > > >> See also the more complete log in attachment.
> > > > >>
> > > > >> Vincent
> > > > >> >>
> > > > >> >> --
> > > > >> >> 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 post to this group, send email to sage-...@googlegroups.com.
> > > > >> >> Visit this group at https://groups.google.com/group/sage-devel.
> > > > >> >> For more options, visit https://groups.google.com/d/optout.
> > > > >> >>
> > > >
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
libd happily builds without libpng.
and this beta does allow from libpng to come from the system.
On Fri, May 31, 2019 at 1:50 PM E. Madison Bray wrote:
>
> On Fri, May 31, 2019 at 2:47 PM E. Madison Bray wrote:
> >
> > On Fri, May 31, 2019 at 2:22 PM Dima Pasechnik wrote:
> > >
> > > On Fri, May 31, 2019 at 12:54 PM E. Madison Bray
> > > wrote:
> > > >
> > > > On Wed, May 29, 2019 at 2:12 AM Colby Kelln wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I'm receiving a similar error message. What exactly did you do to fix
> > > > > the problem?
> > > > >
> > > > > Thanks
> > > >
> > > > FWIW I also experienced this problem upon updating to 8.8.beta7 on
> > > > Cygwin. Possibly for unrelated reasons. Will investigate though.
> > >
> > > the underlying reason for this error is that $(SAGERUNTIME) (in all
> > > the cases I saw it was broken sagelib), which is a dependency of
> > > sagenb,
> > > is broken at the time sagenb is building.
> > >
> > > SAGERUNTIME should depend on sage-starts
> > > (and this probably is not hard to fix in the main Makefile)
> >
> > Yes, I suppose. But that's less interesting: The problem is why is
> > Sage failing to start? In my case it's because the DLL for
> > sage.matrix.matrix_mod2_dense cannot be loaded, either due to a
> > missing dependency or some DLL incompatibility hell. It's hard to be
> > certain why I'm just getting this *now* though upon upgrading from
> > 8.8.beta6 (which worked, I think) to 8.8.beta7. I don't see that much
> > changed. maxima was upgraded as was gmpy2. That shouldn't have
> > broken loading of this DLL.
>
> Now, looking at Colby's sage crash log, it was also a problem loading
> the same module (except on MacOS, so it's maybe not purely a Cygwin
> problem). In her case she got: _gdImageCreateFromPng
>
> Unfortunately Cygwin won't tell me why the DLL load failed exactly but
> it could also be the same missing symbol. I'll have to check. Why
> would there be a missing _gdImageCreateFromPng? I thought we didn't
> change anything about libgd (yet, unless I'm missing something), and I
> have the Sage SPKG for it installed currently.
>
>
> > > > > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
> > > > >>
> > > > >> Indeed, sage did not start... After fixing it, sagenb installs.
> > > > >>
> > > > >> The error message is really confusing.
> > > > >>
> > > > >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
> > > > >> > this error is an indication of an earlier build error. Try
> > > > >> > starting sage.
> > > > >> >
> > > > >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
> > > > >> > wrote:
> > > > >> >
> > > > >> >> Ignore the second e-mail: the error occurred again compiling
> > > > >> >> from scratch.
> > > > >> >>
> > > > >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
> > > > >> >>> It appears to be a problem with my setup.
> > > > >> >>>
> > > > >> >>> I had some Python libraries in my $HOME/.sage/local
> > > > >> >>> that made interference with the sage installation.
> > > > >> >>>
> > > > >> >>> Vincent
> > > > >> >>>
> > > > >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
> > > > >> Dear all,
> > > > >>
> > > > >> Starting from scratch, I failed to build sagenb. More precisely,
> > > > >> it failed building its documentation with
> > > > >>
> > > > >> Running Sphinx v1.8.5
> > > > >> making output directory...
> > > > >> building [mo]: targets for 0 po files that are out of date
> > > > >> building [html]: targets for 19 source files that are out of
> > > > >> date
> > > > >> updating environment: 19 added, 0 changed, 0 removed
> > > > >> reading sources... [ 5%] index
> > > > >> reading sources... [ 10%] misc/introspect
> > > > >> reading sources... [ 15%] misc/misc
> > > > >>
> > > > >> Exception occurred:
> > > > >> File "sage/misc/lazy_import.pyx", line 218, in
> > > > >> sage.misc.lazy_import.LazyImport._get_object
> > > > >> (build/cythonized/sage/misc/lazy_import.c:2495)
> > > > >> raise RuntimeError(f"resolving lazy import {self._name}
> > > > >> during
> > > > >> startup")
> > > > >> RuntimeError: resolving lazy import dumps during startup
> > > > >>
> > > > >> See also the more complete log in attachment.
> > > > >>
> > > > >> Vincent
> > > > >> >>
> > > > >> >> --
> > > > >> >> 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 post to this group, send email to sage-...@googlegroups.com.
> > > > >> >> Visit this group at https://groups.google.com/group/sage-devel.
> > > > >> >> For more options, visit https://groups.google.com/d/optout.
> > > > >> >>
> > > > >> >
> >
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
For Colby, it's broken matrix_mod2_dense.so, due to libgd, which got
built without libpng.
A result of a failed attempt to use libpng from the "system" - I guess
Homebrew or a similar thing.
On Fri, May 31, 2019 at 1:47 PM E. Madison Bray wrote:
>
> On Fri, May 31, 2019 at 2:22 PM Dima Pasechnik wrote:
> >
> > On Fri, May 31, 2019 at 12:54 PM E. Madison Bray
> > wrote:
> > >
> > > On Wed, May 29, 2019 at 2:12 AM Colby Kelln wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm receiving a similar error message. What exactly did you do to fix
> > > > the problem?
> > > >
> > > > Thanks
> > >
> > > FWIW I also experienced this problem upon updating to 8.8.beta7 on
> > > Cygwin. Possibly for unrelated reasons. Will investigate though.
> >
> > the underlying reason for this error is that $(SAGERUNTIME) (in all
> > the cases I saw it was broken sagelib), which is a dependency of
> > sagenb,
> > is broken at the time sagenb is building.
> >
> > SAGERUNTIME should depend on sage-starts
> > (and this probably is not hard to fix in the main Makefile)
>
> Yes, I suppose. But that's less interesting: The problem is why is
> Sage failing to start? In my case it's because the DLL for
> sage.matrix.matrix_mod2_dense cannot be loaded, either due to a
> missing dependency or some DLL incompatibility hell. It's hard to be
> certain why I'm just getting this *now* though upon upgrading from
> 8.8.beta6 (which worked, I think) to 8.8.beta7. I don't see that much
> changed. maxima was upgraded as was gmpy2. That shouldn't have
> broken loading of this DLL.
>
>
> > > > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
> > > >>
> > > >> Indeed, sage did not start... After fixing it, sagenb installs.
> > > >>
> > > >> The error message is really confusing.
> > > >>
> > > >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
> > > >> > this error is an indication of an earlier build error. Try starting
> > > >> > sage.
> > > >> >
> > > >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> >> Ignore the second e-mail: the error occurred again compiling
> > > >> >> from scratch.
> > > >> >>
> > > >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
> > > >> >>> It appears to be a problem with my setup.
> > > >> >>>
> > > >> >>> I had some Python libraries in my $HOME/.sage/local
> > > >> >>> that made interference with the sage installation.
> > > >> >>>
> > > >> >>> Vincent
> > > >> >>>
> > > >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
> > > >> Dear all,
> > > >>
> > > >> Starting from scratch, I failed to build sagenb. More precisely,
> > > >> it failed building its documentation with
> > > >>
> > > >> Running Sphinx v1.8.5
> > > >> making output directory...
> > > >> building [mo]: targets for 0 po files that are out of date
> > > >> building [html]: targets for 19 source files that are out of date
> > > >> updating environment: 19 added, 0 changed, 0 removed
> > > >> reading sources... [ 5%] index
> > > >> reading sources... [ 10%] misc/introspect
> > > >> reading sources... [ 15%] misc/misc
> > > >>
> > > >> Exception occurred:
> > > >> File "sage/misc/lazy_import.pyx", line 218, in
> > > >> sage.misc.lazy_import.LazyImport._get_object
> > > >> (build/cythonized/sage/misc/lazy_import.c:2495)
> > > >> raise RuntimeError(f"resolving lazy import {self._name}
> > > >> during
> > > >> startup")
> > > >> RuntimeError: resolving lazy import dumps during startup
> > > >>
> > > >> See also the more complete log in attachment.
> > > >>
> > > >> Vincent
> > > >> >>
> > > >> >> --
> > > >> >> 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 post to this group, send email to sage-...@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.
> > > > To view this discussion on the web visit
> > > > https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%40googlegroups.com.
> > > > For more options, visit https://groups.google.com/d/optout.
> > >
> > > --
> > > You received this message because you are subscribed to
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
On Fri, May 31, 2019 at 2:47 PM E. Madison Bray wrote:
>
> On Fri, May 31, 2019 at 2:22 PM Dima Pasechnik wrote:
> >
> > On Fri, May 31, 2019 at 12:54 PM E. Madison Bray
> > wrote:
> > >
> > > On Wed, May 29, 2019 at 2:12 AM Colby Kelln wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm receiving a similar error message. What exactly did you do to fix
> > > > the problem?
> > > >
> > > > Thanks
> > >
> > > FWIW I also experienced this problem upon updating to 8.8.beta7 on
> > > Cygwin. Possibly for unrelated reasons. Will investigate though.
> >
> > the underlying reason for this error is that $(SAGERUNTIME) (in all
> > the cases I saw it was broken sagelib), which is a dependency of
> > sagenb,
> > is broken at the time sagenb is building.
> >
> > SAGERUNTIME should depend on sage-starts
> > (and this probably is not hard to fix in the main Makefile)
>
> Yes, I suppose. But that's less interesting: The problem is why is
> Sage failing to start? In my case it's because the DLL for
> sage.matrix.matrix_mod2_dense cannot be loaded, either due to a
> missing dependency or some DLL incompatibility hell. It's hard to be
> certain why I'm just getting this *now* though upon upgrading from
> 8.8.beta6 (which worked, I think) to 8.8.beta7. I don't see that much
> changed. maxima was upgraded as was gmpy2. That shouldn't have
> broken loading of this DLL.
Now, looking at Colby's sage crash log, it was also a problem loading
the same module (except on MacOS, so it's maybe not purely a Cygwin
problem). In her case she got: _gdImageCreateFromPng
Unfortunately Cygwin won't tell me why the DLL load failed exactly but
it could also be the same missing symbol. I'll have to check. Why
would there be a missing _gdImageCreateFromPng? I thought we didn't
change anything about libgd (yet, unless I'm missing something), and I
have the Sage SPKG for it installed currently.
> > > > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
> > > >>
> > > >> Indeed, sage did not start... After fixing it, sagenb installs.
> > > >>
> > > >> The error message is really confusing.
> > > >>
> > > >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
> > > >> > this error is an indication of an earlier build error. Try starting
> > > >> > sage.
> > > >> >
> > > >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> >> Ignore the second e-mail: the error occurred again compiling
> > > >> >> from scratch.
> > > >> >>
> > > >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
> > > >> >>> It appears to be a problem with my setup.
> > > >> >>>
> > > >> >>> I had some Python libraries in my $HOME/.sage/local
> > > >> >>> that made interference with the sage installation.
> > > >> >>>
> > > >> >>> Vincent
> > > >> >>>
> > > >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
> > > >> Dear all,
> > > >>
> > > >> Starting from scratch, I failed to build sagenb. More precisely,
> > > >> it failed building its documentation with
> > > >>
> > > >> Running Sphinx v1.8.5
> > > >> making output directory...
> > > >> building [mo]: targets for 0 po files that are out of date
> > > >> building [html]: targets for 19 source files that are out of date
> > > >> updating environment: 19 added, 0 changed, 0 removed
> > > >> reading sources... [ 5%] index
> > > >> reading sources... [ 10%] misc/introspect
> > > >> reading sources... [ 15%] misc/misc
> > > >>
> > > >> Exception occurred:
> > > >> File "sage/misc/lazy_import.pyx", line 218, in
> > > >> sage.misc.lazy_import.LazyImport._get_object
> > > >> (build/cythonized/sage/misc/lazy_import.c:2495)
> > > >> raise RuntimeError(f"resolving lazy import {self._name}
> > > >> during
> > > >> startup")
> > > >> RuntimeError: resolving lazy import dumps during startup
> > > >>
> > > >> See also the more complete log in attachment.
> > > >>
> > > >> Vincent
> > > >> >>
> > > >> >> --
> > > >> >> 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 post to this group, send email to sage-...@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.c
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
On Fri, May 31, 2019 at 2:22 PM Dima Pasechnik wrote:
>
> On Fri, May 31, 2019 at 12:54 PM E. Madison Bray
> wrote:
> >
> > On Wed, May 29, 2019 at 2:12 AM Colby Kelln wrote:
> > >
> > > Hi,
> > >
> > > I'm receiving a similar error message. What exactly did you do to fix the
> > > problem?
> > >
> > > Thanks
> >
> > FWIW I also experienced this problem upon updating to 8.8.beta7 on
> > Cygwin. Possibly for unrelated reasons. Will investigate though.
>
> the underlying reason for this error is that $(SAGERUNTIME) (in all
> the cases I saw it was broken sagelib), which is a dependency of
> sagenb,
> is broken at the time sagenb is building.
>
> SAGERUNTIME should depend on sage-starts
> (and this probably is not hard to fix in the main Makefile)
Yes, I suppose. But that's less interesting: The problem is why is
Sage failing to start? In my case it's because the DLL for
sage.matrix.matrix_mod2_dense cannot be loaded, either due to a
missing dependency or some DLL incompatibility hell. It's hard to be
certain why I'm just getting this *now* though upon upgrading from
8.8.beta6 (which worked, I think) to 8.8.beta7. I don't see that much
changed. maxima was upgraded as was gmpy2. That shouldn't have
broken loading of this DLL.
> > > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
> > >>
> > >> Indeed, sage did not start... After fixing it, sagenb installs.
> > >>
> > >> The error message is really confusing.
> > >>
> > >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
> > >> > this error is an indication of an earlier build error. Try starting
> > >> > sage.
> > >> >
> > >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
> > >> > wrote:
> > >> >
> > >> >> Ignore the second e-mail: the error occurred again compiling
> > >> >> from scratch.
> > >> >>
> > >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
> > >> >>> It appears to be a problem with my setup.
> > >> >>>
> > >> >>> I had some Python libraries in my $HOME/.sage/local
> > >> >>> that made interference with the sage installation.
> > >> >>>
> > >> >>> Vincent
> > >> >>>
> > >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
> > >> Dear all,
> > >>
> > >> Starting from scratch, I failed to build sagenb. More precisely,
> > >> it failed building its documentation with
> > >>
> > >> Running Sphinx v1.8.5
> > >> making output directory...
> > >> building [mo]: targets for 0 po files that are out of date
> > >> building [html]: targets for 19 source files that are out of date
> > >> updating environment: 19 added, 0 changed, 0 removed
> > >> reading sources... [ 5%] index
> > >> reading sources... [ 10%] misc/introspect
> > >> reading sources... [ 15%] misc/misc
> > >>
> > >> Exception occurred:
> > >> File "sage/misc/lazy_import.pyx", line 218, in
> > >> sage.misc.lazy_import.LazyImport._get_object
> > >> (build/cythonized/sage/misc/lazy_import.c:2495)
> > >> raise RuntimeError(f"resolving lazy import {self._name} during
> > >> startup")
> > >> RuntimeError: resolving lazy import dumps during startup
> > >>
> > >> See also the more complete log in attachment.
> > >>
> > >> Vincent
> > >> >>
> > >> >> --
> > >> >> 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 post to this group, send email to sage-...@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.
> > > To view this discussion on the web visit
> > > https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%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-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.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/sage-devel/CAOTD34Zw48dMEZ3w%3DwiQgRZwkMaBhikU71H-ihOsh%3DC%3DJXWOxw%40mail.gmail.com.
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
On Fri, May 31, 2019 at 12:54 PM E. Madison Bray wrote:
>
> On Wed, May 29, 2019 at 2:12 AM Colby Kelln wrote:
> >
> > Hi,
> >
> > I'm receiving a similar error message. What exactly did you do to fix the
> > problem?
> >
> > Thanks
>
> FWIW I also experienced this problem upon updating to 8.8.beta7 on
> Cygwin. Possibly for unrelated reasons. Will investigate though.
the underlying reason for this error is that $(SAGERUNTIME) (in all
the cases I saw it was broken sagelib), which is a dependency of
sagenb,
is broken at the time sagenb is building.
SAGERUNTIME should depend on sage-starts
(and this probably is not hard to fix in the main Makefile)
>
> > On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
> >>
> >> Indeed, sage did not start... After fixing it, sagenb installs.
> >>
> >> The error message is really confusing.
> >>
> >> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
> >> > this error is an indication of an earlier build error. Try starting sage.
> >> >
> >> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
> >> > wrote:
> >> >
> >> >> Ignore the second e-mail: the error occurred again compiling
> >> >> from scratch.
> >> >>
> >> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
> >> >>> It appears to be a problem with my setup.
> >> >>>
> >> >>> I had some Python libraries in my $HOME/.sage/local
> >> >>> that made interference with the sage installation.
> >> >>>
> >> >>> Vincent
> >> >>>
> >> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
> >> Dear all,
> >>
> >> Starting from scratch, I failed to build sagenb. More precisely,
> >> it failed building its documentation with
> >>
> >> Running Sphinx v1.8.5
> >> making output directory...
> >> building [mo]: targets for 0 po files that are out of date
> >> building [html]: targets for 19 source files that are out of date
> >> updating environment: 19 added, 0 changed, 0 removed
> >> reading sources... [ 5%] index
> >> reading sources... [ 10%] misc/introspect
> >> reading sources... [ 15%] misc/misc
> >>
> >> Exception occurred:
> >> File "sage/misc/lazy_import.pyx", line 218, in
> >> sage.misc.lazy_import.LazyImport._get_object
> >> (build/cythonized/sage/misc/lazy_import.c:2495)
> >> raise RuntimeError(f"resolving lazy import {self._name} during
> >> startup")
> >> RuntimeError: resolving lazy import dumps during startup
> >>
> >> See also the more complete log in attachment.
> >>
> >> Vincent
> >> >>
> >> >> --
> >> >> 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 post to this group, send email to sage-...@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.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%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-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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAOTD34Zw48dMEZ3w%3DwiQgRZwkMaBhikU71H-ihOsh%3DC%3DJXWOxw%40mail.gmail.com.
> 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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAAWYfq12YRTSgj057YQSTMf06zy2d9WnWpsQ6nb4iPjS8E8MTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
On Wed, May 29, 2019 at 2:12 AM Colby Kelln wrote:
>
> Hi,
>
> I'm receiving a similar error message. What exactly did you do to fix the
> problem?
>
> Thanks
FWIW I also experienced this problem upon updating to 8.8.beta7 on
Cygwin. Possibly for unrelated reasons. Will investigate though.
> On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
>>
>> Indeed, sage did not start... After fixing it, sagenb installs.
>>
>> The error message is really confusing.
>>
>> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
>> > this error is an indication of an earlier build error. Try starting sage.
>> >
>> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
>> > wrote:
>> >
>> >> Ignore the second e-mail: the error occurred again compiling
>> >> from scratch.
>> >>
>> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
>> >>> It appears to be a problem with my setup.
>> >>>
>> >>> I had some Python libraries in my $HOME/.sage/local
>> >>> that made interference with the sage installation.
>> >>>
>> >>> Vincent
>> >>>
>> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
>> Dear all,
>>
>> Starting from scratch, I failed to build sagenb. More precisely,
>> it failed building its documentation with
>>
>> Running Sphinx v1.8.5
>> making output directory...
>> building [mo]: targets for 0 po files that are out of date
>> building [html]: targets for 19 source files that are out of date
>> updating environment: 19 added, 0 changed, 0 removed
>> reading sources... [ 5%] index
>> reading sources... [ 10%] misc/introspect
>> reading sources... [ 15%] misc/misc
>>
>> Exception occurred:
>> File "sage/misc/lazy_import.pyx", line 218, in
>> sage.misc.lazy_import.LazyImport._get_object
>> (build/cythonized/sage/misc/lazy_import.c:2495)
>> raise RuntimeError(f"resolving lazy import {self._name} during
>> startup")
>> RuntimeError: resolving lazy import dumps during startup
>>
>> See also the more complete log in attachment.
>>
>> Vincent
>> >>
>> >> --
>> >> 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 post to this group, send email to sage-...@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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%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-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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAOTD34Zw48dMEZ3w%3DwiQgRZwkMaBhikU71H-ihOsh%3DC%3DJXWOxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: sagenb failed to build on 8.8.beta3
On Thu, May 30, 2019 at 11:14 PM Colby Kelln wrote: > > I do not have a libpng*.log file. What does this indicate? this, as well as your config.log, says that a good libpng was found on your system, but for some reason libgd was not able to find it. I presume that it was found in an installation of MacPorts, or Homebrew, or Anaconda, or some other similar pseudo-distribution like this. Youl also appear to have gfortran installed there. Please provide this information to us (while none of these are officially supported, I was able to build Sage with Homebrew packages). I guess you have Homebrew, just from the value of PATH you have in config.log What is the output of $ pkg-config --libs libpng $ pkg-config --cflags libpng (in case you have pkg-config installed) if you run Homebrew, I'd recommend you install pkg-config. Thanks. I appreciate your patience. We really should get Homebrew better supported, with official instructions on what needs to be installed to build Sage... PS. In case you just want to install Sage quickly, you could install Sage's libpng: ./sage -i libpng libgd followed up by make HTH Dima > > I've attached my config.log which says 8.8.beta6. > > Thanks again for your help. > > On Thursday, May 30, 2019 at 6:02:47 PM UTC-4, Dima Pasechnik wrote: >> >> OK, in your log of libgd I see >> >> ** Configuration summary for libgd ..: >> >> >>Support for PNG library: no >> ... >> >> whereas it must have been yes. >> >> And the output of >> >> $ otool -L local/lib/libgd.3.dylib >> >> confirms that libpng was not linked to libgd. This is the cause of the error. >> We should fix it. I've opened https://trac.sagemath.org/ticket/27901 >> >> Could you please post the log for libpng >> logs/pkgs/libpng*.log ? >> >> You have not mentioned the exact version of Sage you are trying to build. >> What is it? 8.7? A recent beta? >> (please post the config.log from the Sage's main directory) >> >> Thanks. >> >> On Thu, May 30, 2019 at 10:34 PM Dima Pasechnik wrote: >> > >> > hmm, this looks OK too. >> > What is the output of >> > >> > otool -L local/lib/libgd.3.dylib >> > >> > Thanks. >> > >> > On Thu, May 30, 2019 at 10:15 PM Colby Kelln wrote: >> > > >> > > $ otool -L >> > > local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so >> > > >> > > local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so: >> > > >> > > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgmp.23.dylib >> > > (compatibility version 24.0.0, current version 24.3.0) >> > > >> > > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libm4ri-0.0.20140914.dylib >> > > (compatibility version 0.0.0, current version 0.0.0) >> > > >> > > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libgd.3.dylib >> > > (compatibility version 4.0.0, current version 4.0.0) >> > > >> > > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version >> > > 1252.250.1) >> > > >> > > /Users/Colby/Documents/Math/ICERM2019/sage_stuff/local/lib/libpari-gmp.dylib >> > > (compatibility version 2.11.0, current version 2.11.1) >> > > >> > > >> > > On Thursday, May 30, 2019 at 3:47:46 PM UTC-4, Dima Pasechnik wrote: >> > >> >> > >> Thanks, this looks in order. Could you please post the output of >> > >> >> > >> otool -L >> > >> local/lib/python2.7/site-packages/sage/matrix/matrix_mod2_dense.so >> > >> >> > >> I suspect it is linked to a "wrong" libgd. >> > >> >> > >> >> > >> On Thu, May 30, 2019 at 6:51 PM Colby Kelln wrote: >> > >> > >> > >> > I'm nearly certain this is the file you asked for; if not, let me >> > >> > know. I appreciate your help. >> > >> > >> > >> > On Thursday, May 30, 2019 at 4:44:18 AM UTC-4, Dima Pasechnik wrote: >> > >> >> >> > >> >> Thanks. sagenb is a package that depends on sage, and sage should >> > >> >> better be in working order at the moment it is built. >> > >> >> >> > >> >> the error message in the log indicates that perhaps libgd, another >> > >> >> package, has not been built correctly. >> > >> >> Could you post log of it, logs/pkgs/libgd*.log ? >> > >> >> >> > >> >> thanks. >> > >> >> >> > >> >> On Thu, 30 May 2019 05:39 Colby Kelln, wrote: >> > >> >>> >> > >> >>> The error message reads: >> > >> >>> >> > >> >>> Error installing package sagenb-1.1.2 >> > >> >>> >> > >> >>> >> > >> >>> So I've attached the sagenb-1.1.2 log file. >> > >> >>> If it's relevant, the output also reads: >> > >> >>> >> > >> >>> RuntimeError: resolving lazy import dumps during startup >> > >> >>> >> > >> >>> >> > >> >>> These errors occur just when building sage. I also attempted to run >> > >> >>> sage to see if that gave more info and I attached the crash report. >> > >> >>> Thanks, again. >> > >> >>> >> > >> >>> >> > >> >>> On Wednesday, May 29, 2019 at 3:43:35 AM UTC-4, Dima Pasechnik >> > >> >>> wrote: >> > >> >> > >> On Wed, May 29, 2019 at 2:12 AM Colby Kelln >> > >> wrote: >> > >> > >> > >> >>>
