#9703: Doctest failures caused by non-working sympow on 32-bit Solaris x86 and
32-bit OpenSolaris
------------------------+---------------------------------------------------
   Reporter:  drkirkby  |       Owner:  GeorgSWeber
       Type:  defect    |      Status:  new        
   Priority:  major     |   Milestone:  sage-4.5.3 
  Component:  build     |    Keywords:             
     Author:            |    Upstream:  N/A        
   Reviewer:            |      Merged:             
Work_issues:            |  
------------------------+---------------------------------------------------
Changes (by drkirkby):

 * cc: leif, pjeremy, fbissey, was, cremona (added)


Comment:

 Replying to [comment:3 mpatel]:
 > By generating the data files directly, with
 `SAGE_LOCAL/lib/sympow/new_data`,  I was able to get the "optional" and
 "not tested" examples
 [http://www.sagemath.org/doc/reference/sage/lfunctions/sympow.html here]
 to run.  To really run `./sympow -new_data 2` for the example

 Try that on the '''global''' installation of sage on sage.math - not your
 own private one.

 I'm told part of the problem is that SYMPOW is trying to write data files
 below its installation directory. So it fails on a global installation of
 Sage, unless the user the user has root access.

 But there's very little error checking, so the fact the data files are not
 created is not reported.

 > It seems that part of the Sage interface to SYMPOW is broken.

 If it was only that!

 > But I don't know if missing data files caused the failures reported here
 and at #9166.

 To the best of my knowledge, not all examples need data files. When they
 do, a message is printed telling one how to create the data files. So that
 is not all the reason. That is certainly applied by the README file in the
 source code.

 I've run the {{{smypow}}} executable from the command line, and find
 problems unrelated to the generation of data files.

 It's not just the C code that is bad. There's a {{{Configure script}}}
 that starts with {{{#!/bin/sh}}}, then has code which checks if {{{sh}}}
 is on your system or not!

 My preference would be to remove this, or at least move it to
 experimental, but William seems keen to keep it as a standard package. It
 seems a bit strange to me given.

  * This is apparently very specialised code.
  * It is so badly written
  * It is causing problems on Solaris x86, Cygwin and !ArchLinux.

 That seems an alful lot of problems

 I'm cc'ing a few people that I know have looked at SYMPOW at some point in
 the past. They might have some comments. Perhaps William has some comments
 to he would like to add to the ticket.

 Dave

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9703#comment:7>
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