#7287: [needs review] Update Maxima spkg to build ECL library
---------------------------+------------------------------------------------
   Reporter:  nbruin       |       Owner:  nbruin    
       Type:  enhancement  |      Status:  needs_work
   Priority:  major        |   Milestone:  sage-4.2.1
  Component:  packages     |    Keywords:            
Work_issues:               |      Author:            
   Reviewer:               |      Merged:            
---------------------------+------------------------------------------------

Comment(by kcrisman):

 Replying to [comment:5 nbruin]:
 > In the above transcript, the fact that (require 'maxima) fails indeed
 indicates that the install failed. The other attempts to load maxima fail
 because the library "maxima.fas" now gets installed in a different place.
 >

 I guess what I meant was that Maxima still works as an executable within
 Sage.

 > If you take a look at the patch that was made to spkg-install,
 > you can see that the four lines added can't possibly lead to
 > maxima failing so badly.

 Yes, I noticed that.  Of course, Maxima itself isn't failing per se...
 > One guess I can make is that I packaged the spkg in the wrong way (I
 actually followed the instructions in spkg-dist!). The resulting spkg is
 quite a bit smaller than "p0" that Ghitza provided, so perhaps maxima
 automake files got deleted by that script?
 >

 That seems very likely; the size should be exactly the same, one would
 think.

 > To test this hypothesis:
 >  - Unpack the original maxima spkg (or install with -s)
 >  - apply the attached patch, or paste in the relevant lines into spkg-
 install
 >  - install again
 >
 > If that works, then one should probably just repackage the spkg.
 Otherwise, I don't know what the problem is.

 Unfortunately, although repackaging it did seem to solve the size issue, I
 still get the same error as above.  In particular, I get the following in
 a different log:
 {{{
 ;;; Note: Creating tag: "_eclLn4HfWn8_QUH5U1z" for #P"binary-ecl/maxima-
 package.o"
 ;;; Internal error: Unable to find include directory
 ;      - Binary file binary-ecl/maxima-package.fas is old or does not
 exist.
 ;        Compile (and load) source file
 /Users/.../sage-4.2/spkg/build/maxima-5.19.1.p1/src/src/maxima-
 package.lisp instead? y
 ;      - Should I bother you if this happens again? y
 ;      - Compiling source file
 ;        "/Users/.../sage-4.2/spkg/build/maxima-5.19.1.p1/src/src/maxima-
 package.lisp"
 ;;; Compiling /Users/.../sage-4.2/spkg/build/maxima-5.19.1.p1/src/src
 /maxima-package.lisp.
 ;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=2
 ;;; End of Pass 1.
 ;;; Note: Creating tag: "_eclLn4HfWn8_1eX5U1z" for #P"binary-ecl/maxima-
 package.o"
 ;;; Internal error: Unable to find include directory
 ;      - Loading binary file "binary-ecl/maxima-package.fas"
 }}}
 So it's not finding that even upon normal building.   Is the .fas file
 what we typically use, though?  My sense is that it's
 /local/lib/maxima/5.19.1/binary-ecl/maxima.  I don't know that the
 automake message is as important, as apparently there is a Maxima
 executable still there:
 {{{
 ----------------------------------------------------------------------
 | Sage Version 4.2, Release Date: 2009-10-24                         |
 | Type notebook() for the GUI, and license() for information.        |
 ----------------------------------------------------------------------
 sage: 3+3
 6
 sage: integrate(x^3)
 1/4*x^4
 }}}

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