#8192: Update PolyBoRi to newest upstream release
--------------------------+-------------------------------------------------
 Reporter:  malb          |         Owner:  PolyBoRi                       
     Type:  enhancement   |        Status:  closed                         
 Priority:  major         |     Milestone:  sage-4.4.1                     
Component:  packages      |    Resolution:  fixed                          
 Keywords:                |        Author:  Alexander Dreyer, Burcin Erocal
 Upstream:  N/A           |      Reviewer:  Martin Albrecht                
   Merged:  4.4.1.alpha1  |   Work_issues:                                 
--------------------------+-------------------------------------------------

Comment(by mvngu):

 From [http://groups.google.com/group/sage-
 devel/browse_thread/thread/ff294013a41ea05c sage-devel]:
 [[BR]]

 Sage 4.4.1.alpha2 contains two !PolyBoRi spkg's:

  * polybori-0.6.3-20091028.spkg
  * polybori-0.6.4.spkg

 I think polybori-0.6.4.spkg is the newer one, so I deleted the other one
 from `SAGE_ROOT/spkg/standard/`. Here's a diff between the `spkg-install`
 of polybori-0.6.3-20091028.spkg and polybori-0.6.4.spkg:

 {{{
 #!diff
 [mv...@sage mvngu]$ diff -Naur polybori-0.6.3-20091028/spkg-install
 polybori-0.6.4.p0/spkg-install
 --- polybori-0.6.3-20091028/spkg-install        2009-05-17
 10:31:16.000000000 -0700
 +++ polybori-0.6.4.p0/spkg-install      2010-04-29 07:10:46.000000000
 -0700
 @@ -6,14 +6,14 @@
     exit 1
  fi

 -PBDIR=polybori-0.6
 +PBDIR=polybori-0.6.4
  WORKDIR=${PWD}/src
  SCONS=scons

  # For some strange reason the installed boost in $SAGE_LOCAL causes
  # make install failures, so copy it over.
 -mkdir src/boost_1_34_1.cropped
 -cp -r $SAGE_LOCAL/include/boost src/boost_1_34_1.cropped
 +#mkdir src/boost_1_34_1.cropped
 +#cp -r $SAGE_LOCAL/include/boost src/boost_1_34_1.cropped
  BOOSTDIR=boost_1_34_1.cropped

  patch()
 @@ -26,9 +26,6 @@

      cp patches/SConstruct src/${PBDIR}/SConstruct
      cp patches/PyPolyBoRi.py src/${PBDIR}/pyroot/polybori
 -
 -    # workaround so will build on cygwin
 -    cp patches/cpu_stats.c src/${PBDIR}/Cudd/util/cpu_stats.c
  }


 @@ -68,7 +65,7 @@

  remove_dylib()
  {
 -    # linking dynmic libraries causes segfaults at exit (see #2822)
 +    # linking dynamic libraries causes segfaults at exit (see #2822)
      if [ `uname` = "Darwin" ]; then
          rm -f $SAGE_LOCAL/lib/libpolybori.dylib
          rm -f $SAGE_LOCAL/lib/libpboriCudd.dylib
 @@ -101,9 +98,3 @@
  echo "Removing dynamic libraries..."
  remove_dylib
  echo "Done removing dynamic libraries."
 -
 -# force a rebuild of the PolyBoRi extension
 -if [ -f $SAGE_ROOT/devel/sage/sage/rings/polynomial/pbori.pyx ]; then
 -    touch $SAGE_ROOT/devel/sage/sage/rings/polynomial/pbori.pyx
 -fi
 -
 }}}

 I replaced polybori-0.6.4.spkg with

 
http://sage.math.washington.edu/home/mvngu/spkg/standard/polybori/polybori-0.6.4.p0.spkg

 The latter spkg restores the command "remove_dynlib". I then built Sage
 4.4.1.alpha2 from scratch on sage.math with polybori-0.6.4.p0.spkg.
 Doctesting resulted in the following failure:

 {{{
 #!sh
 [mv...@sage sage-4.4.1.alpha2]$ ./sage -t -long local/lib/python2.6/site-
 packages/sagenb-0.8-py2.6.egg/sagenb/misc/misc.py
 sage -t -long "local/lib/python2.6/site-
 packages/sagenb-0.8-py2.6.egg/sagenb/misc/misc.py"
 **********************************************************************
 File "/dev/shm/mvngu/sandbox/sage-4.4.1.alpha2/local/lib/python2.6/site-
 packages/sagenb-0.8-py2.6.egg/sagenb/misc/misc.py", line 109:
     sage: print "ignore this";
 sage.server.misc.find_next_available_port('', 9000, verbose=False)   #
 random output -- depends on network
 Exception raised:
     Traceback (most recent call last):
       File
 "/dev/shm/mvngu/sandbox/sage-4.4.1.alpha2/local/bin/ncadoctest.py", line
 1231, in run_one_test
         self.run_one_example(test, example, filename, compileflags)
       File
 "/dev/shm/mvngu/sandbox/sage-4.4.1.alpha2/local/bin/sagedoctest.py", line
 38, in run_one_example
         OrigDocTestRunner.run_one_example(self, test, example, filename,
 compileflags)
       File
 "/dev/shm/mvngu/sandbox/sage-4.4.1.alpha2/local/bin/ncadoctest.py", line
 1172, in run_one_example
         compileflags, 1) in test.globs
       File "<doctest __main__.example_2[2]>", line 1, in <module>
         print "ignore this";
 sage.server.misc.find_next_available_port('', Integer(9000),
 verbose=False)   # random output -- depends on network###line 109:
     sage: print "ignore this";
 sage.server.misc.find_next_available_port('', 9000, verbose=False)   #
 random output -- depends on network
       File "/dev/shm/mvngu/sandbox/sage-4.4.1.alpha2/local/lib/python
 /site-packages/sage/server/misc.py", line 105, in find_next_available_port
         for port in range(start, start+max_tries+1):
       File "element.pyx", line 1271, in
 sage.structure.element.RingElement.__add__
 (sage/structure/element.c:10830)
       File "coerce.pyx", line 765, in
 sage.structure.coerce.CoercionModel_cache_maps.bin_op
 (sage/structure/coerce.c:6966)
     TypeError: unsupported operand parent(s) for '+': '<type 'str'>' and
 'Integer Ring'
 }}}

 I have wrapped up a sage.math binary of this patched version of Sage
 4.4.1.alpha2. You can find it at

 http://sage.math.washington.edu/home/mvngu/sage.math-bin/sage-4.4.1.alpha2
 -patched-sage.math.washington.edu-x86_64-Linux.tar.gz

 I removed the directory

 `SAGE_ROOT/devel/sage-main/doc/en/thematic_tutorials/`

 and wrapped up a source distribution, which can be found at

 http://sage.math.washington.edu/home/mvngu/sage-
 src/sage-4.4.1.alpha2-patched.tar

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8192#comment:31>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to