On Apr 26, 5:54 pm, ugus <[EMAIL PROTECTED]> wrote:
> Hi Michael,
>
> > I would suspect you need to do the following thing:
> > a) cd into $SAGE_ROOT
> > b) source local/bin/sage/env
> > c) patch the python.spkg, then run ./spkg-install from its base
> > directory
> > d) cd into $SAGE_ROOT again
> > e) ./sage -ba
> > f) start sage
> > Have you done those things listed above? If not I would highly
> > recommend that you do the same thing. Since this is interactive it
> > might be best to meet in IRC to see if we cannot figure this out.
>
> You were partly right. After the compilation,
> running "./sage -ba" command additionally in sage_root directory
> solves the problem...However, what strange is that the errors are
> independent from dbm.so: even if dbm.so is compiled correctly or not,
> running /sage -ba removes the errors.
Hi Osman,
Well, something went wrong with the wrong gdbm and if building a
Cython extension fails usually Sage errors out. Looking at the log it
did work for you, so there might be a bug hidden in Sage's build
system somewhere. If you can come up with a reproducible case I can
take another look, but since we are killing the old build system this
or next week anyway I would rather see if the new version catches the
issue than spend a lot of time on debugging the issue.
> Osman
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
