build error:

Done installing PolyBoRi.
Removing dynamic libraries...
Done removing dynamic libraries.
touch: cannot touch `/home/tarbox/projects/sage-3.1.2.rc1/devel/sage/
sage/rings/polynomial/pbori.pyx': No such file or directory

real    4m46.438s
user    4m26.737s
sys     0m18.829s
sage: An error occurred while installing polybori-0.5rc.p3
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /home/tarbox/projects/sage-3.1.2.rc1/install.log.  Describe your
computer, operating system, etc.
If you want to try to fix the problem, yourself *don't* just cd to
/home/tarbox/projects/sage-3.1.2.rc1/spkg/build/polybori-0.5rc.p3 and
type 'make'.
Instead type "/home/tarbox/projects/sage-3.1.2.rc1/sage -sh"
in order to set all environment variables correctly, then cd to
/home/tarbox/projects/sage-3.1.2.rc1/spkg/build/polybori-0.5rc.p3
(When you are done debugging, you can type "exit" to leave the
subshell.)
make[1]: *** [installed/polybori-0.5rc.p3] Error 1
make[1]: Leaving directory `/home/tarbox/projects/sage-3.1.2.rc1/spkg'
Command exited with non-zero status 2
268.18user 19.08system 4:48.17elapsed 99%CPU (0avgtext+0avgdata
0maxresident)k
112inputs+864168outputs (0major+4562397minor)pagefaults 0swaps

full log at:

http://tarbox.org/sage/install.log.3.1.2.rc1.bz2

-glenn

On Sep 8, 10:33 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> Hello folks,
>
> after the not so great rc0 this one will hopefully work a lot better.
> Most issues beside ghmm and hmm should be fixed. PolyBoRi should
> actually be working and not create random-ish segfaults at exit. We
> also fixed the notebook in secure mode and most of the critical or
> blocker notebook bugs. Please build and test and report any issues.
> Hopefully we will fix the ghmm/hmm Itanium issue tomorrow and move the
> last step toward 3.1.2.final - the release is overdue. I also noticed
> an odd failure in
>
> matrix/matrix_real_double_dense.pyx
>
> on OSX only.
>
> Sources and binaries are in the usual place:
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.2/
>
> Cheers,
>
> Michael
>
> #1785: Alex Ghitza: bug in creating points on elliptic curves over
> extension fields [Reviewed by John Cremona]
> #3711: Mike Hansen: notebook -- folder of worksheets not properly
> saved [Reviewed by Timothy Clemans]
> #3918: Mike Hansen: notebook -- MAJOR BUG involving uploading file
> from URL [Reviewed by Timothy Clemans]
> #4064: Alex Ghitza, John Cremona: fix pari precision issues [Reviewed
> by John Cremona, Alex Ghitza]
> #4070: Michael Abshoff: fix polybori-0.5.rc1 build issues [Reviewed by
> Martin Albrecht]
> #4071: Mike Hansen: Fix issues in the lisp interface [Reviewed by
> Michael Abshoff]
> #4072: Mike Hansen: Fix issue in trait_names in the sage0 interface
> [Reviewed by Martin Albrecht]
> #4073: Martin Albrecht: disable colors in sage0 [Reviewed by Mike
> Hansen]
> #4074: Mike Hansen: the notebook is totally broken in secure mode with
> the new twisted spkg [Reviewed by Michael Abshoff]
> #4075: David Joyner: fix bug in BCHCode [Reviewed by Robert Miller]
> #4077: Mike Hansen: notebook - ReactorNotRunning error consistently
> seen in sage-3.1.2.rc0 [Reviewed by Michael Abshoff]
> #4078: Mike Hansen: evaluate all has sometimes erratic behavior
> [Reviewed by William Stein]
> #4080: Martin Albrecht: Symbol clash between global M4RI and
> PolyBoRi's M4RI [Reviewed by Michael Abshoff]
> #4081: Robert Miller: memleaks in nonlinear binary codes [Reviewed by
> Michael Abshoff]
> #4082: Michael Abshoff: Sage 3.1.2.rc0: numerical noise on OSX/Intel
> in schemes/elliptic_curves/ell_number_field.py [Reviewed by Mike
> Hansen]
> #4084: Jason Merrill: plot(1/cos,-1,1) fails [Reviewed by Michael
> Abshoff]
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to