#9210: pkg-config prefix statements in SAGE_LOCAL/lib/pkg-config not changed 
upon
Sage move
---------------------------+------------------------------------------------
   Reporter:  jason        |       Owner:  GeorgSWeber 
       Type:  defect       |      Status:  needs_review
   Priority:  major        |   Milestone:  sage-4.4.4  
  Component:  build        |    Keywords:              
     Author:  Jason Grout  |    Upstream:  N/A         
   Reviewer:               |      Merged:              
Work_issues:               |  
---------------------------+------------------------------------------------

Comment(by drkirkby):

 It was a lot quicker than I expected.

 Something has gone wrong here though. The installation worked fine before
 it was moved. First I create the binary.

 {{{
 drkir...@redstart:~/32/sage-4.4.3$ ./sage -bdist 4.4.3-ax
 Sage works!
 Copying files over to tmp directory
 local/lib/python2.6/python2.6: failed to get acl entries
 local/lib/libgfortran.so: failed to get acl entries
 cp: cannot access *.sage
 Copying Sage library over
 Making empty spkg's
 }}}

 I think we need to copy libgfortran (see #8049) though the failure to do
 so should not cause me a problem, as the system has it. But when I tried
 to move the distribution, I get:

 {{{
 -bash-3.00$ ./sage
 ----------------------------------------------------------------------
 | Sage Version 4.4.3, Release Date: 2010-06-04                       |
 | Type notebook() for the GUI, and license() for information.        |
 ----------------------------------------------------------------------
 The Sage install tree may have moved
 (from /export/home/drkirkby/32/sage-4.4.3 to
 /export/home/sageserv/sage-4.4.3-after-rewrite-sage-location-patch-
 Solaris10_03_2005-sun4u-SunOS)
 Changing various hardcoded paths
 (please wait at most a few minutes)...
 Do not interrupt this.
 Done resetting paths


 ------------------------------------------------------------
 Unhandled SIGSEGV: A segmentation fault occured in Sage.
 This probably occured because a *compiled* component
 of Sage has a bug in it (typically accessing invalid memory)
 or is not properly wrapped with _sig_on, _sig_off.
 You might want to run Sage under gdb with 'sage -gdb' to debug this.
 Sage will now terminate (sorry).
 ------------------------------------------------------------
 }}}

 I don't have gdb on this machine. I'll investigate, but for now, there may
 be a problem here.



 Dave

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